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>

Similar Messages

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

DTP error: Type conflict when calling FM - after transport to Prd

Hi ,
i have asset_attr datasource.it was working in my BW dev.
however after transport to BW prod. when i try to upload data using DTP it gives me an Abrupt error
"0ASSET_ATTR IPDCLNT030 : Type conflict when calling a function module (fiel
Message no. RSDS666"
no more information is given, & the request ends in red.
This is first time i'm using this Infoobject upload.
however all my other transaction data & other master data all are getting uploaded fine.
even Asset_text datasource is working fine.
Did anyone face similiar probs ?
can anyone guide me on this error ?
thanks
ramesh

Hi
Take a look at note 1130907.
Regards,
Chandu.

Condition doesn't work after transport to QAS system.

Hi all:
the condition doesn't work after the workflow transported to QAS system. the workflow designed has a constraint that only the creation of the document of Type M4 can trigger the workflow, but creation of Type M5 document can also trigger the workflow, could you please tell me the possible reason?
Thank you very much

Hi,
Once Try checking as pavan suggested whether the Customizing requested is transported.
To Maintain Workflow start conditions you can also maintain through SWB_COND and ensure its transported.
Regards
Narin

Delete session after error 023 and WP has reached abap/heaplimit = 40000000

Hello,
I had upgraded my system's kernel to 7.21 401 last weekend and started getting below errors.
     "Delete session after error 023" and "WP has reached abap/heaplimit = 40000000"
When I change the abap/heaplimit parameter to 6000000000 program runs without error.
This parameter value is out of max value of this parameter.
I donot want to give the parameter over max allowed value.
I also changed dbsl patch to 7.21 418 but no solution.
I searched through sap notes and scn but could not find an answer to my problem.
What could be the relation between kernel upgrade and this parameter?
Why the program was working with Kernel 7.21 316 and not working with 7.21 401?
I inserted SM21 and developer trace file below.
Can you help about the issue, please?
Thanks and Regards,
Yuksel AKCINAR
SM21:
     11:56:52 DIA 010 200 USER1 TX01          R4 7 Delete session 004 after error 023
dev_wx:
L Fri Mar 13 11:52:31 2015
L EVTSDL: Begin of FORM PROCESS_EVENT_TRIGGERED_JOBS
L EVTSDL:    Event raised: SAP_END_OF_JOB
L EVTSDL:    Event parameters: SLCA_LCK_SYNCHOWNERS            10523100
L EVTSDL:    Begin of FORM SELECT_EVENT_TRIGGERED_JOBS
L EVTSDL:      Eventhistory > There are no active profiles of criteria type 'EVTHIS'
L EVTSDL:    End of FORM SELECT_EVENT_TRIGGERED_JOBS
L EVTSDL: End of FORM PROCESS_EVENT_TRIGGERED_JOBS
L TIMESDL: CLEANUP_MUTEX try to grasp for server:
L TIMESDL: arq01_ARQ_10
L TIMESDL: CLEANUP_MUTEX not grasped (is busy)
A
A Fri Mar 13 11:56:35 2015
A WP has reached abap/heaplimit = 40000000 bytes
A
A Fri Mar 13 11:56:39 2015
A SelMemClass: heap quota (DIA) exceeded 2000000000 2000030480
A
A Fri Mar 13 11:56:40 2015
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.
A ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
C Call to DbSlRollback96 while DBIF already active in DbSlExeRead96
B ***LOG BZY=> unexpected return code 1 calling DbSlRollback [dbcon        3820]
B ***LOG BYJ=> database function ROLLBACK for connection R/3 failed [dbcon        3823]
B *** ERROR => DISTRIBUTED_TA_FAILED:
[dbcon.c      2029]
B {root-id=0050569300301EE4B2AC40086FE743BF}_{conn-id=00000000000000000000000000000000}_0
B 00: name=R/3, con_id=000000000, state=ACTIVE      , tx=NO , bc=NO , hc=NO , perm=YES, reco=NO , info=NO ,
B      timeout=000, con_max=255, con_opt=255, occ=NO , prog=
M ***LOG R39=> ThIRollBack, db_rollback ( 016384) [thxxhead.c   14956]
M in_ThErrHandle: 1
M *** ERROR => ThIRollBack: db_rollback (step 4, th_errno 18, action 2, level 1) [thxxhead.c   11560]
M {root-id=0050569300301EE4B2AC40086FE743BF}_{conn-id=00000000000000000000000000000000}_0

