A failure occured while calling Diagnostics Setup web service

Hi Guys.
When performing the Automatic Activities of the Solution Manager 7.1 Basic Configuration, on one step you can execute the Diagnostics Configuration.
When clicking on the details it shows the following message.
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 401 : Unauthorized")
Error when processing Web service call
I tried running the configuration a user having SAP_ALL, also j2ee_admin, so no clue where is the authorization fault.
Any ideas what is causing this Authorization Error?
I also tried to access SMD manually on saphost:8000/SMD but it says Root Cause Analysis Setup has been moved and Call transaction SOLMAN_SETUP from the SAP GUI to configure SAP Solution Manager.
Is there any url to access to SMD directlty without going thru SOLMAN_SETUP since i dont see where is the url.
Thanks!

Please make sure that your solman box meet the software prerequisit as per this note below
1483508 : Solution Manager 7.1: Root Cause Analysis pre-requisites
This will solve that ptoblem .
Best Regards
Jai Wardhan

Similar Messages

Error occured while Adding a reference Web Service(BizTalkServer2009_Tutorial2)

Hi,
I was going through the Biztalk tutorials. While doing the second tutorial of web service I got stuck while adding reference to the Web Service.
Steps I did:
Add service reference(by right clicking my project) --> Advanced --> Add Web Reference --> URL : http://localhost/b2bsupplierprocesspo/process.asmx
But somehow this URL is not accesible over there. I got following error:
Please suggest/guide me on this.
Thanks, Girish R. Patil.

The error clearly states the reason for failure, being "CS0016: Could not write to output file ..... ..... - Access is denied."
The directory in question is the "C:\Windows\Microsoft.Ner\Framework\v2.0.50727\Temporary ASP.NET Files". So two things
Does the tutorial mention that the Web Service should be hosted under a .Net V2.0 Application Pool? If so then please give "Full Control" permissions to the above directory for the BizTalk Service Accounts (which also should be part of your "BizTalk Isolated
Host Users" Group.
If not then the service has to be hosted in a .Net v4.0 app pool. Change the Application Pool Settings through IIS Manager and give permissions to a similar folder (Temporary ASP.Net) but under the Framework\V4.0.... directory.
Regards.

Error in PeopleTools 8.48 while calling CI based Web Services from BPEL

Hi All,
I am working with a CI based web serives and using the PeopleSoft generated wsdl file while calling from a BPEL process. When I am using the same component in PeopleTools 8.47, it's working fine. But the same is NOT working when I'm using PeopleTools 8.48 using the same BPEL server and program.
Here is the error message :-
exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: oracle_endpoint: oracle_endpoint.
Please help if you know the answer.

Hi,
You need to download all the associated xml schemas from PeopleSoft portal and store them in the path where you are creating BPEL process, it's different from what we used to do in PeopleTools 8.47 ( there was only one wsdl file), whereas in PeopleTools 8.48 you need to copy all associated xml schemas.
But I m not able to find out why the native JAVA error is thrown, do I need to provide some patches?

Delayed response while calling the process web service

I have four managed servers in a cluster and the ip addresses are
managed_server_1 -20.20.40.21
managed_server_2 -20.20.40.22
managed_server_3 -140.20.40.23
managed_server_4 -140.20.40.24
The admin server is on 20.20.40.21
I start the managed server from command prompt using the commant
./startManagedWeblogic {name of the managed server} {admin console url} ie
i start managed_server_1 from 20.20.40.21 unix box by going to {weblogic installation}\bin
and running the following command (we have some issues with the node manager so have been using this
method)
./startManagedWeblogic managed_server_1 http://20.20.40.21:17003
similarly i start the other servers from their respestive unix boxes
managed_server_2 from the 20.20.40.22 unix box using the command ./startManagedWeblogic managed_server_2 http://20.20.40.21:17003
managed_server_3 from the 140.20.40.23 unix box using the command ./startManagedWeblogic managed_server_3 http://20.20.40.21:17003
managed_server_4 from the 140.20.40.24 unix box using the command ./startManagedWeblogic managed_server_4 http://20.20.40.21:17003
all these servers are in the cluster named BPM_cluster and the bpmengine is deployed onto this cluster
when i deploy the application to the bpmengine it gets properly deployed onto the servers
and i could see the process web services getting generated
but when i try to call these webservices for each managed server seperately
the response from managed_server_1 and managed_server_2 takes leass tha 2 secs
but the response from managed_server_3 and managed_server_4 takes about 25 secs
I am not able to figure out why us taking so long from the managed servers 3 and 4
the bpmengine ds and directory ds have the cluster as targets (I also tried to point to all the servers in the cluster even that
didnot work). I feel that there is db connectivity issue from the servers but i am not sure how to check that.
Can anyone help me with this ?
Thanks

Please make sure that your solman box meet the software prerequisit as per this note below
1483508 : Solution Manager 7.1: Root Cause Analysis pre-requisites
This will solve that ptoblem .
Best Regards
Jai Wardhan

Exception while calling the dotnet web service.

I have an Axis2-1.3 web client to a dotnet web service. The client makes rapid calls to the webservice. some times it works but often the call fails with the following exception.
org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Connection reset
     at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
     at com.somefirm.SystemManagerStub.fromOM(SystemManagerStub.java:2193)
     at com.somefirm.SystemManagerStub.getAllPlayersSettings(SystemManagerStub.java:914)
     at com.ser.services.webclient.Client1$ObjectListener.processMessage(Client1.java:279)
     at com.ser.services.webclient.Client1$ObjectListener.onMessage(Client1.java:174)
     at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.deliverAndAcknowledge(MessageConsumerImpl.java:338)
     at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.onMessage(MessageConsumerImpl.java:273)
     at com.sun.messaging.jmq.jmsclient.SessionReader.deliver(SessionReader.java:113)
     at com.sun.messaging.jmq.jmsclient.ConsumerReader.run(ConsumerReader.java:185)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.Exception: com.ctc.wstx.exc.WstxIOException: Connection reset
     at com.somefirm.Rule$Factory.parse(Rule.java:681)
Caused by: com.ctc.wstx.exc.WstxIOException: Connection reset
     at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:683)
     at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1086)
     at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:927)
     at com.somefirm.Rule$Factory.parse(Rule.java:643)
     ... 14 more
