Urgent - Messages in RWB in "System Error" status - Resending

All,
I am trying to resend the messages in Message Monitoring of RWB which are in "System Error".
Message selected and Clicked on resend and it would not ask my password.
We are on SP19 of XI 3.0. Is it something new with the SP19?
I am pretty much sure that it used to ask for password earlier. And we dont have SSO (single sign on) enabled.
reg,

Naveen,
Have you seen this weblog:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also if you give the password once you dont need to give again. So that might be the reason why it is not asking you. Close all your browsers and open once again and give a try.
---Satish

Similar Messages

SAP PI Message Cancellation Alert - Message does not have restartable error status

Hello SCNers
Version: 7.1
Scenario: File --> PI -->SOAP
We have a situation where a PI message in Integration Engine shows error status.We want to cancel the message in IE but are unable to do so.
On clicking Cancel for this message in SXMB_MONI, we are receiving an alert "Message does not have restartable error status".
In SXMSPMAST table, value for ITFACTION is DEL.
We do not want to run report RSXMB_DEL_TO_ARCH, that would change status of all messages with DEL status to ARCH.
Is there a way to Cancel or Change the Status of this single message?
Regards
Sudheer

Hi Hareesh,
Tried that too, but to no avail.
Strangely, the log shows NO_ERROR_STATE for the cancelation of this message thru RSXMB_CANCEL_MESSAGES.
But in SXMSPMAST table the status of this message is 14 (System Error - Manual Restart Possible).
Regards
Sudheer

I cannot open my itunes, I keep getting message, saying Itunes exe-system error. The progam can't start because SVCR80.dll is missing from your computer.?

I cannot open my itunes, I keep getting message, saying Itunes exe-system error. The progam can't start because SVCR80.dll is missing from your computer.?

Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
(99807)

I am getting an error message Aps Daemon exe system error 1cud49dll...what can I do to fix this???

I am getting an error message Aps Daemon exe system error 1cud49dll. I cannot reinstall itunes...help please!!!

See Troubleshooting issues with iTunes for Windows updates for tips on repairing the iTunes installation.
tt2

'System Error' status at Message Monitoring( HTTP to FILE )

I have created a scenario HTTP to FTP. I sent message to XI server using the HTTP Client.
After sending the message I am getting the response at browser.
Result:
http-Status: 200 Message accepted
Payload:
But when I look in to the Message monitoring at RWB, I am getting the message status as
System error. while going to the details i can see below error category.
Error Category MAPPING
Error Code EXCEPTION_DURING_EXECUTE
(Is the password different for port 50000 and 8000)
Please help me to solve this issue.
Thanks in Advance,
John

This is the trace message that I got for this error
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:72) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) 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:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) 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:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>

"waiting" and "system error" status cannot be resent in rwb?

Hi,gurus:
In RWB->MESSAGE MONITORING,I can't resend or cancel the messages with the status " waiting" and "system error".
when I clicked "resend" button,it asked for user and password.After I was authentificated,the system didn't resend a message. Have you ever met this issue?
By the way,I could resend the error messages before.
Thanks in advance.

Hi,
I checked the note 1233918,and it talked about the same issue.
But the solution is as follows,which I don't know what to do.(Our PI version is PI7.0 SR3 SP14)
Symptom
When the first message for a managed system is cancelled or resent, after pressing ok in the logon pop-up nothing happens - message is not resent or cancelled. The logon data is correct, since subsequent resend/ cancel works without further logon request. Another symptom is cancelling or resending a wrong message, when using the filter mechanism in the table. E.g. the table displays messages A, B, C, D. If message C is selected and after that the filter is set so that message C is hidden from the filter selection, when selecting message D and trying to resend/cancel it, message C is cancelled/resent (the hidden one, previously selected) and nothing is happening with message D.
Other terms
NWA, PI, Message monitoring, resend, cancel
Reason and Prerequisites
The UI Proxy connection was not obtained properly. Another reason - TableAccessories was not invalidating the nodes properly. Also after filtering the result list, resend/cancel was taking wrong message Ids.
Solution
For SP5 install LMNWABASICCOMP05P_1.SCA or higher patch level.
For SP6 install LMNWABASICCOMP06P_1.SCA or higher patch level.

