Exception 1 When calling IWB_HTML_HELP_URL_GET occured

Hi,
Could any body help me to overcome from the below problem.
While executing the queries with an end user id (ofcourse we have only
one Enduser id presently) in Analyzer we are getting the error
Exception 1 When calling IWB_HTML_HELP_URL_GET occured.
But in the query designer , while executing the query as Display Query
on the web , we are not getting any error with that userid.And also we
are not getting this problem with the userid which has all
authorizations.
Kindly provide a help to sort out this problem in the Analyzer.
We are working on Netweaver 2004s and on SP 13. And using 7.x Analyzer.
Thanks and Regards,
Anil Kumar Sharma .P

Hi Anil,
check this thread it may be helpful....
Re: How to install help files on BI 7.0 bex analyzer
cheers
Sunil

Similar Messages

Exception happened when calling deliver API for BI Publisher Bursting

Hi All,
I have developed a BI Publisher report on OBIEE standalone instance (Oracle Business Intelligence 11.1.1.5.0).
I am able to generate the report and burst the output to emails successfully.
But when I tried to burst the output directly to the printer or to save the output FILEs to local machine, am getting the below error/exception.
For PRINT type...error is below
Document delivery failed
[INSTANCE_ID=bisrv.oracleads.com.1305914111196] [DELIVERY_ID=1182]Error deliver document to printer::Exception happened when calling deliver API::Error deliver document to printer::Exception happened when calling deliver API::oracle.xdo.delivery.DeliveryException: oracle.xdo.delivery.DeliveryException: java.net.UnknownHostException: blr-ibc-7a-prn1 oracle.xdo.service.delivery.DeliveryException: oracle.xdo.delivery.DeliveryException: oracle.xdo.delivery.DeliveryException
for FILE type.... error is below
Document delivery failed
[INSTANCE_ID=bisrv.oracleads.com.1305914111196] [DELIVERY_ID=1192]Error deliver document to file::FILE=[D:\Harish:9930609876-10001969343.pdf::Exception happened when calling deliver API::FILE=[D:\Harish:9930609876-10001969343.pdf::Exception happened when deliver to file:: FILE_NAME= D:\Harish/9930609876-10001969343.pdf] ::oracle.xdo.delivery.DeliveryException: java.io.FileNotFoundException: D:\Harish/9930609876-10001969343.pdf (No such file or directory)oracle.xdo.ser
Can anyone please help on this?
Thanks,
Harish

Hi Varma,
thanks for the reply.
Here are the below sql scripts I used.
-- Printer
SELECT BILL_NUMBER      KEY,
'Layout'           TEMPLATE,
'en-US'                     LOCALE,
'PDF'                          OUTPUT_FORMAT,
'PRINT'                     DEL_CHANNEL,
BILL_NUMBER                OUTPUT_NAME,
'true'                          SAVE_OUTPUT,
'Direct Printers'           PARAMETER1,
'LocalPrinter'               PARAMETER2,
1                               PARAMETER3,
'd_single_sided'           PARAMETER4,
'default'                     PARAMETER5
FROM XXXX_BILL_TAB;
-- File
SELECT BILL_NUMBER           KEY,
'VLayout'           TEMPLATE,
'RTF'               TEMPLATE_FORMAT,
'en-US'           LOCALE,
'PDF'           OUTPUT_FORMAT,
'FILE'           DEL_CHANNEL,
'true'           SAVE_OUTPUT,
'Monthly Bill for ' || MOBILE_NUMBER OUTPUT_NAME,
'D:\Harish'      PARAMETER1,
MOBILE_NUMBER||'-'||BILL_NUMBER     PARAMETER2
FROM XXXX_BILL_TAB;
Thanks,
Harish
Edited by: 899863 on Dec 16, 2011 4:01 AM

Exception Message when calling WebService component

Hi,
We are using a Webservice component in our workflow. I want to know if there is a way to get the Exception message when an exception occurs in the Webservice call. We want to be able to handle the exception in the Livecycle layer and not the Flex layer.
When I draw a route from the Exception lightning bolt and select the type of Exception, it goes to the route when an exception occurs but I have not found a way to get the Exception message.
Does anyone know how to do that?
Thanks in Advance.
A

I'm using Linux in my server, and yes, my application is configured to run through an Http Proxy-server =)
When running the application on local, I included the Ip of my webservice in the proxy exceptions, so It wasn't blocked.
Maybe I have to remove the webService Ip from the exceptions, when running in the server.
I'll provide you with more details of my server as soon as the person in charge arrives.
But then, you think that exception is raised whenever the proxy or the application is blocking the webservice ip?
If that's so, I think I have a good track to keep searching.

Exception CX_SY_DYN_CALL_ILLEGAL_TYPE when calling function

Hello,
When I call a function module, it gives a runtime error like this:
Runtime error CALL_FUNCTION_CONFLICT_TYPE
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
The problem is that I'm using something like below:
call function zzz
exporting
        xxx             = yyy
with:
xxx type char50
yyy type char2
Is there a possibility to transform my char2 into a char50?
By doing this, I would be able to use the function module.
Thanks

hi,
do one thing just make the type and size of both the importing and exporting parameter same...
example:-
data: a(10) type c.   (importing)
data: b(10) type c.       (exporting)
i think this will help u
with regards,
Ritesh J

Exception Handling when calling a PHP Webservice

I followed a great tutorial on setting calling PHP services from ABAP ([Accessing arbitrary databases from within ABAP using a PHP data hub and web services|Accessing arbitrary databases from within ABAP using a PHP data hub and web services]). Unfortunately I'm getting occassional CX_AI_SYSTEM_FAULT exceptions and I don't know how to handle them gracefully.
I'm calling the web service ABAP code from an RFC function which for some reason doesn't allow TRY/CATCH statements (I get a message saying "During RFC/update, no exception classes can be used".)
I'd be happy enough just to ignore the error since it's currently dumping users out of order entry.
To make matters more complicated, I can't TRY/CATCH my own RFC since I'm calling it from GuiXT
I'd really appreciate help on this; I'm pretty stumped.
Thanks,
Lee

Well, to answer my own question, I found an ugly workaround.
Change attribute from "Remote-enabled" to "Normal Function", add the TRY/CATCH logic. Then call this function from the "real" RFC.
Off to program like it's 1979!
Lee

Utl_file - exception handling when inserted in bulk.

Hi,
I am using Oracle 10gR2. I wanted to write data to a file. Due to huge number of records, I am collecting them into a collection, traversing e collection, appending the values in collection to a varchar variable with new line in a loop.If the array size is say 50, I will have 50 values in the Vatchar variable separated by CHR(10). and I will insert the variable using UTL_FILE.PUT so that 50 lines will be inserted with values into the file.
Now my query is if any one among those 50 values gives an exception, I feel all the 50 values can't be loaded. Please suggest exception handling in this case.
Regards,
Naveen Kumar.C.
Edited by: Naveen Kumar C on Sep 17, 2009 5:23 PM

You could use a CLOB in conjunction with UTL_FILE to write it out 32K at a time...
SQL> ed
Wrote file afiedt.buf
1 DECLARE
2    l_file    UTL_FILE.FILE_TYPE;
3    l_clob    CLOB;
4    l_buffer VARCHAR2(32767);
5    l_amount BINARY_INTEGER := 32767;
6    l_pos     INTEGER := 1;
7 BEGIN
8    BEGIN
9      SELECT dbms_xmlgen.getxmltype('select * from emp natural join dept').getclobval()
10      INTO   l_clob
11      FROM   dual;
12    EXCEPTION
13      WHEN NO_DATA_FOUND THEN
14        RETURN;
15    END;
16    l_file := UTL_FILE.fopen('TEST_DIR', 'Sample2.txt', 'w', 32767);
17    LOOP
18      DBMS_LOB.read (l_clob, l_amount, l_pos, l_buffer);
19      UTL_FILE.put(l_file, l_buffer);
20      l_pos := l_pos + l_amount;
21    END LOOP;
22 EXCEPTION
23    WHEN NO_DATA_FOUND THEN -- occurs when end of CLOB reached
24      UTL_FILE.fclose(l_file);
25    WHEN OTHERS THEN
26      DBMS_OUTPUT.put_line(SQLERRM);
27      UTL_FILE.fclose(l_file);
28* END;
SQL> /
PL/SQL procedure successfully completed.
SQL>

Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.boots

When attempting to create a new Account in siebel integrated with OEDQ the following error occurs.
ERROR
Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.bootstrap.library.path)(SBL-APS-00118)
STEPS
The issue can be reproduced at will with the following steps:
1) from EDQ director we have imported the EDQ_CDS,EDQ-REFERENCE DATA & EDQ_HISTORICAl DATA packages sucessfully.
2) Created dnd.param file in SIebel server SDQCOnnector folder.
3) Copied the libdnd.so file to siebsrvr lib directory(32 bit)
3) In dnd.param file we have mentioned the javalib file and instllation directory path(<Siebsrvr roo>/dnd/install)
4) Unzipped the EDQ-Siebel Connector files in dnd/install folder
5) Copied the dnd.properties file in dnd/install directory and modified it accordingly to point to installed EDQ instance.
6) Configured the Siebel components for EDQ integration.
7) Realtime EDQ jobs are running.
8) Create a new Account
Env details are
On : 8.2.2.14 [IP2014] version, Client Functionality
EDQ 11.1.1.7.4
IBM JDK 1.7 32 bit
Using Open UI
Any Champ have faced this issue and overcame it please let me know the resolution steps. your help is
Regards
Monoj Dey
9007554589

