Error in trace sxmb_moni

hi,
i am seeing the following trace in the sxmb_moni trasnsaction when i exectute my report program.report program is in turn calling a proxy method to generate the xml to sen dthe dat to PI. but in sxmb_moni transaction i am getting the following trace which says interface not found.
I am wondering why interface name is coming as SI_EP003_ActionItemManagement_OA*
where as it should be SI_EP003_ActionItemManagement_OA(why an extra * is being appended)
here is the 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">COMMIT is expected by application !</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 = SRD</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = 109771</Trace>
<Trace level="1" type="Timestamp">2009-02-26T09:54:49Z 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 = DE03EB7D45EC81F1AE480050569F1467</Trace>
<Trace level="1" type="T">PLNAME = SENDER</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 = SENDER</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_SENDER</Trace>
<Trace level="1" type="T">Queue name : XBTS0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0006</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="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface SI_EP003_ActionItemManagement_OA*</Trace>
<Trace level="1" type="T">select interface namespace http://infosys.com/srm/esf</Trace>
<Trace level="1" type="T">no interface found</Trace>
</SAP:Trace>

thanks

Similar Messages

Error in Trace Level: could not create BPE proxy for message, no XML objec

Hi
We are doing a scenario of File to RFC using BPM and I am getting this errror in Tcode SXMB_MONI.
<?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>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No object type found for this message; check the activation of the corresponding process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And getting this error in Trace level
could not create BPE proxy for message, no XML object definition found for message EB32BB50610A11DC9648001321CB837D
Why this error occurs?
What could be in error?
Thanks in advance
Regards
Sami Qureshi

Hi Sami,
Check if thse threads can help u,
Error in BPE Adapter
BPM - BPE_ADAPTER errors
BPE Adapter Error
Exeception during execution error
***********Reward points if helpfull************

Detailed error message in sxmb_moni

Hi guys,
is it possible to get detailed error information in sxmb_moni like the error information in the integration repository when using the test tag
sample error message in test tab
+ns0:ZMOZPRUCK_envelope_update/ns0:ZMOZZFZT_update[4]/ns0:dbTableName/ns0:access/ns0:SPRAS.+
in sxmb_moni the error message is truncated
sample
+During mapping com/sap/xi/tf/_JDBC_ZPRUCK_2_ZMOZPRUCK_envelope_u~ a RuntimeException occurred. com.sap.aii.utilxi.misc.api.BaseRuntimeException:RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:ZMOZPRUCK_en~</+
This will save myself for copy/paste the payload in the test tab. In case of big message the Java GUI of the ESR lacks and it is impossible to test the mapping with such big messages.
any suggestions on that?
Thanks

Gugel,
Check this thread and the blog:
level of trace
/people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
Usually 1 should be good in prod.
Regards,
---Satish

Why aren't adapter errors visible in SXMB_MONI?

My client has an integration scenario that updates an Oracle database through a JDBC receiver channel. Occasionally an insert/update statement will fail. The adapter engine logs the Oracle error message, but that error message doesnt show up in SXMB_MONI. SXMB_MONI happily displays the checkered flag. You can only see the adapter error in runtime workbench.
Why arent adapter errors visible in SXMB_MONI?

> It seems odd that error messages arent propagated
> from one stack to the other so that we have a
> COMPLETE view of the lifecycle of our messages. The
> left hand doesn't communicate with the right.
You can't propagate an error which occurs in a later point of the pipeline to a previous point.
They error may occurr in the adapter, but when the message gets to the AE, the Integration Engine pipeline is already complete.
But you know, the later point can carry on errors occurred at a earlier point. That is why you can see the Integration Engine errors in the Messsage Monitoring.
It is a matter of culture. SAP consultants, in general, are more confortable with ABAP stack (SXMB_MONI) than with Java Stack (Message Monitoring). But, in this case, the Java tool is more complete.
Regards,
Henrique.

Capturing Application Error log from SXMB_Moni

