Error in Message Monitoring

Hello,
When I enter to "Runtime Workbench" -> Message Monitoring, I choose:
is.<instance_number>.<server_name> and press "display" button, then I get an error:
"Unknown error: javax.ejb.CreateException: getJCOCLient
(String,String)"
When I choose af.<sid>.<server_name> in the combo box, the problem doesn't exists.
Please Advice,
Dimitry Haritonov

Hello,
Finally I solved the problem. Somehow adding parameter:
-Duser.language=en
solved the problem.
instruction (note 768457):
==========================
"...Enter config tool,drill down to Instance_[ID] -> server_[ID] and add the parameter on the right side in the section 'Java parameters'"
After adding parameter, I stopped and started XI. Then the problem disappeared.
Good luck,
Dimitry

Similar Messages

System error in message monitoring

Hello,
Scenario is proxy to database. Status seems to sytem error in message monitoring. Error detail is In audit log of message details as belows:
JDBC Message processing failed, due to Error processing request in sax parser: Error when executing statement for table/stored proc. 'If_test ' (structure 'STATEMENT'): java.sql.SQLException: ORA-00936: missing expression
I should resent this message content. When i press Resend tab in message monitoring, error status is not being changed.
Thanks in advance

Hi,
Check the payload received is correct or not in this case ...
Take payload and check at mapping level...
if you are using insert or update statement you can enable log at the receiver jdbc channel in advance mode(logSQLStaement to true) to see how the statement is getting framed ...
HTH
Rajesh

System Error in Message Monitoring while it shows checked flag in SXMB_MONI

Hia,
We are working on ABAP Proxy --> SAP PI 7.1 --> SOAP (Asynchronous Scenario).
(ECC -> PI -> Legacy CRM)
I have following queries:
1. While sending messge across to Legacy system, we can see CHECKED flag in SXMB_MONI but there is System Error in Message Monitoring. When checked legacy system is unable to receive any message. Cannot understand the issue.
2. Is there any way to check in PI system whether the message has reached Legacy System other than making scneario synchronous?
Regards

System is getting connected and able to send asynchronous messages to legacy system. But getting following error while sending synchronous error:
2010-05-10 13:15:05     Information     Delivering to channel: CC_SOAP_SOReject_Out
2010-05-10 13:15:05     Information     SOAP: request message entering the adapter with user J2EE_GUEST
2010-05-10 13:15:05     Information     SOAP: completed the processing
2010-05-10 13:15:05     Information     SOAP: continuing to response message f33caa90-5c07-11df-c659-96d147c2ff0f
2010-05-10 13:15:05     Error     SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.. Setting message to status failed.
2010-05-10 13:15:06     Error     The message status was set to FAIL.
I have already checked Data Structure and it is fine.
Regards
In this scenarios we are using XSLT mapping using CDATA.
Please suggest solution.

System Error in Message Monitoring -Proxy to SOAP async scenario

Hi All,
My scenario is ABAP Proxy---> SAP PI 7.1 ---> WEbService(Asynchronous SOAP ).
In Moni message is showing successful Flag, but message has got stuck in "system Error" at message monitoring.I can't see any Audit log in Message monitoring .
but in related Soap Receiver communication channel i can see the below Error
"2010-08-11 09:54:15 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Information SOAP: sending a delivery error ack ...
2010-08-11 09:54:15 Information SOAP: sent a delivery error ack
2010-08-11 09:54:15 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005. "
Please help , what could be the problem.
Thanks in Advance.
Jyoti

Hi Jyoti,
>Is there any specific setup required at Provide side while moving to Acceptance system
I dont think so.
Please compare EXACTLY the settings of the two Comunication Channels, especially the server path. Please assure that you ve sent exactly the same message content from Acceptance system.
Regards,
Udo

Error in message monitoring while creating new record in R/3

Hi All,
I am getting the following error in message monitoring while creating a new record from SAP Mobile client.
Service name: Validation_Service
Message: BackendKeys are not filled in table HEADER returned by getDetails
I am passing some random number from Client to SAP R/3 create function module.
When i pass the same value in create FM as in message monitoring. I am able to create the record successfully,
Corresponding to newly created record, i can see the data in getdetail header also.
Not sure why this error is coming.
Appreciate your help!!
Thanks & Regards
Devendra

The CREATE FM should not only create the entry, it should also EXPORT the key that it uses to create the entry. Is it doing that?
i.e. the CREATE signature is usually something like:
CREATE_BLAH
IMPORTING header TYPE header_row
EXPORTING key type header_row-key_field.
So the 'key' here should be filled by the FM and returned to DOE.

Wrong port in FTP receiver adapter - no errors in message monitoring?