Hi Yuksel ,
From the trace file it seems it is a parallel processing Jobs . Has anything changed ( In terms of number of parallel background work process ) in this Job .
If this relates to only one job dont think this increased memory could be because of the kernel patching .
The only thing i could think of is the following ( 1713986 - Installation of kernel 721 (EXT) ) - The note is valid for 721 als
5.6 Dynamic work processes (NetWeaver 7.00/7.01)
The 720 and 721 kernel versions support the dynamic increase of the number of work processes at runtime. However, this function is not fully compatible with NW 7.00 and NW 7.01. To prevent errors from occurring, deactivate it by setting the following parameters:
rdisp/wp_no_restricted = 0
rdisp/configurable_wp_no = 0
rdisp/dynamic_wp_check = FALSE
rdisp/wp_max_no = Sum of:( rdisp/wp_no_dia + rdisp/wp_no_vb2 + rdisp/wp_no_btc + rdisp/wp_no_vb + rdisp/wp_no_spo + rdisp/wp_no_enq ).
Mind that rdisp/wp_max_no has the default value DEFAULT, which will add two unwanted dynamic processes if not set the number of configured, classical wp types.
Check the parameters and try again after a restart .
Believe have seen in many projects functional consultants complaining the issue is after the patch upgrade . Does this fall in that category
Thanks ,
Manu

BPM error after transport

hi all,
i get the following error after transport on Q system:
"No object type found for this message; check the activation of the corresponding process"
the trace gives me this explanation:
"could not create BPE proxy for message, no XML object definition found for message 48C56A8CD7D615EEE10000000A9E014F"
In SXI_CACHE the business process has status zero, business process and everythng else in transport is active.
So what else can i do to fix that bug?
Thanks
Stefan

HI,
Then check the error log carefully. Problem might be some else. If not try to reimport the transport with the help of BASIS.
Also check the status of check table in quality. Is it active?
All ur objects are in single TR? If not the u have to move check table TR first and then later objects TR.
If nothing works then include all the objects in another TR and transport. make sure all are active.
Thanks,
Vinod.

Queue blocked after BPM error!

Hi,
Is there any configuration steps to do in order to avoid incoming message to be blocked (Scheduled on outbound side) in the queue when there is a bpm error.
Thanks in advance,

