SAP BW timeout

I am running a Crystal report against a BW query, via the Business Objects Enterprise XI scheduler, which is returning a successful completion message even if the query times out on the BW server.
Any thoughts as to why it should return a "successful" message?
We have raised the timeout limit on the BW server, but I would like to understand why I get the wrong return code.
Thanks,
Andy

Andrew,
Welcome to SDN , what is the message supposed to indicate... is it supposed to indicate that the job is successfully scheduled without errors or that the query has been rendered successfully ? For the latter , if there are no errors and the query can be scheduled without problems then by the definition of the success message the scheduling is a success. Maybe thats why. You could also look at :
1. Run a query trace to find out why your query is taking so much time
2. Then find out if your ODBO connection is proper
3. Check the settings on your messages in the scheuling service.
Hope it helps..
Arun
Assign points if useful

Similar Messages

SAP GUI timeout setting

Hi,
How is the SAP GUI timeout setting done?
Thank you.

Hi Lammie,
Strange. If that's happening, then definitely there should be some user-specific settings somewhere. Or maybe it has something to do with the profiles in RZ10. I don't know if it's possible but maybe the profiles can be associated with users and in your case, different ones are associated to your user and your colleagues's users.
Best regards,
Akshat

Using RS with SAP Netweaver - Timeout during allocate /CPIC 'ThSAPCMRCV'

Hi All,
I am trying to connect to a remote SAP BI server from my local SQL server 2005 Reporting Services. I was able to view all info objects in the query builder but when I try to drill down and view members / drag and drop to create a query / preview the RS report, I get the following error ,
u201CError occurred retrieving child nodes - error occurred when starting the parser - timeout during allocate: /CPIC-CALL 'ThSAPCMRCV' u201D.
I have SAP front end and business explorer installed on my system. We also have the latest patches on SAP BI server.
I tried changing the timeout value but dint help.
Any help is appreciated.
Many Thanks,
Chitra

Hi
I think you should post this in basis and security forum.
Cheers
Chanda

SAP-Router : timeout while pending for route completion

Hi Experts,
I have configured sap-router . Through router I am able to maintain connection for my sap systems on service.sap.com
But when I try to connect through 0SS1 or trying to connect through sm59 it is giving error
ERROR: timeout while pending for route completion
I have checked my saprouttab where I have maintained entry for 3299 port.
I don't know where I am going wrong.
Please provide solution.
Regards
Yogesh

Hello,
Is your SAPRouter in the DMZ ?
In that case, you have to open the firewall port.
Regards,
Abhilash

SAP inactivity timeout

Is there a way to set the SAP gui inactivity timeout for a specific user or group of users?

Hi Chris,
Note <a href="http://service.sap.com/sap/support/notes/27320">27320</a> has descriptions about rdisp/keepalive and rdisp/gui_auto_logout, are you looking for something else in this case?
Regards, Mark

SAP Router timeouts

Hi Team,
We have installed a new sap router in our landscape, Now across all the systems SAP is getting timeout issue from our router.
If i am changing it to old router everything works fine.
My query is what all commands need to check for network timeout issue, then is there any timeout parameter need to set after installation of new router in windows server 2008 for SAP Router.
Kindly suggest on this .
Thanks,
Pradeep.

Hi Nirav,
Verify if saprouter.exe and niping.exe is placed under directory E:USRSAPSAPROUTER and same path is mentioned in windows services.
If path is correct one then you need to modify registry
Under HKEY_LOCAL_MACHINE ® SYSTEM ® CurrentControlSet ® Services ® Event Log ® Application enter the key saprouter and define the following values for it:
EventMessageFile (REG_SZ): ....saproutersaprouter.exe
TypesSupported (REG_DWORD): 0x7
I hope this will help you.
Regards,
Rupali Bajpai

SAP Smartform Timeout Dump in Production for the invoice form

Hi Friends,
I am working on Invoice Smartform. It is working fine when it is having avg line items. where as in my case one invoice iss having more than 500 line items in production. For this in production it is giving timeout short dump.
In that invoice i am displaying standard fuctionality of invoice form and at the same tim i am displaying Serial Numbers based on delivery and Open Quantity based on Order. So it will take time for back processing.
Insted of Back ground processing is there any other possibility to solve this. If not Please give me some steps how to implement this form in background based on conditions (if it is having more than 200 line items then only i need to run in background else foreground)
Pls give me your valuble inputs.
Thanks,
Srinivas.