Hi,
I wanted to capture the error information from Application error log from ECC sxmb_moni and forward that as email alert.
We have already alert configuration in place with alert category using standard variables. Was wondering if I have to capture application error log from sxmb_moni what would be steps involved. Please let me know if anybody has worked on this and appreciate your help on this.
Sample Error message from sxmb_moni of ECC system
MT_Fault
Error in Application System
Detailed Information
Process Order invalid
Thanks
Selvam
Edited by: Selvam_muthu on Jun 23, 2011 5:40 PM

Hi Selvam,
As the exception is raised in ECC system, alert cannot be trigger, alert will get trigger when there is a error in PI system. To raise a email, write additional code in ECC to trigger the e-mail with proper error content

After effects error ray- trace 3d initial shader compile failed

I have an AMD Phenom II X6 1055T Proccesor
16 GB in RAM
WIndows 8 64 bits
NVIDIA QUADRO K4000 ( I have this problem since I've installed this card)
after effects error ray- trace 3d initial shader compile failed

Have you added the card by editing supported cards text file as Quadro K4000 was not one of the supported cards for After Effects CS6.
Try updating the drivers to the latest . Install CUDA driver and check :
https://developer.nvidia.com/cuda-downloads

PL_TIMEOUT error message in SXMB_MONI

Hi..
I am doing File to RFC to Webservice to File sceanrio. While executing the scenario for first time i got the output. For second time execution, i got the below message in sxmb_moni.
<?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">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>
Could you please help out why this error is coming. I have done scenario correctly.

Gugel,
Check this thread and the blog:
level of trace
/people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
Usually 1 should be good in prod.
Regards,
---Satish

Error when trace is on

Hi,
With the trace is on, with each refresh of the query, I get a popup saying that '<Internal error> receing from BW server failed.BW server raised exception.System Failure. Do you want to see further information.' Whether I click yes or no, I get a popup in German. The logon pad opens up asking for user id and password.
Any suggestions?
Thanks.
Param

Ok, you are right, thanks Mylenium.
Here are a few details about my system :
iMac, 27-inch, Late 2009.
Processor 2.66 GHz Intel Core i5
Memory 4 GB 1067 MHz DDR3
Graphics ATI Radeon HD 4850 512 MB
And about After effect stuff
I am working in 1280 X 720 (half HD) comp size 25fps
I want to convert simple text into 3D text for logo animation.
I hope these inputs are helpful to suggest me something.
Thanks.

Error in trace file

Following is getting created in D:\Oracle\Ora81\DATABASE folder once or twice a month. I do not see any error entries in db1alrt.log. Please help to find out the problem.
Thanks,
Anil
Dump file .\ORA05244.TRC
Sun May 01 21:30:07 2005
ORACLE V8.1.5.0.0 - Production vsnsta=0
vsnsql=d vsnxtr=3
Windows NT V5.2, OS V14.206, CPU type 586
Oracle8i Release 8.1.5.0.0 - Production
With the Java option
PL/SQL Release 8.1.5.0.0 - Production
Windows NT V5.2, OS V14.206, CPU type 586
Instance name: db1
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
5244
*** 2005.05.01.21.30.07.127
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [508], [163], [0], [1413697536], [1], [0], [], []
Current SQL information unavailable - no session.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp+a5 CALLrel ksedst+0
75BE3F8
ksfdmp+e CALLrel ksedmp+0 3
_kgeriv+95 CALLreg 00000000
ED16A08
3
kgeasi+67 CALLrel kgeriv+0
1E440
0 1FC
5
675BE570
kslwte+11a CALLrel kgeasi+0
ED16A08
0 1FC
2 5 0
A3 0
0 0
54435000
0 1 0
0
opikndf2+537 CALLrel kslwte+0 A3
54435000
1 0
_opitsk+3da CALLreg 00000000
ED193E4
2
675BF544
1 0
opiino+50c CALLrel opitsk+0 0
_opiodr+4ce CALLreg 00000000 3C 4
675BFBF8
opidrv+380 CALLrel opiodr+0 3C 4
675BFBF8
0
sou2o+19 CALLrel opidrv+0
opimai+110 CALLrel sou2o+0
OracleThreadStart@4+48c CALLrel opimai+0 2
675BFE78
77E4A98D CALLreg 00000000
----- Argument/Register Address Dump -----
Argument/Register addr=675be3f8. Dump of memory from 0x675BE3B8 to 0x675BE4F8
675BE3A0 00000000 00000003
675BE3C0 E8D60800 6552211C 00000033 00000000 FFFFFFFD 00000048 00000000 00000000
675BE3E0 00000000 00000000 0000001D 2ED16888 675BE408 00418404 00C936B4 00C936B4
675BE400 00C936D4 00C936B4 00C936B4 00C936B4 00C936BC 00C936B4 00C936BC 00C936B4
675BE420 00C936B4 00C936B4 00C936B4 00C936BC 675BE4E0 004191E0 675BE444 0000001C
675BE440 00000000 2A2A2A0A 30303220 35302E35 2E31302E 332E3132 37302E30 32332D25
675BE460 2D252073 25207338 7332332D 675F0020 00000000 00000001 000007D5 35373620
675BE480 37454642 25200038 7332332D 342D2520 00000A73 00000003 65522178 00000033
675BE4A0 00000000 2ED16888 01218A97 00000000 00000000 00000000 675BFFEC 00000000
675BE4C0 675BFE78 00000000 00000001 00000001 00000000 675BDDD0 00000009 675BE504
*** Trace file full ***

you have what one session wants the other session has what you want; neither will give it up and so Oracle detects this and kicks one out. If you trace your SQL and COMMIT logic you will find the problem

Abap import error DbSl Trace: ORA-1403 when accessing table SAPUSER

hi all
I am installing ERP 6.0 (ABAP) on win2003 cluster, oracle 10g, I have error at database instance intallation. here some logs
DD03L.log
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090812102157
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Apr 3 2009 09:03:56
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(RTF) ########## WARNING ###########
 Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(TPL) ERROR: unknown template variable "tablespace"
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090812102157
import_monitor.log
ERROR: 2009-08-12 10:21:57 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is interrupted with R3load error.
Process 'I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error' exited with return code 2.
For mode details see 'DD03L.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2009-08-12 10:22:25
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-08-12 10:22:25
1 error(s) during processing of packages.
INFO: 2009-08-12 10:22:25
Import Monitor is stopped.
sapinst_dev.log
ERROR 2009-08-12 10:22:25.718
 CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
TRACE 2009-08-12 10:22:25.718 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2009-08-12 10:22:25.734 [sixxcstepexecute.cpp:951]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
TRACE 2009-08-12 10:22:25.781 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > High-Availability System > Based on AS ABAP > Database Instance( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAP/DB. </body></html>
TRACE 2009-08-12 10:22:25.781 [iaxxgenimp.cpp:1255]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
sapinst.log
WARNING 2009-08-12 10:22:25.718
Execution of the command "C:\j2sdk1.4.2_21-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_21"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_21-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_21-b03, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
Loading of 'DD03L' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.
ERROR 2009-08-12 10:22:25.718
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-08-12 10:22:25.734
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
any idea
Regards
ABH

hi
All logs are above (include import_monitor.log and java)
thanks

Error in trace log - Error in Mapping EngineODIException

Hi,
in the trace log file of OID i am getting the following error:
Trace Log Started at Mon Sep 24 08:56:34 CEST 2007
c360f8d929b0427faf0c332e05e78025_85bf9c6eeeec452c8a41c3ab23d03fc6 - Error in Mapping EngineODIException: Exception Connecting to DB :java.sql.SQLException: ORA-01017: invalid username/password; logon denied
ODIException: Exception Connecting to DB :java.sql.SQLException: ORA-01017: invalid username/password; logon denied
     at oracle.ldap.odip.gsi.DBConnector.connect(DBConnector.java:134)
     at oracle.ldap.odip.prov.ProvWriter.initialise(ProvWriter.java:113)
     at oracle.ldap.odip.engine.ProvThread.mapInitialise(ProvThread.java:642)
     at oracle.ldap.odip.engine.ProvThread.execMapping(ProvThread.java:559)
     at oracle.ldap.odip.engine.ProvThread.runOldVersion(ProvThread.java:543)
     at oracle.ldap.odip.engine.ProvThread.run(ProvThread.java:173)
java.lang.NullPointerException
     at oracle.ldap.odip.gsi.DBConnector.end(DBConnector.java:210)
     at oracle.ldap.odip.engine.ProvThread.mapEnd(ProvThread.java:718)
     at oracle.ldap.odip.engine.ProvThread.runOldVersion(ProvThread.java:546)
     at oracle.ldap.odip.engine.ProvThread.run(ProvThread.java:173)
java.lang.NullPointerException
Exception in Provthread
It started since I changed password of PORTAL schema.
everything works but i am wondering what's going on because trc file is now full of those messages
thanks,
Branislav

Hi Sami,
Check if thse threads can help u,
Error in BPE Adapter
BPM - BPE_ADAPTER errors
BPE Adapter Error
Exeception during execution error
***********Reward points if helpfull************

How can we make pe_adapter errors visible in sxmb_moni

Hello,
We are running on xi 3.0
Some errors that occur in mapping are not visible in sxmb_moni
The only way to see them is to open the successfull message and see that the second message of adapter is in status : 29 "Transfer to process engine"
or to open some workflow transaction monitoring were we can see work item is in error.
Is there a way to see this error in sxmb_moni or to modify the message status?
Thanks,
Laurent.

hmmm.. Unfortunately No
Best way to avoid manual monitoring is to use XI 's Alert Framework.If an error occurs, the Alert is triggered and the Alert contains the Message ID and this will help you locate the message immediately.
We have used XI Alerts and I have found them to be really useful!
Regards
Bhavesh

Getting Error in tcode sxmb_moni??

Hello All,
Its giving error while PI picks the file and sends to BW.
===================================================================================================
Registration failed
What happened is? The proclamation the URL http: //golit**03:8001/sap/xi/engine/ was interrupted based on more defectively registration data. Reference
The registration was carried out in the system DBG(SID of BW). The registration was carried out for the client 400 and the user and the language.
What can you do? If you control yet no user name, turn to your system administrator.
Mistake code: ICF-LE-http-c:400-l:-T:4-C:6-U:-P:-L:6
HTTP 401 - Unauthorized
Your SAP Internet Communication Framework team.
When I am trying to check from sxmb_moni,I am getting this error.Can you please help me.

Hi,
Please check this note 1292171
Extract from note
"The message monitor tool could be started directly via transaction sxmb_moni. The official transaction for all web service runtime tools is srt_tools. The message monitor could be also started from there with button Monitor for Processed XML Messages."
"Server receives HTTP code 401 "Unauthorized". Possible reasons: the user is locked, user/password are not set correctly in the logical port, the user does not have right to execute WS calls. If SSO is used there may not be trust relationship between consumer and provider."
Regards
Puneeth

Error categories in SXMB_MONI

I've been surfing around to find a list of predefined error categories and error ID's used in SXMB_MONI without luck.
Ex. Error Category = "MAPPING", Error ID="EXCEPTION_DURING_EXECUTE".
Can anybody guide me to such a list?
Regards
Peter

hi,
check out this table: SXMSSYERR
is this what you're looking for ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

How to catch errors watched in sxmb_moni through abap program??

Dear Gents,
I have one scenario which is proxy -> xi -> jdbc. Scenario works fine when every thing is good, but if there are any errors in XI usually we catch the exception after calling the proxy as :
TRY.
 CALL METHOD cl_rfq_sapin->mios_rfq_sapin
 EXPORTING
 output = output
 IMPORTING
 input = input.
 COMMIT WORK.
CATCH cx_ai_system_fault INTO cl_system_fault .
 gv_system_fault = 'X'.
CATCH cx_ai_application_fault INTO cl_application_fault.
 gv_application_fault = 'X'.
ENDTRY.
But by this code we are able to know whether it is system error or application error. But we cant get actual error. To see the actual error we need to go to SXMB_MONI in XI. The some sample error in sxmb_moni is as follows :
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://10.56.5.79:1433;databaseName=SXD': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either invalid or not running.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
So is there any way we can catch the above error in the abap program ??
Your responeses were highly appreciated.
Regards,
Santhosh

hi,
did you try using acknowledgments?
http://help.sap.com/saphelp_nwpi71/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
(code at the bottom of this page)
Regards,
Michal Krawczyk

Error in trace sxmb_moni

Similar Messages

Maybe you are looking for