Hi,
yes we can do through SXMB_ADMIN, SMQ1..
Outbound Scheduler (Transaction SMQS)
If the Outbound Scheduler is responsible for sending and executing these LUWs, and the logon data in transaction SM59 in the destination is incomplete, then any subsequent LUW calls might be executed under the logon data of a previous user. This occurs if the destination scheduler is already running under another user when the LUW is called and no logon data is maintained in transaction SM59. In this case, the destination scheduler runs under the user that started the scheduler (and this user's language). This means the destination scheduler runs under the wrong logon data, as does the processing of the subsequent LUWs.
Until now, destinations could only be registered in the Outbound Scheduler if the logon data (client, user, password, language) had been defined completely in transaction SM59 (if LUWs always needed to be processed under a specific user and language). Destinations with incomplete logon data could be registered only if the user and language was not important. In addition, some internal destinations (NONE/SPACE) do not allow you to enter a user or language in transaction SM59. For this reason, and for tRFC compatibility, you can only register these destinations in the Outbound Scheduler with the optional Without tRFC flag.
see below links
http://help.sap.com/saphelp_nw04/helpdata/en/1a/d2fc40b2c7f96fe10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/665f3c482a7331e10000000a114084/frameset.htm
The reason of blocking a queue
Queues getting blocked on error
Regards
Chilla..

Message Split without BPM - Error

Hi,
I am creating a message split scenario without BPM as per weblog <a href="/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible Split without BPM</a>
I am able to receive message in XI but after that it shows error in Integration engine.
Error Category : MAPPING
Error Code : GENERIC
I am able to see the message in SXMB_MONI with error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>No messages created from split mapping</SAP:P1>
Please advice.
Thanks,
Sri.

Hi Venkat,
I am not able to see sub-groupid in sxmb_moni.
Please see below the contents from sxmb_moni trace.
============================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = QN7</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-18T05:51:20Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 67F58830CE9E11DA91CD00111120E6DB</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<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">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0002</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0002</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = QN7</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-18T05:51:20Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<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="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 level="1" type="T">Post-split internal queue name = XBTO6___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = QN7</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-18T05:51:20Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<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="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<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">Mapping-Object-Id:29EB87F0231C357A8336DDEBD574EEAB</Trace>
<Trace level="1" type="T">Mapping-SWCV:0CF1E1E0C5FC11DABCB9E4A50A07012B</Trace>
<Trace level="1" type="T">Mapping-Step:1</Trace>
<Trace level="1" type="T">Mapping-Type:JAVA</Trace>
<Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_MM_filesplit_without_bpm_</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Thanks,
Sri.

BPM Error:PL_timeout

Hi all,
i am facing one error in SXMB_MONI.
The scenario is Sync-Async Bridge using BPM,request is successfully processing from XI but response case getting error in SXMB_MONI like pipeline timeout error at call Adapter.can anyone help me in this.
BestRegards
Venkatagiri

make a search on sdn this is a very common issue in sync/async bridge (using BPM) scenarios...
PL_TIMEOUT in Sync Async scenario using BPM
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true
Create BPM in synchronous mode please help

RDS 2012 R2: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the (name-of-service) service

Hi guys,
On a random base (daily, weekly) we're experiencing major log-in problems on our Windows Server 2012 R2 Remote Desktop Services farm. The VM's are hosted on Hyper-V 2008 hosts and we're not using Citrix techniques etc.
Users are reporting that they cannot log-in, the log-in sessions hangs with a blank screen when loading their user profile (e.g. Please Wait For The User Profile Service).
In the System event log of the server on which the user is logging on the following errors are shown:
Source:        Service Control Manager
Date:          23-12-2014 7:28:01
Event ID:      7011
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after 30 (or sometimes 60) seconds, the same error only another service (in random order):
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after exactly 30 seconds, the same error only another service:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxmSms service.
etcetera, with the following errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndPointBuilder service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The Portable Device Enumerator Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TrkWks service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
These errors are logged continuously.
An administrator cannot solve this since he isn't able to login in as well (console or remotely), only a hard reset of the VM is possible to use the affected server again.
I took different steps to solve this problem without any success, like:
- Installing the latest Windows updates
- Removed unnecessary printer drivers, print monitors and print processors (no local printers/drivers are installed, only Remote Desktop Easy Printer driver is used)
- Searched different forum posts, but found only hotfixes for Windows Server 2008 R2.
Can someone please help me with this annoying problem?
Many thanks!!
EDIT:
Of course is increasing the time-out not really an option here... http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx

Hi Jeroentjuhh,
1)Do you see this problem on all VM's or only on Windows 2012 R2 server?
2)Are these VMs' in hyper-v cluster?
3)Do you see event id 56 or 50? Please see the below link if it helps you to resolve these events.
http://blogs.msdn.com/b/scstr/archive/2012/02/29/how-to-troubleshoot-the-terminal-server-security-layer-detected-an-error-in-the-protocol-stream-and-has-disconnected-the-client-client-ip-and-the-rdp-protocol-component-x-224-detected-an-error-in-the-protocol-stream-and-has-d.aspx
Thanks,
Umesh.S.K

Logon Balancing error 88 and Error timeout occured for BW transaction Iview

Hello All,
I am trying to connect BW system from portal.
We are using SAP GUI for Window to launch the Transaction iViews and browser we are using is IE 7.0 and IE 8.0. I have selected the Technique to Start SAP GUI for Windows is "SAP Shortcut File". When calling the iView, it opens in the new window and asked downloads the file.
After download , I am getting connecting window and then following error
Logon Balancing error 88 :Connection to server is not possible(RC.9)
In detail error is
Error: timeout occured
Tue Aug 16 15:50:44 2011
Release 640
Component NI(Network interface), version 37 rc=-5,
Please suggest any approaches for the issue.
Thanks
Anand Kumar