Hi Vipin,
Pls provide more details like SP level , Kernel level etc.
I can see two probable reasons:
Incorrect installtion of GUI , pls try reinstalling the GUI and then try
Kernel upgrade but this solely depends on the current level and defer for further investigation.
Best Regards
Umesh

Timeout during allocate of Vertex RFC

Hi Guys.
Im facing this odd issue after an offline backup is completed and brings the system.
As you can see the Vertex RFC is no longer working and displays a timeout issue after a Sales programs tries to reach it.
Also when testing the RFC is unable to initialize.
M *****************************************************************************
M *
M * LOCATION    SAP-Gateway on host etgrws01.entegris.com / sapgw20
M * ERROR       timeout during allocate
M *
M * TIME        Tue Dec 28 16:43:08 2010
M * RELEASE     640
M * COMPONENT   SAP-Gateway
M * VERSION     2
M * RC          242
M * MODULE      gwr3cpic.c
M * LINE        1854
M * DETAIL      no connect of TP /boltons/D01/vertex/3.3/TransLink/verrfc from
M *              host etgrws01.entegris.com after 22 sec
M * COUNTER     6378
M
A RFC 1448 CONVID 40614370
A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPECMINIT
A RFC> ABAP Programm: CL_XTAX_RULES_RFC=============CP (Transaction: VA02)
A RFC> User: VMESENBR (Client: 200)
A RFC> Destination: VERTEX (handle: 3, , )
A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
[abrfcio.c    7933]
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1464
CPIC-CALL: 'ThSAPECMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
DEST =VERTEX
HOST =etgrws01
PROG =/boltons/D01/vertex/3.3/TransLink/verrfc
[abrfcio.c    7933]
That /boltons/D01/vertex/3.3/TransLink/verrfc is located on the same server as the SAP application, so i cannnot figure out why is showing partner not available/timeouts, when is pinging a program on the same server.
I have tried restarting the Dispatcher
rfc/use_gwstart =1
Increased CPIC timeout value gw/cpic_timeout =120 (Increased CPIC timeout)
I have also searched thru these notes but still no luck
Note 581509 - Reasons for timeout during allocate
Note 638701 - Starting RFC servers takes too long
Note 948636 - Starting executables locally using RFC
The only workaround for this, is restarting the SAP Application, in order to have the RFC working again, but this seems an overkill to fix an RFC Ping Issue.
All ECC Systems have the same program version and configuration but only Dev system is facing this.
The whole point of this, is why when the system is shut down in order to perform an offline backup causes this, and the only way to fix this, is shutting down/start up the system again.
If you have some ideas of what could be causing this, it's would be highly appreciated.
Martin

Hi Martin,
We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
Your help on this is greatly appreciated.
Thanks much!
Best regards,
Cyanna

BPM Sync/Async Scenario: error: "Timeout condition of pipeline reached"..!

Hi,
I am doing Sync/Async BPM scenario.
-> Receive message and process and response back to the sender.
Sometimes it will correct correctly. Sometime the message will come and stay in XI and fails with error
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I observed that the messages will stay in transaction "SXMS_SAMON" . and will fail after sometime.
What might be the reason. ? what need to do to stop these kind of errors?
Thanks
Deepthi.

Hi Praveen,
Webservice <--> XI -->BW .
BPM :
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoBW)->Send(Send Response) ---> stop.
Messages are getting struck in SMQ1 and SM58 at these three points.
1. Message comes and stays in SXMB_MONI in status "Log Version"
The messages are stuck in SMQ1 in READY status without doing any processing.
XBQO$PE_WS90100002 WORKFLOW_LOCAL_100 1 READY 26.02.2009
Once I push the queue by Activating/Unlocking, it will process.
2. when it is trying to send the message to R/3 (Backend system) it is waiting in SM58 with below entry.
WF-BATCH SWW_WI_EXECUTE_INTERNAL_RFC WORKFLOW_LOCAL_100 Transaction recorded
Manually I execute LUW to push it. Once I done the message will go to R/3 system and Response mapping also complete.
3. Again it is waiting at SM58 with below deatails while sending the response to sender.
PIAFUSER SWW_WI_COMP_EVENT_RECEIVE_IBF WORKFLOW_LOCAL_100 Transaction recorded
we are again manually execute LUW. Once we done the response message will go back to Sender.
Any Idea to solve this..?
Thanks
Deepthi