Hi Monoj,
A few questions:
- What OS is Siebel running on?
- What version of the Siebel connector are you using?
- Which libdnd.so file are you using?
- What's the contents of your dnd.parms file?
thanks,
Nick

Netweaver throwing following exception when calling the ProductionOrder WS

Hi,
when calling the ProductionOrder web service I get the following exception from the system:
nested exception is: com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe00103e] ) in rollback.
The system was migrated from Netweaver CE 7.1 SP4 to SP5 before the error started to occur.
Any ideas how to fix this? Start/Stopping ME didn't do the trick.
Kind Regards,
Christoph Mertins

Yes the stack trace is:
System exception
[EXCEPTION]
javax.ejb.EJBException: nested exception is: com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe0013ffffffb6] ) in rollback.
com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe0013ffffffb6] ) in rollback.
at com.sap.engine.services.ts.jta.impl.TransactionImpl.rollback(TransactionImpl.java:921)
at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:486)
at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:296)
at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy3782.create(Unknown Source)
at com.sap.me.productdefinition.wserpimpl.productionOrder.ProductionOrderPersister.createOrUpdate(ProductionOrderPersister.java:133)
at com.sap.me.productdefinition.wserpimpl.GenericVOServiceImpl.createOrUpdate(GenericVOServiceImpl.java:57)
at com.sap.me.productdefinition.wserpimpl.productionOrder.ProductionOrderServiceHandlerAdapter.updateProductionOrder(ProductionOrderServiceHandlerAdapter.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.proxy.AdviceInterceptor.intercept(AdviceInterceptor.java:45)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at $Proxy3884.updateProductionOrder(Unknown Source)
at com.sap.me.production.ws.ProductionOrderService.updateProductionOrder(ProductionOrderService.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:96)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:525)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:494)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:260)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:178)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:114)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:72)
at com.sap.engine.services.webservices.servlet.SOAPServletExt.doPost(SOAPServletExt.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.me.webservice.ClearServiceContextFilter.doFilter(ClearServiceContextFilter.java:28)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@aa1bf8e has already been closed.
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.throwBaseResourceException(LocalTXManagedConnectionImpl.java:89)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.rollback(LocalTXManagedConnectionImpl.java:389)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.rollback(TransactionImpl.java:813)
... 83 more
Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@aa1bf8e has already been closed.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.vendor.VendorConnectionHandle.validate(VendorConnectionHandle.java:383)
at com.sap.sql.jdbc.vendor.VendorConnectionHandle.setAutoCommit(VendorConnectionHandle.java:38)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.rollback(LocalTXManagedConnectionImpl.java:386)
... 84 more

Exception when calling ABAP Proxy modelled in SAP PI: CL_SOAP_RUNTIME_ROOT

Hi,
We have a scenario where we:
1. Modell an interface in SAP PI
This interface contains a complex type from a different namespace
2. Use it to create an ABAP proxy in backend system
3. Configure it with SOAManager
4. Call the ABAP proxy ws directly from a third-party system (biztalk)
We're currently testing calling the ABAP proxy from soapUI, but get a strange exception thrown by the SOAP framework in ABAP backend.
The test in soapUI is setup by importing the WSDL acquired from SOAMANAGER.
The error message we in the SOAP response is:
CX_SY_REF_IS_INITIAL:Exception CX_SOAP_ROOT occurred
(program: CL_SOAP_RUNTIME_ROOT==========CP, include: CL_SOAP_RUNTIME_ROOT==========CM004, line: 130)..
An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally,
nor declared in a RAISING clause.Dereferencing of the NULL reference
It is a very low level error from the CL_SOAP_RUNTIME_ROOT program and not a descriptive error message at all.
We've checked the user and the authorizations it has, we've redone the SOAManager config but the problem persists.
We find no dumps in the ABAP proxy since the request never reaches it.
For a limited time I'll make WSDL and SOAP response available
WSDL (some values anonymized) available at http://dl.dropbox.com/u/4379928/SOAP/project.wsdl
Complete SOAP response is available at http://dl.dropbox.com/u/4379928/SOAP/soap_data.xml
Any ideas on where to look?

Hi,
We've now managed to implement a workaround.
The workaround was to create the endpoint in PI as well.
So that the traffic goes from third-party solution->PI-> WS-enabled ABAP Proxy
When we did this initially, we got some errors related to the asynch method of this call, but this was resolved by changing the channel from "best effort" to "Guaranteed delivery".
Still we don't know what the root cause of the initial problem was, but we assume it is related to the asynch nature of the service (though we have other asynch proxies that work without problems).
Regards
Dagfinn

I am receiving this error message when trying to export pictures: 'Unable to Export": An internal error has occured: Win32 API error 2 ( "The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute.// I have a H

I am receiving this error message when trying to export pictures: 'Unable to Export": An internal error has occured: Win32 API error 2 ( "The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute.// I have a HP ENVY Phoenix, fully loaded, 1 1/2 years old.

Nevermind I fixed it. Thank you.

Exception when calling SOAP Lookup-API async

Hello,
i'm calling a SOAP-Comunication Channel (Lookup-API) out of my MessageMapping. The WebService Called is asynchron because i just send some data and i don't care about the result. The WebService itselfs is implemented on our XI. In other words: we call us self.
In order to call my WebService asynchronous, i added &QualityOfService=ExactlyOnce at the end of the URL. The SOAP-Action is:
http://sap.com/xi/WebService/soap1.1
The problem is: the WebService works perfekt! But: in my mapping i get
nevertheless the following exception:
Errorcom.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_Receiver_SetIdocStatusAsync (Party: , Service: SetIdocStatus, Object ID: f6b1ce38e9fa332cba4eb1a6f0a3e17f) null com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel SOAP_Receiver_SetIdocStatusAsync (Party: , Service: SetIdocStatus, Object ID: f6b1ce38e9fa332cba4eb1a6f0a3e17f) null at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:96) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:141) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:74) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.af.service.api.AFException at com.sap.aii.af.service.api.AdapterAccess.call(AdapterAccess.java:122) at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:87) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:141) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:74) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