Hello Vijay, Sandeep,
1) when I try the following combination in service file, I am getting given below error. if i use sapmsBWD 3600/tcp or if I do not use sapmsBWD 3600/tcp, i am getting the same following error.
sapgw97 3397/tcp
sapgw98 3398/tcp
sapgw99 3399/tcp
SAPmsBWD 52500/tcp
sapmsBWD 3600/tcp
<return>
Logon Balancing error 88 :Connection to server is not possible(RC.9)
In detail error is
Error: timeout occured
Tue Aug 16 15:50:44 2011
Release 640
Component NI(Network interface), version 37 rc=-5,
2) when I try the following combination in service file, I am getting given below error
sapgw97 3397/tcp
sapgw98 3398/tcp
sapgw99 3399/tcp
sapmsBWD 3600/tcp
SAPmsBWD 52500/tcp
<return>
Error:partner 10.21.80.23:sapmsBWD not reached
Tue Aug 16 17:22:31 2011
realease 710
Component NI(network interface) version 39
Detail Nip connect2: 10.21.80.23:3600
system call connect
Error No:10061
'WSAECONNREFUSED:connection refused'
@Sandeep: I have check the port number in SMMS transaction code: I have three port Number :3220,3320,8020.
Please any one can guide me further.
Thanks.
With regards.
Anand Kumar

SE30 - Unable to end the measurement (error number 5, Time limit reached)

Hello there,
I wish to perform a complete ABAP trace using SE30 for a program running for 4 hours. The system is R/3 4.6C.
However I got the error message below once I clicked "Back" button or F3 when the program finished after 4 hours.
Please note that ST12 is not available in the system I logged on.
=============================================================
Error message:
"Unable to end the measurement (error number 5, Time limit reached)
Message no. S7 068"
Meas. type           Fully aggregated
Session type         In current session
Status               Time limit reached
Error message text   Time limit exceeded. LIMIT: 1800000000, ELAPSED TIME: 1800957266
File user            XXX
User                 XXX
File ID              ATRAFILE
Release              46C
Version              6
Operating system     HP-UX
Number of processors ???
=============================================================
The ABAP trace results only managed to capture the first 45 minutes of the ABAP calls (due to timeout i think). I would need the whole and complete ABAP trace result for 4 hours, NOT the first 45 minutes. Is there any setting in SE30 can be set for this purpose? Note that there is no ABAP error for the program I traced.
The following link didn't answer my question as well. Hope you can provide clue in this case.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
Runtime analysis, SE30, ERROR
Thanks,
KP

Hi Kim,
The Limit is expliced on the Doc.
http://help.sap.com/saphelp_nw70/helpdata/en/4d/4e2f37d7e21274e10000009b38f839/frameset.htm
It's 4293 Actually and you set it on SE30 by change the Measurement Restrictions, tab Duration/Type.
regards.

Changing TCP/IP timeout conditions?