Caused by: java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
     at org.apache.commons.httpclient.ContentLengthInputStream.read(ContentLengthInputStream.java:169)
     at java.io.FilterInputStream.read(FilterInputStream.java:111)
     at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:107)
     at java.io.FilterInputStream.read(FilterInputStream.java:111)
     at java.io.PushbackInputStream.read(PushbackInputStream.java:161)
     at java.io.FilterInputStream.read(FilterInputStream.java:90)
     at com.ctc.wstx.io.UTF8Reader.loadMore(UTF8Reader.java:362)
     at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java:110)
     at com.ctc.wstx.io.MergedReader.read(MergedReader.java:101)
     at com.ctc.wstx.io.ReaderSource.readInto(ReaderSource.java:84)
     at com.ctc.wstx.io.BranchingReaderSource.readInto(BranchingReaderSource.java:57)
     at com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1021)
     at com.ctc.wstx.sr.StreamScanner.parseLocalName2(StreamScanner.java:1771)
     at com.ctc.wstx.sr.StreamScanner.parseLocalName(StreamScanner.java:1731)
     at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2912)
     at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2846)
     at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
     ... 16 more
Can any one please help me?

Hi Durga,
thanks for the reply.
But i did not understand your solution.
here is the code i use...
BAPI__MATERIAL__GET__DETAIL bapi_input = new BAPI__MATERIAL__GET__DETAIL();
bapi_input.setMATERIAL(matnr);
try{
BAPI__MATERIAL__GET__DETAILLocal bapi_local = this.getBAPI__MATERIAL__GET__DETAIL();
BAPI__MATERIAL__GET__DETAIL_dot_Response res = bapi_local.BAPI__MATERIAL__GET__DETAIL(bapi_input);
BAPIMATDOA doa = res.getMATERIAL__GENERAL__DATA();
BAPIRETURN ret = res.getRETURN();
retValue = new Ret();
retValue.setMsg(ret.getTYPE());
}catch (Exception e) {
     e.printStackTrace();
plz lemme know if any thing is wrong with it.
or do i have to configure something on the server to make bapi global.
thnks,
Sudheer.

A failure occured while importing Java SSO ticket certificate in ABAP stack Exception : FOREIGN_ENQUEUE_LOCK

Dear All,
We have completed the fresh installation of Soman7.1.
Now , We are doing the "Configuration of the Solman" and we are in the Step "Basic configuration ".
SID: SMI
Hostname: Solmantrg
Solman version: 7.1
The SSO Setup is failing with below error.
Message :
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null. Details : 'user' missing
Details of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg.thetimes.co.in (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null
!! Exception : 'user' missing
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
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:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
========================
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1087)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3310)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:773)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:722)
at com.sap.sup.admin.setup.SolManRfcAdapter.getJ2eeSsoSettings(SolManRfcAdapter.java:649)
at com.sap.sup.admin.setup.ManagingServices.updateSSOfromURLrepository(ManagingServices.java:790)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:773)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
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:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
In strustsso2, cerficate date is valid only.
kindly help us to fix this SSO_Setup issue
Thanks and Regards,
Gayathri.K