Hello all
We're on XI 3.0 SP16 and have created / configured a HTTP XML -> XI -> FTP Server scenario. In the receiver comm. channel (ftp) we had specified a wrong port number and always wondered, why we never got errors in message monitoring. Everything seemed to be processed correctly... but no file arrived on the FTP server (receiver) side!
After correcting the wrong FTP port number in the receiver FTP comm. channel everything went fine.
We now encountered a similar problem with a RFC receiver adapter. We're using it in another scenario HTTP XML -> XI -> RFC to SAP R/3 (4.7).
For some reason it died (red status in adapter monitor) and it was no more possible to do RFC calls from XI to SAP R/3 (normal RFC adapter, NO proxies).
In XI message monitor everything seemed to be ok but no message arrived till SAP R/3. Nothing in any queue...
After deactivating and reactivation the RFC receiver comm. channel it worked again BUT ALL PREVIOUSLY SENT messages seem to be lost.
Is it really the way it works? Does XI integration engine at runtime NOT catch whether or not a RFC or FTP receiver adapter died, thus is not able to tell somewhere in message monitor that a message could not be delivered at all?
I'm really confused here but hopefully I simply don't understand some easy principles to take into account...
Our SAP R/3 is on rel. 4.70 with Web AS 6.20. The XI 3.0 plugin is not installed. Do we need to go with server proxies there and use QOS = best effort?!?
Thanks for some suggestions.
Best regards,
Renaud

Hi Michal
Thanks... works great for normal XML based messages!
Now, what if I wanted to pass binary files from one ftp server via BPM to another ftp server in order to enable the transport acknowledgment?
The files polled from ftp server using the ftp sender adapter are all in binary format (ARJ). No xml data in there. How should the message format look like in BPM for the receiving step? Or: how to make sure not to loose the binary content when passing through BPMs?
I need this sort of scenario because of the tansport acknowledgment and because I need to have some sort of message splitting (send the binary file over to a second ftp server and additionally send some kind of info message to SAP R/3 regarding thin binary file).
BTW: in the MessagingSystem/monitor/monitor.jsp I do not see sender / receiver information. Is this normal? It's quite of a bad thing to look inside each message in order to find out what message I'm having in front of me...
Thanks a lot for your support and patience!
Kind regards,
Renaud

"Error in message monitoring in runtime workbench"

Hello All,
I have an error in message monitoring in runtime workbench.
We have installed PI7.0 and it should run on port 50000.But it is running on port 50100.
Please suggest what are the steps involved to resolve this problem.
Thanks and Regards
SAN
null
k san

San,
Can you please copy / paste error message.
Also check if you have set correct port in Exchange profile under Runtimeworkbench.
Nilesh

Error in Message Monitoring in XI.

Hi All
Affter clicking Message Monitoring in RWB there is DETAIL button above the message listed when i am trying to click on the detail button it shows the error like "The page cannot be displayed".
pls help me .
Thaking you in advance.

Hi Hiren,
Plz check below mentioned blog. It will help you out:
<a href="/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi:///people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Subhasha

Re: Error in mesage monitoring