The problem is: i don't know how to check for the HTTP-Header, because
my call
SOAPOutPayload = accessor.call(payload);
throws the mentioned exception, even though it works behind the scene.
Is it possible to check for the HTTP-Response-Code in the catch block?
We want to avoid an synchronous scenario because we don't need the result and the WebService is rather slow.

I have an IPhone 4S and am using the Phonak Icom with my hearing aids. All works well except for when I get an incoming call I can't hear the ringing/ringtone in my aids. Any solution?

I have an IPhone 4S and am using the Phonak Icom with my hearing aids. All works well except for when I get an incoming call I can't hear the ringing/ringtone in my aids. Any solution?

Did you get any answers?

MSS - Business Event Details - Error Unexpected Exception when Calling RFC

Dear Experts,
Manager is getting the Error "Unexpected Exception when Calling RFC from Profile Application 'Business Event' when he tries to get the Training history of ONE employee in MSS. However, he is getting the details for the other employees of his department.
Any inputs on this?
Thank you.

I believe it is our custom iView that is incorrect.

Environment.Exit hangs when called from an application domain exception handler

I've implemented a handler for exceptions not thrown in the main GUI thread of my C# WinForms application, as follows:
AppDomain.CurrentDomain.UnhandledException += OnUnhandledExceptionThrown;
This handler is called from a background thread. The last statement in this handler is a call to
Environment.Exit with the application exit code. However, the application hangs in this call. From within Visual Studio, it hangs and I'm unable to break the application; I have to use Task Manager to terminate Visual Studio. Environment.Exit
works fine when called from the unhandled exception handler for the GUI thread. Is there a better way to terminate the application in the context of an unhandled exception thrown by a background thread?

Are you just trying to avoid a crash? Environment.Exit can cause deadlocking if exiting in the wrong kind of scenario; if you're just trying to avoid a crash, use
GetCurrentProcess with
TerminateProcess to terminate your own process. It skips the notification phases that Environment.Exit uses which prevents the common deadlock scenarios.
WinSDK Support Team Blog: http://blogs.msdn.com/b/winsdk/

My iphone is a 3g and I was updating it's sofware from 4.1 to 4.2 when an error called 1604 occured during the restoration. what should i do?

my iphone is a 3g and I was updating it's sofware from 4.1 to 4.2 when an error called 1604 occured during the restoration. what should i do?

Shifaau wrote:
now an error code by 1015 comes up.
Again...Search the forums or Google for the error message appearing and follow the troubleshooting steps provided.

Exception 1 When calling IWB_HTML_HELP_URL_GET occured

Similar Messages

Maybe you are looking for