BPM Error: Timeout condition of pipeline reached- After transporting to Prd

Hi,
I am doing Sync/Async BPM scenario.
-> Receive message and process it and send to BI and response has to send back to the sender.
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoR/3)->Send(Send Response) ---> stop.
It is working correctly in Test system. We transported to production and we are getting the below error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I crossed checked with the test system configuration and evything looks similar. Moreover there are someother Sync/Async BPM scenarios which are all working perfectly.
Kindly help me , What might be the reason. ?
Thanks
Deepthi.

Some of the trace:
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="SA_COMM">
<Trace level="1" type="T">Start Sync/Async Communication</Trace>
<Trace level="1" type="Timestamp">2009-08-17T04:48:09Z AUSNSW Starting Processing</Trace>
<Trace level="1" type="T">Pipeline Timeout: 17.08.2009 15:08:10 AUSNSW</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface OS_Payment</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/FOC/DirectSales/Payments</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface AS_Payment</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/SAP_PI/DirectSales/Payment</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>

CLIENT_SEND_FAILED 500 Timeout Error

Hi Guys,
i am getting below error in PI MONI, can any one please help me how to resolve this isuue.
This interface is File to Proxy(ECC).
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Timeout</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Timeout) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks,
Siva.

Hi,
Is your scenario synchronous?
Did you get a chance to look at below links:
Re: CLIENT_SEND_FAILED for sync calls
INTERNAL CLIENT_SEND_FAILED Internal Server Error 500 Error while sending b
Regards,
Naveen

Synchronous Call Timeout but the PO still created in ECC.

Hi PI Expert,
I have problem with synchronous call (Web Service -
> RFC). Sometimes if the processing time in ECC take longer time the webservice will throw exception timeout but then the processing stil continue in receiver communication channel until success.
So if you use SXI_MONITOR you can see 2 transaction, Sender web service error timeout and RFC success.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Timeout</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error while sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
But the RFC communication still able to continue until succes. Supposed to be both error if the sender communication channel timeout ?
- <ns0:Z_MM_STO.Response xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<EX_RESULT><RETURN><item><TYPE>E</TYPE><ROW>0</ROW><PARAMETER>POHEADER</PARAMETER><MESSAGE>0100905701</MESSAGE><MESSAGE_V1></MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><SYSTEM></SYSTEM></item><item><TYPE>E</TYPE><ROW>1</ROW><PARAMETER>POHEADER</PARAMETER><MESSAGE>External document number 100905701 already assigned</MESSAGE><MESSAGE_V1>100905701</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><SYSTEM>ECPCLNT300</SYSTEM></item></RETURN></EX_RESULT>
</ns0:Z_MM_STO.Response>
Please advise is that anything that i can check ?
Thank You and Best Regards
Fernand.
Edited by: Fernad Lesmana on Aug 23, 2010 7:59 AM
Edited by: Fernad Lesmana on Aug 23, 2010 8:00 AM
Edited by: Fernad Lesmana on Aug 23, 2010 8:01 AM