I am running LV8.5 across several different platforms (Mac, Linux, Windows). I am using the standard LV TCP/IP listen/connect vi's within a larger custom network communication vi, and I am trying to make my application both platform-independent and robust against various types of network and/or LabVIEW failure. I am encountering a problem after I either stop the vi which controls the network connection or kill LV to simulate an overall "crash" of the application. After the stop/crash, I want to restart the network connection vi immediately; however, I am running up against the OS's built-in "Timed Wait", in which the stale socket connection is not immediately killed. If I restart the vi too soon, the TCP/IP Listen vi returns "Error 60", since, obviously, the port I have chosen is still reserved by the system for the previous socket connection. The idea behind the "Timed Wait" is to avoid killing active sockets that just don't happen to be passing any messages within a (presumably short) period of time, but the forced wait I am experiencing prior to reconnection is not optimal for my application. Furthermore, the amount I have to wait is platform-dependent--there is a noticeable difference between Unix-based systems and Windows, for example. Among other requirements, I would like uniform reconnection behavior regardless of platform, so what I am trying to do is find a way to set the timeout condition just for this socket, while leaving the overall "Timed Wait" for the system at the default value. If the "socket timeout" value is in fact user-definable within LV, then I can determine by trial and error the optimal value that allows me to reconnect in a timely fashion while still avoiding timeouts on an active connection. But at this point I don't see how to set this value at all, since the relevant TCP/IP vi's do not have the appropriate input wires. They do have inputs that determine their own timeout conditions, but this is only for determining after what amount of time, for example, the Connect vi returns a failure to connect, not the timeout value that determines when to kill a stale socket after a previously-successful connection has been terminated.
A solution that was offered to a previous discussion board request based on the same Timed Wait/Error 60 problem was to change/increment the port for the new connection so that it is not attempting to use exactly the same resources as the old connection. I do not want to do this, since
other aspects of my program currently require the port to be set to a specific
value (in addition to the lesser concerns I have about using up the available port resourcess if the vi experiences multiple failures in rapid succession). So again, what I am hoping to find is a way to change socket-specific timeout conditions within LV. If the answer is, in fact, "LabVIEW does not support this feature", that is OK--as long as I know that for sure, then I can implement other work-arounds. For example, I've already build a "While Error...wait N seconds" into the reconnect step of my network communication vi; however, having the ability to define for myself the interval after which I can reconnect would still be preferable.
Thank you,
Kyler

Hi kkuehn,
I've talked to a few more application engineers here, and this issue sounds like it's an operating system setting. Could you change this setting? ...potentially, yes. The hard part would be in finding out where to change it for each operating system. I don't really have any paths to point you down though in your search.
There's one option you could investigate. Before trying to reopen the "stale" port, you could try closing that port at the beginning of the program.
Perhaps someone from the community, who has more operating system knowledge as to this option, could respond to this post as well.
I hope this helps,
Kevin S.
Applications Engineer
National Instruments

APEX.CONDITION.UNHANDLED_ERROR in Application after Update to 4.2

following error in an Application (working perfect in Apex 4.0.2) after Update to 4.2.0
after entering url:
Error Error processing condition.
ORA-00907: missing right parenthesis
Technical Info (only visible for developers)
is_internal_error: true
apex_error_code: APEX.CONDITION.UNHANDLED_ERROR
ora_sqlcode: -907
ora_sqlerrm: ORA-00907: missing right parenthesis
error_backtrace:
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1325
ORA-06512: at "SYS.WWV_DBMS_SQL", line 1185
ORA-06512: at "SYS.WWV_DBMS_SQL", line 1256
ORA-06512: at "SYS.WWV_DBMS_SQL", line 1294
ORA-06512: at "APEX_040200.WWV_FLOW_DYNAMIC_EXEC", line 880
ORA-06512: at "APEX_040200.WWV_FLOW_CONDITIONS", line 331
Any Ideas?
regards
Ralf

the was an missed ' in an authorization schema (SQL Query) - prior Versions of Apex ignored that error ...

Pricing error: Mandatory condition ZPRI is missing

Hi,
When creating a credit memo request with reference to the original order we get the error: Pricing error: Mandatory condition ZPRI is missing.
Checking in Analysis we get following information:
"The condition is set as an automatic condition without access sequence. Stored condition formulas may deactivate the condition.
Example: In the case of the NRAB free goods condition the minimum amount is not reached. In this case the condition is deactivated using the base value calculation formula 029."
The condition type (statistical price) is setup not to be maintained manually and we want to keep it this way.
As no access sequence exist I do not know how to add a condition record.
I am also unable to trace any condition formulas.
I have checked other credit memo requests for this sales area and none of them have ZPRI in their pricing analysis.
Could anyone help me out?
Let me know if you need more information.
Thanks in advance!
Best regards,
Geert

Hi
Can you check the pricing procedure that is triggered in the Credit memo by going to Pricing analysis..
kinly check and maintain the same.
Regards
Damu

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

Similar Messages

Maybe you are looking for