Hi ,
Thanks for the above reply.
I have executed the Step 2.3 AND 2.4 and i started the SSO Setup again. Still i am getting below error
Message
A failure occured while importing Java SSO ticket certificate in ABAP stack
Details Of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Also , i have checked the note # 1008474 Diagnostics Setup Wizard uses wrong ABAP client.
As mentioned in above note, i have checked in visual admin all settings are maintained correctly.
RFC destination WEBADMIN & SOLMANDIAG is also working fine.
please tel why i am getting Foreign Enquelock
Regards,
Gayathri.K

Sysprep - "Failure occurred while executing drmv2clt.dll" - Fix

I don't usually have problems running sysprep, but the first time I ran it on a Windows 7 (BETA Ultimate 32bit) PC I received an error that Sysprep could not continue and was halted. I went to c:\windows\system32\sysprep\panther and opened the setuperr.log file. (Actually, Windows won't let you open this file (!) so copy it out of this directory, then open it.) There was not much in the file, just a few lines referencing drmv2clt.dll.
2009-04-20 13:37:55, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'drmv2clt.dll,Sysprep', returned error code -2147024864[gle=0x00000020]
2009-04-20 13:37:55, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x00000020]
2009-04-20 13:37:55, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]
I searched the MS KB, and sadly, could find nothing. Then I Googled some of the above and found a couple of references to this. They mentioned that drmv2clt.dll is associated with Digital Rights Management and this error in Sysprep could be fixed by disabling Media Sharing in Windows Media Player. That seemed odd. This Windows 7 PC was setup just to test Sysprep and imaging. We didn't even start or configure Windows Media Player. I also had no idea how to disable Media Sharing in Media Player?? This time I went to Windows Help and searched it, but sadly, it too had no information. I once again Googled this and found out how to disable Media Sharing in Media Player.  It is a service that is configured to automatically start at boot up.
Click Start > Run, type Services.msc to open the Services applet.
Scroll down to Windows Media Player Network Sharing Service, double click it, change the Startup type to Disabled. Click OK.
Reboot the PC
Once I did this, I re-ran Sysprep (sysprep /generalize /oobe /shutdown /unattend:sysprepdomainWin7.xml) and it ran without error.
Seems like a sysprep bug.  I don't think this is a Win7 thing since the fix for this I read was from a BDD 2007 document. Oh, and if you want to know how to fix problems in Windows, use Google.

Yes, for a company that has a long and challenged history of omnipotence I have come to expect these information black holes as a technician. I have been working with MS and also with Windows since DOS 2.2 and I recall the DOS 4.0 debacle. It was the beginning
of the use of "Hi-memory" area. They had created the ability to use hi-memory (introduced by Compaq) but they didn't bother to reserve or map what was in memory. So when DOS went to retrieve information loaded in memory it either was overwritten, or could
not be located. Thus, all machines locked! I worked with a couple engineers from UC Irvine who identified and resolved the problem Windows. I recall working at WB and I introduced Windows ADS, well ultimately we had to migrate from one machine to another.
There was an information store containing the data of active directories configuration and security called the "DIT" in restoring ADS I ran into a wall. There was no documentation on how to move the DIT, the core of ADS's information. Well I finally got to
a high level technician that could work with me to relocate and document the procedure. If you are familiar with UNIX then you understand that the user community documents and tests new code. Just inherent part of computing. So I am not surprised that they
have left us to resolve this issue ourselves.
Of course they are now pushing AZURE and online storage which could be why they aren't assisting us with this issue.
the only time is now!