Set Message in BPM to System Error - Manual Restart Possible ?

Hello,
I'm working on a scenario where two idocs are merged in a BPM. The next step is sending the message in a synchronous RFC (BAPI) to a SAP R/3. Is it possible to set the merged message to the message status 'System Error - Manual Restart Possible' in the SXMB_MONI, when the BAPI returns an Error message?
When it's not possible, is there an othe possibility to sent the message again, without involving the source system?
Thanks in advance
Matthias

Hi,
It would be better i think if you use the concept of raising an exception in your response mapping
please refer:
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
in the response mapping you can check the condition for the responce code from RFC.
Ranjit

How can i resend messages which failed with System Error

hi Can any one please help me with 3 messages stuck in adapter engine ,they are failing with system error,I tried to resend them but still they failing with the system errorXI_J2EE_ADAPTER_XI_HANDLER.so can any body help me with this problem .
thanks
p

Hi,
Check the threads..
[File (xml)>>xi>>IDoc;
[Problem in Webservice -> XI -JDBC;
[Problem in JDBC Reciver Channel;
Regards,
Prakasu

Message in Message Monitor/ RWB stay forever in status DLNG

Hi,
We have a problem with a Message inside our J2EE Adapter. The message remains in the status DLNG forever.
We use SAP XI 3.0 Service Stack 13.
We have the following scenario:
When sending messages via the Oracle JDBC connection to the Receiver-Service, the
message keeps the delivering status and never fails if the message
fails on the database level. In this particular case, the message failed on the DB level due to a misconfigured trigger and due to unique constraints. The state of the messages can be resolved by cycling the entire J2EE engine.
How can I handle such a message that stay in DLNG status?! And why is it hanging there? I cannot restart the message, I cannot stop it I also cannot cancel it out of the RWB.
regards
Nesimi
Message was edited by: Nesimi Buelbuel

any solution to the problem mentioned here ?
we are also facing the same issue.
have tried all kinds of restarts.
any further help will be appreciated.
thanks,
gaurav

Cancel System Error Messages from RWB

Hi All,
I have nearly 3000 messages those were got System Error in Integration Engine process, but when i check messages in SXMB_MONI all are success and written to target folders also.There is no problem absolutely.
Now i just want to cancel those System Error messages from RWB--Message Monitor to keep system green and do not want to see those system error messages again.
Iam not able to cancel those messages from RWM, it is saying that User and pwd incorrect but iam providing correct one only.
I went to details of that system error message from Message Monitor, i took message id and filtered with that in SXMB_MONI. i got the message with error state.Iam able to cancel that from MONI but not from RWB which is fine and disappearing from RWB list.
the thing is i can't copy each and every message id by opening details button for every message
How can i proceed for this. please advice me
REgards

Hi Ravi,
For example iam able to see system error message in RWB--Message Monitor under Integration Engine at 9:30
when i execute SXMB_MONI for the same time and see, there is no error message for that able to see success.
When i took message id from RWB--message monitor and filter that in MONI means it is showing me the error message.
I can able to cancel it from MONI which is fine. but this way i have 3000 messages in RWB--Message monitor under IE.
How to copy and paste then filter those error messages in MONI???this is pain process to copy each and every one by one
Iam not able to get those if i filter with the status group as System Error manual Restart Possible criteria
Regards

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

Error message without error status matching

Hi Gurus,
I have a error message from process chain as follows:
Failure Group EREC01 Special FULL - Job 1 Process Group EREC01 Special FULL - Job 1 Of Type Local Process Chain Has Status Ended with errors (Process Chain Encapsulate EREC01 GRP) It is now 21:19:54 on 05/05/2010 (time zone PST) Current Process Chain Run: D80JW1WN91Q0OEZ3K0ZGF3MS5 in System BIP (Host biprd03)
but when I get into rspc to check the status for this running, it shows green for status in the log view. why does this error message come up without any error status matching?
Many thanks

Hi,
Please check if your are looking the correct process chain and in correct transaction. you may look at the logs of this process chain in RSPCM and not in RSPC.
If you can not find this error status message in RSPCM, them check SM37 and SM12 by providing the proper timeinterval for the message you got.
Regards,
Pratap Sone

Messages stuck in TO BE DELIVERED status

Hi !
Suddenly, whenever a message has to use the File Adapter, no mather which communication channel is to be used, the message is stuck with the "TO BE DELIVERED" status.
These messages, all have SUCCESSFUL status in the SXMB_MONI. The problem is in adapter engine. ALL have NO errors in their Audit Log. Because the problem is in adapter engine/framework, obviously queues at SMQR/SMQ1/SMQ2 are emtpy. ALL have QoS = EO (no eoio queue is used, NO predecessor messages are stuck with system error).
This occurs no mather which adapter is the sender (RFC, File, etc.)
The audit log is:
2008-04-10 16:59:34
Success
Message successfully received by messaging system. Profile: XI URL: http://xxxxxxx:yyyyy/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-04-10 16:59:34
Success
Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-04-10 16:59:34
Success
Message successfully put into the queue.
If we try to resend the message using the "resend" button in RWB, the message keeps in the TBDL state and the only difference is a new "success" entry in the audit log saying that:}
"Success | Admin action: Trying to redeliver message".
We already refreshed the cache and restarted the Java stack.
Any clues?
Thanks !
Regards,
Matias.

Hi,
Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort means Asynchronous). TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
The MS returns HTTP 200 to the Integration Server only if this was executed successfully. In this example scenario, status TO_BE_DELIVERED should not appear since we assume that the IS has called the servlet successfully.
The status is updated from TO_BE_DELIVERED to DELIVERING when the message has popped out of the receive queue and the event handler lookup was successful, so there is a small gap where TO_BE_DELIVERED could remain in the message monitor, although it was delivered from IS successfully.
Regards,
Srini

Message struck in adapter engine with status Hold

Hi,
In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
Regards,
Krishna

Hello,
Below is some information on how to resolve this type of issue:
1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
4 - Sort the messages in ascending order based on the Sequence no.
5 - Check the predecessor message of the first message in status "HOLD"
Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
a - Predecessor is in Failed State/System Error : Cancel/Resend the
first message in status HOLD after this. Then the remaining messages
can be cancelled/resent.
b - Predecessor is in DLVD state(delivered state) : First Holding
message can be resent/cancelled followed by the others.
c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
predecessor message failed and correct the reason for the failure.
Then resend the predecessor message and then cancel/resend the
remaining HOLD messages. Alternatively, you can directly try
resending this NDLV predecessor message and see if it goes. If it
goes, then the remaining HOLD messages can be resent/cancelled.
Another option could be to cancel this NDLV predecessor message so
that it goes to FAILED state and then cancel/resend remaining HOLD
messages.
Regards,
Sarah

System error in MDT

Hi Experts,
we got Interface Proxy to JDBC. the bach ground runs in SAP every day in the night and send the data to XI, Then XI will write to database.
In SAP back ground job runs successfully and send to XI. in XI successfull in sxmb_moni also.
but the message end up with system error in adapter engine.
when i restart the message in the morning it went through successfully.
Audit log is like this:
Audit Log for Message: 72737178-bcf0-484a-8462-68c8a7e7f1b0
Time Stamp Status Description
2008-01-29 21:10:43 Success Message successfully received by messaging system. Profile: XI URL: http://sappxi:58000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2008-01-29 21:10:43 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-29 21:10:44 Success The message was successfully retrieved from the receive queue.
2008-01-29 21:10:44 Success Message successfully put into the queue.
2008-01-29 21:10:44 Success The message status set to DLNG.
2008-01-29 21:10:44 Success Delivering to channel: ReceiverChannel_JDBC
2008-01-29 21:10:44 Success MP: entering
2008-01-29 21:10:44 Success MP: processing local module localejbs/CallSapAdapter
2008-01-29 21:10:44 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2008-01-29 21:31:22 Success JDBC adapter receiver channel ReceiverChannel_JDBC: processing started; party , service JUSTENOUGH
Can anyone tell me is there anything problem with network related problem.
Kind Regards,
kiran

Hi Prateek,
There is no information available in audit log. there is no page available in audit log only it contains one page only, i dont why the audit log stoping there.
any input is appreciated.
Kind Regards,
kiran

Urgent - Messages in RWB in "System Error" status - Resending

Similar Messages

Maybe you are looking for