Hi Fernand,
The last parameter (syncMessageDeliveryTimeoutMsec) you mentioned is for general timeout setting of RFC receiver calls (see note FAQ RFC Adapter: https://service.sap.com/sap/support/notes/730870). That one seems high enough in your case
xiadapter.inbound.timeout.default is the default setting of 180 seconds, which is normally the default for all timeouts in PI.
Normally in icm there's a setting for the http port (e.g. something like icm/server_port_x prot=http,port=500xx,timeout=180,proctimeout=180)
Can you confirm that one is higher then 60 seconds? (Just saw you saying something about 60 seconds before editing the posting)
Best wishes
Sebastian
Edited by: Sebastian Simon on Aug 26, 2010 1:24 AM

HTTP_RESP_STATUS_CODE_NOT_OK -- 500 -- Timeout

Hi Guys,
There is 1 msg gone to error status with below error .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Timeout</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error when sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
This error happened only once and again all the msgs for the same interface processing successfully.
Scenario is: proxy --> XI --> IDoc(Asynchronous)
Could any one plz let me know wht could be the problem that time?
Thanx,
Kumar

Hi Kumar,
as far as I understood your problem, the Timeout error occurs when sending from
ABAP Proxy (?) to the Integratin Server, correct?
Please check with transaction SMICM on both sides the trace file and the parameter settings for the http protocol.
It could be that your message is quite large, and therefore the default values of 60 seconds are to small defined.
In general for Timeout settings, there is a nice unit called "Timeouts in XI" in the XI3.0/XI7.0 Troubleshooting Guide available at
<a href="http://service.sap.com/instguidesNW70">http://service.sap.com/instguidesNW70</a> > Operations
- Process Integration: <a href="http://Troubleshooting Guide - SAP XI 3.0/SAP NW 7.0">http://service.sap.com/~sapidb/011000358700005909032005E.PDF</a>
Extract from the guide, which should be also valid for your case:
ICM 402 timeout for http client calls (IS -> AF): ICM_HTTP_TIMEOUT
Value for all ports: icm/keep_alive_timeout (Default: 60 seconds)
Value for specific ports:
icm/server_port_0 = PROT=HTTP,PORT=<icmhttpport>, TIMEOUT=30, PROCTIMEOUT=900
PROCTIMEOUT not set > TIMEOUT is used > TIMEOUT not set > icm/keep_alive_timeout is used
Default: TIMEOUT and PROCTIMEOUT not set >icm/keep_alive_timeout is used
In the event of errors, increase the PROCTIMEOUT value for the HTTP/HTTPS ports used.
Do not increase icm/keep_alive_timeout or the TIMEOUT value as this would lead to a higher resource consumption.
For more information, see SAP Note 824554 - ICM timeout parameters.
Best regards,
Silvia

Handle WSDL data connection timeout during PDF generation

I have created in LiveCycle Designer XDP template. In template i defined WSDL Data connection. For data loading i call xfa.connectionSet.WsDataConnection.execute(0).
For PDF generation i created LiveCylce process and use generatePDFOutput component.
If WebService works output service generates document with all data - OK.
If i turn off webservice and run process ouputservice generates PDF document with empty fields. Is where any possibility to raise execption to calling process if WSDL connection timeouts or gives SOAP fault error in response?
I want catch web service errors in process and do not generate PDF if some webservice used in PDF template is not accesible during generation.

Hi Martin,
We are experiencing the same issue with SAP/Vertex. Can you let me know how you resolve this? Did you change the SAP gateway timeout parameter? If so, which one is it?
Your help on this is greatly appreciated.
Thanks much!
Best regards,
Cyanna

User getting locked while sending message sync via BPM. Please help

Hi Experts,
I have a sync - sync scenario where I am sending data synchronously from webservice to a sync RFC FM. I am using BPM and in BPM I have three steps
1. Receive step - Opens Sync-Async Bridge
2. Sync Send step
3. Send step - Closes SYnc-Async bridge.
This BPM solution is same as that give in the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
When I test this scenario I am getting
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
When I check the "Status monitor for Sync/Async communication" via SXMB_MONI, I found that my message is listed there with BPE status = "Wait".
On double clicking my message I found that there is an error " User is locked. Please notify the person responsible".
Why is my BPE struck in "Wait" stage and user is locked?
What am I doing wrong? Am I missing any settings in SOAP sender communication channel?
Please help me in resolving this problem.
Regards
Gopal

Hi,
Few months ago we had also problems with "locked user" in XI, in our case XIAPPLUSER was sometimes (b)locked.
Perhaps note:
721548 Changing the passwords of the XI 3.0 service users
will help you.
We removed and entered the service users again, with the password in CAPITALS and language blank.
After that our problem was solved, I hope yours too.
Regards
Jack

SAP BW timeout

Similar Messages

Maybe you are looking for