Internal Error occurred while calling the ProcessDPCommands API

We have installed Business Objects XI with MySQL. We are getting following error when we click on view query on the WEBI Reports
" Internal Error occurred while calling the ProcessDPCommands API Error WIS 30270".
When we change the CMS database to ORACLE everything works fine it looks like some issues when CMS database is MYSQL
Please hep to fix this problem
Installation is on Solaris 10
Edited by: AshishDatar on Nov 6, 2009 3:00 PM
Installation is on Solaris 10

did you check whether universe connection is pointing to the correct db?The following url might be helpful:
[http://www.forumtopics.com/busobj/viewtopic.php?t=52355&view=previous]

An internal error occurred while calling 'submitReport' API. (Error: ERR_WI

An internal error occurred while calling 'submitReport' API. (Error: ERR_WIS_30270)
We get above mentioned error message at any point in WebI Rich Client.
DataSource: Teradata 12.0 (Local machine)
BO XI 3.1 Client installed on local machine
Universe (Secured connection)
WebI : desiging and creating in Standlone mode
WebI client version : 12.1.0.882
Many times above written error is thrown 2-3 times even when we click on OK button and lastly followed by new error message:-
Unable to get the first page of the current report - Web Intelligence will switch to structure view (WIJ 20003).
Flow: We create report based on locally saved universe. There are couple of scenarios for which error comes
1) After successfully saving the report, reopen and refresh causes this error (1st error and 2nd)
2) Droping a properly written variable on measure column, if done Ctrl + Z, report works sometimes (both or 2nd error message)
3) Draging out the mesaure or dimension from report (only 2nd error)
Report is simple and no other stuff except the cross tab table
Even if we start with simply dropping the dimension and measures on report, 2nd error comes at any time.
What we noticed is that if we do all desiging in structure mode and then run instead of in result mode, reports works for more time.

You can have a look here:
Input Controls with Break Error on webi report
http://www.forumtopics.com/busobj/viewtopic.php?t=60789&postdays=0&postorder=asc&start=45
Re: internal error occurred while calling the 'submitReport' API.
I'm Back
HAPPY NEW YEAR

Error: Your request could not be completed because a failure occurred while the report was being processed.

Post Author: sagimann
CA Forum: Deployment
Hello,
I'm not sure if this is due to bad deployment, but I suspect it is, at least due to bad environment.
My env is:
Solaris 10 64 bit
Oracle 10g client installed under /opt/oracle/app/oracle/product/10.2.0/client_1
BOXIR2 + FP2.6 installed under /opt/reporting, running under user 'bouser'. by the way, 'tnsping' works via that user.
Important bouser env:
ORACLE_HOME=/opt/oracle/app/oracle/product/10.2.0/client_1
TNS_ADMIN=$ORACLE_HOME/network/admin
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32
I reboot the box, then start BO like so:
cd /opt/reporting/bobje
. setup/env.sh
./mysqlstartup.sh
./startservers
./tomcatstartup
Then, I import a BIAR file with some reports, and whenever I try to open any report via infoview, I get a gray error message INSTEAD of the input param form:
Error:
Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator.
This does not occur in our BOXIR2 on Windows, which is why I'm guess it's a deployment/env issue. The main obstacle I have is: how do I diagnose this? there's nothing in the bobje/logging folder, nothing in the /var/adm/message file except for the following line:
May 5 15:23:23 testbox1 boe_pagesd[3865]: [ID 253862 user.error] A failure occurred while the Page Server was processing report 'test report' (id=777) for user Administrator
pls advise,
thank you.

The solution is to turn off the printer preference (bottom of Page Setup screen) in the Crystal Report before uploading to the Server. Thanks to: http://pinchii.com/home/2011/12/error-adding-reports-to-crystal-reports-server/
The explanation, from a comment in the above linked blog post:
"To elaborate more on the error, what basically happens is that the Crystal Reports engine tries to get the status of the u201Creport printeru201D aka u201Cdefault printeru201D which was present on the system when the report was created, but the printer does not exist anymore. This causes the Crystal engine to error out. By setting the report to u201CNo Printeru201D, it tells the Crystal Engine not to look for that report printer when opening the report."
Edited by: abirdman on Feb 3, 2012 9:49 PM