Iam getting this error in message monitoring
my sender is idoc and receiver is jdbc.
Unable to execute statement for table or stored procedure. 'EPMFA_ORD_HST' (Structure 'EPMFA_ORD_HST_Insert') due to java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated.
JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'EPMFA_ORD_HST' (structure 'EPMFA_ORD_HST_Insert'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated....

Hi ,
Check your test data,the problem with data,the error could be because of the length of filed defined in data base is less than your test data filed length.
your database table has a colum named 'EPMFA_ORD_HST' of type VARCHAR(30),Now if you will try to insert a string of length greater than 30, the program will throw this type of exception.
Regards,
Raj

'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>

How to delete the error message in the Web page Message Monitoring

Hi All:
I'd like to ask a question.If there is error message in the T-code sxmb_moni->Monitor for Processed XML Messages,I can cancel the error message manually and archive the message. After that,I can delete the message from "Monitor for Processed XML Messages".
But after those operation,I find in the web page " Message Monitoring", there are still messages in the "Messages from Component Integration Server and/or Adapter Engine".
How can I delete those message both successful and error.
Thanks All
Elliott

Hi Elliot,
SXMB_ADM
Integration Engine Configuration
Specific Configuration
Category: DELETION
Parameters: PERSIST_DURATION, PERSIST_DURATION_ERROR
Subparameters: SYNC, ASYNC
Change "Current Value".
and execute your delete job again!
Regards,
Udo

Error in Seeburger Message Monitoring

Hi ,
I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file.
I m getting error in seeburger message monitoring with status as "Could not send ansynchrone MDN to partner - url not set!". can anybody tell me whats the reason behind it,where it went wrong.

Really didn't understand your scenario. That sentence makes no sense:
"I m using Seeburger as Sender R/3 System.and the receiver is Xi.as an idoc file."
But what I understand from the error message you have provided...................
if you are using Seeburger AS2 adapter as Receiver Comm Channel..........then there is definitely some cofig error is settings for MDN acknowledgement.
Under Parameters Tab:
You must have set the following parameter
MDN Mode = "ASYNC"
And has not provided the following parameter just below it :
Receipt Delivery Address
This parameter should have value: the URL of your own AS2
server where the asynchronous MDNs are
to be delivered.
Hope this solves your problem.
Regards,
Suddha

SOAP error in audit log of message monitor

Hi,
I am using RPC wsdl file for idoc-xi-soap services. When I am doing the testing for the scenario in the message monitor I am getting the following audit log:
2008-02-29 15:21:48 Success Message successfully received by messaging system. Profile: XI URL: http://EMHBSSAP05.bekaertcorp.local:56600/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-02-29 15:21:48 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-02-29 15:21:48 Success The message status set to DLNG.
2008-02-29 15:21:48 Success Delivering to channel: ZCC_Material_SOAP
2008-02-29 15:21:48 Success MP: Entering module processor
2008-02-29 15:21:48 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2008-02-29 15:21:48 Success Message successfully put into the queue.
2008-02-29 15:21:48 Success The message was successfully retrieved from the receive queue.
2008-02-29 15:21:48 Success SOAP: request message entering the adapter with user J2EE_GUEST
2008-02-29 15:21:48 Success SOAP: completed the processing
2008-02-29 15:21:48 Success SOAP: continuing to response message a9ea9a30-e6d1-11dc-c8bd-001a4b0658c1
2008-02-29 15:21:48 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
2008-02-29 15:21:48 Success SOAP: sending a delivery error ack ...
2008-02-29 15:21:48 Success SOAP: sent a delivery error ack
2008-02-29 15:21:48 Success Acknowledgement creation triggered for type: SystemErrorAck
2008-02-29 15:21:48 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
2008-02-29 15:21:48 Success Acknowledgement creation triggered for type: AckNotSupported
2008-02-29 15:21:48 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
2008-02-29 15:21:48 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:.
2008-02-29 15:21:48 Success The message status set to WAIT.
Can anybody suggest what is the meaning and root cause for the error:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
Thanks & Regards
Prabhat

go to sxi_monitor and get the inbound message, later go to IR an do a TEST mapping.
any error occur?if yes, paste it here
generally soap fault o soap exception relate to an error from WS side,but before say nothing check you have all data and transformation OK.
hope it helps

In Message Monitoring Message showing Error:Message

Hi
Can anyone solve this problem.Its urgent for me.
My scenario is IDoc->XI->FILE
The file i am trying to generate is an xml file which i am dropping in XI application server using File system.
The problem is when i am going to see the message using transaction SXMB_MONI the perticular message interface is showing waiting for acknowladgement status .
But in message monitoring in runtime workbench the it is showing following status:
Adapter Engine
<b>Holding</b>
18.11.2005 05:42:09
CORP_SAP_DR2_030 http://limited.com/usa/sap_appl/retail/VendorsSAPAPOToMANU
MIIA_Create
BS_MANU
I am in SP14.
Also the output xml file is not getting created in the XI application server.
Please let me know the solution.
Thanks
Debraj Roy

hi debraj..
is ur mesage ie sxmb_moni in red staus or scheduled status...??
if in scheduled cud be errors with queues ...delete ur queues with tcodes : smq1 and smq2...
and also hopefully u must have configured ur idoc correctly..
https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
regards..
vishal

Jdbc adapter error on confirmation message in message monitor (rwb)

I have the scenario iDoc -> PI 7 - > jdbc (AS400 odbc driver).
When I do INSERT statements, the data is stored in the Database and the RWB message monitoring shows status Successfull.
However, for every insert, an other message shows up in the message monitoring with reversed Sender and Receiver (so it looks like a confirmation message is trying to find its way back to XI). This message first is is Status "Waiting", and after some time gets in Status "System Error".
As I am not expecting any responses in my XI configuration (as I have no place to send them to), I want to stop these messages showing up in the Adapter Engine (as there will be many Error Status messages that are of no interest to me).
How can I stop these messages, or what should I do in XI to process them (and dump them in my receiver determination). I have NO BPM involved .

Hi,
For each open connection a entry is made j2ee stack.So when the it reaches to max and execption is thrown.
In Jdbc adapter configuration -> advance mode -> Set -> Disconnect from the database after processing each message.
Should solve the prob
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Error in Message Monitoring

Similar Messages

Maybe you are looking for