An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30270)

Hi ALL,
I am facing a wierd issue while opening/refreshing/broadcasting a webi report.
The error message scrnshot:
This error is not throughout the reports, but for specific reports only, when checked the Bex query definition it works fine, but gives error for Webi reports.
Recently we had upgrade of BO 4.0 SP7 patch 9.
The reports are directly built on Bex queries, Bex queries contains simple Structures and few CKF's.
Would be thankful for any help recieved in resolving the above issue.
Regards,
Jaywant Kulkarni.

Hi jaywant,
Please check the note: 1760827 it may be helpful
( An internal error occurred while calling the 'processDPCommands' API. (ERR_WIS_30270) due to some scenarios.
Scenario 1:
Error occurs when try to refresh a migrated Web Intelligence report in InfoView, after entering a date or dates for prompts.
Suggested Solution:
Modify problematic report in Webi.
Change the prompt definition to be a constant, run the report in Webi, and save it.
Change the prompt definition back to prompt with required date definition. Make sure you are using the correct date format! (The report prompt should tell you what the format is supposed to be.) Re-run the report in Webi, and save it.
Re-open the report in InfoView and refresh.
Scenario 2: Error occurs when trying to edit the properties of a Webi report containing merged dimensions.
Suggested Solution:
Remove the merged dimensions and then re-establish them.
Scenario 3: Error occurs when the InfoView report has been open and idle for a long time.
Suggested Solution:
This error can be an indication of a time-out, based on the server’s settings. Make sure you save your work often. You will need to close and re-open the report when you get this error, and you may have lost any unsaved changes.

"An internal error occured while calling 'answerPrompts' API.(Error: wis_30

Hi Gurus
Getting an error message while running a webi report from infoview link(server:8080/InfoViewApp/logon.jsp)
as
"An internal error occured while calling 'answerPrompts' API.(Error: ERR_WIS_30270)
I found that while selecting refresh checkbox in one of the query which is using .xls file from the local system this is showing above error while running from above link.
If it is unchecked it is running without any error.
while running report from webirichclient(where we are developing reports) it is running without any error.
Thanks in Advance
Regards
Ritu Raj

It seems you are on SP3, and I assume the operating system of the BO server is Windows based.
Please cross-check that the Excel version you have matches the ODBC driver in the supported platforms document for XI3.1 SP3 [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4079f8f6-2b49-2d10-d790-bc596012dc25]
Second thing, I would like to see screenshots of what you mean by
"I found that while selecting refresh checkbox in one of the query which is using .xls file from the local system this is showing above error while running from above link.
If it is unchecked it is running without any error."
just to avoid misunderstandings from my side
Thanks!
Best regards,
Simone

An internal error occured while calling 'getBlob' API.(Error: ERR_WIS_30270

Hi,
I am using BOXI R3.1, when i open a Webi Report & getting one Error:
An internal error occured while calling 'getBlob' API. (Error: ERR_WIS_30270).
Do anyone know how to fix error?
Regards,

Hi,
this is an old thread..
There are a great many potential reasons for this problem.
I would recommend you use our Knowledge Base search on SMP - link here: http://service.sap.com/xsearch
.. and search for terms : webi 'getBlob' API
Also, some information about your Product version and Patch level is requiered.
Also, any explanation of workflow -
does it only happen when opening report?
are you using OpenDoc hyperlink navigation?
Moving between report tabs?
Are many Schedules running concurrently at that time ?
regards,
H

Error Message: An internal error occured while calling 'openDocumentMDP' AP

Hi,
I am working on BO XIR3.1,
we have two acceptence environment and we use the same liscense key for both the environment.
i am trying to schedule a report in the acceptence environment and my scheduling is geting failed.
due to the reason below
Server Used: XXXXXXXX.AdaptiveJobServer
PID: 3444
Parent Object Path: Cust Reports/
Remote Instance in Federated Cluster: No
Expiry: 2/16/2022 8:59 AM
Formats: Web Intelligence
Parameters:
Error Message: An internal error occured while calling 'openDocumentMDP' API. (Error: ERR_WIS_30270) .
it is a very urgent issue ,kindly help me out to solve this issue.

Thanks Amith,
You are getting error in all reports or particular report?
All the reports
These reports are migrated from one environment to other?
No,it was created in the same environment
what is the BO SP level?
SP 1
restart the SIA and then schedule report and see you are getting error or not?
I had done this ,and i am geting the same error.
Kindly help me out with a solution.
Regards
S.Cyril

Error RCIRAS0546, failure occured while the report was being processed

Hello all,
We use Crystal Reports 2008 V1 server on Linux. With 2 reports now we get the error when viewing the report from the Central Management Console (CMC)
"Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator. [RCIRAS0546]"
In de /var/log/messages, I get messages like these:
Sep 28 17:37:30 vsrv01 boe_crprocd[25630]: A failure occurred while the server was processing report file 2:11154 (RCIRAS0568)
Sep 28 17:37:40 vsrv01 boe_crprocd[25630]: A failure occurred while the server was processing report '10. LEN Rapportage per scenario (kapitaallasten, investeringen, algemene gegevens) (V1)' (id=11154) for user 12 (RCIRAS0567)
I tried several parameters on the CrystalReportsProcessingServer, like increasing/decreasing the Maximum Current Jobs and Number of Prestarted Children. None of these make a difference. Als the error occurred when viewing the report as Administrator.
The reports has a dynamic parameter, wtih content coming from the database (drop-down list). When selecting one value the report is viewing fine. With a selection of more values the error occurred. In Crystal Reports 2008 there is no problem.
I restarted the CRProcessingServer with -trace. In the trace I see the following lines:
It seems that several subprocesses start for retrieving data based on the parameter values.
After the crash of the first child, the above mentioned error occurs.
2010/09/28 15:37:23.075|==| | |25630|1474829200| |||||||||||||||(ProcWorkerManager.cpp:82) PageChildDesc constructor (id=3)
2010/09/28 15:37:23.075|==| | |25630|1474829200| |||||||||||||||(ProcWorkerManager.cpp:5489) doCreateChild() created a new child 3
2010/09/28 15:37:30.011|==| | |25630|1474562960| |||||||||||||||(ProcWorkerManager.cpp:6814) cleanupChildren() starting
2010/09/28 15:37:30.011|==| | |25630|1474562960| |||||||||||||||[ProcWorkerManager.cpp : 6854] RAS-CORE-METRICS (before cleanup) number of child processes = 3
2010/09/28 15:37:30.011|==| | |25630|1474562960| |||||||||||||||(ProcWorkerManager.cpp:6979) child id=1 crashed
2010/09/28 15:37:30.011|==| | |25630|1474562960| |||||||||||||||(ProcWorkerManager.cpp:6994) cleanupChildren() removing child id=1
2010/09/28 15:37:30.012|==| | |25630|1474562960| |||||||||||||||(ProcWorkerManager.cpp:101) PageChildDesc destructor (id=1)
2010/09/28 15:37:30.012|==| | |25630|1474562960| |||||||||||||||(ProcWorkerManager.cpp:7028) cleanupChildren() marking as stopped: worker id=1 in child id=1
2010/09/28 15:37:30.012|==| | |25630|1474562960| |||||||||||||||(ProcWorker.cpp:2703) stopping worker id=1
2010/09/28 15:37:30.012|==| | |25630|1474562960| |||||||||||||||(ProcWorkerManager.cpp:7168) cleanupChildren() ending
Does someone know this problem and what to do about this?
With kind regards,
Pim van Stam
SvSnet

We got this error message on a report that had 5 subreports, 3 of which were based on stored procedures. The report was running fine in our Dev environment and in the CR developer, but not when we published it to another environment. The problem was caused because the stored procedures had been changed in Dev (so that they ran correctly) but these changes had not been released to the other environment. Once the scripts were run to update the stored procedures the report ran successfully. So it apepars that the problem was because the stored procedure/s the subreports were using were failing, but we only got the RCIRAS0546 error message.

A failure occured while calling Diagnostics Setup web service

Similar Messages

Maybe you are looking for