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

Similar Messages

Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

Hi,
I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
2014-03-26 08:39:10
Information
The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
2014-03-26 08:39:10
Information
Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2014-03-26 08:39:10
Information
Message successfully put into the queue.
2014-03-26 08:52:48
Information
Admin action: Trying to redeliver message.
The connection between the receiver is ok, does this have something to do with the Communication Channels?
Please help.
thank you.

Hi Eng Swee,
there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
this is what is indicated in the Audit Logs
2014-03-26 02:38:47
Information
Admin action: Trying to fail message.
2014-03-26 02:38:47
Error
The message status was set to FAIL.
2014-03-26 02:38:47
Information
Admin action: The message was successfully set to status failed.
2014-03-26 02:38:47
Error
Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
2014-03-26 02:38:47
Error
Asynchronous error reported.
Is this the reason why the messages are stuck?
thank you!

To Be delivered status in Message monitoring

Hi,
There are some messages in TO BE DELIVERED status in Message monitoring while selecting integration server. I could neither cancel nor resend.
any input reg. this will be appreciated.
I didn't see any messages with TO BE delivered status in adapater engine.
I could able to clear What ever messages in system error status in adapter engine by filtering based on sequential id.
I have seen this thread & link also.
To Be Delivered
Re: "To be delivered" status in RWB -- Any solution?
http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
I could not see any entry in SMQ1, SMQ2, SM58 also
Thanks
Praba
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:02 PM
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:04 PM

Hi,
You cannot resend or cancell the messages which are in status "To Be Delivered". Check Receiver adapter File/Jdbc/ OFTP e.t.c. which is processing these messages.
Check with your Basis team to remove the lock of adapters if any. Or to process these messages you require soft restart of Java stack.
I had same kind of issue two days back with OFTP adapter messages and did soft restart of java stack with help of Basis team.
Hope it will helps you
Cheers
Veera

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

SYSTEM-ERROR. Tokens: MESSAGE = Io exception: NL Exception was generated;

Hello,
When I am running a page in jdev, I am getting the following error:
NVFactory: _readNVPair expected )
NVFactory: _readNVPair expected )
NVFactory: _readNVPair expected )
NVFactory: _readNVPair expected )
oracle.apps.fnd.framework.OAException: Application: FND, Message Name: SYSTEM-ERROR. Tokens: MESSAGE = Io exception: NL Exception was generated; (Could not lookup message because there is no database connection) at oracle.apps.fnd.framework.OACommonUtils.processAOLJErrorStack(OACommonUtils.java:884).....
Till yesterday the page was running fine but suddenly I am encountering this exception.
The DBC file is also fine without any slashes(/).
The DataBase connection is getting established successfully.
Please give your suggetions on to solve this issue.
Thank you.

Right click on the DB connection you are using and check whether you able to connect and open the "Sql Worksheet"?
--Shiv

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

Message status "Holding" - Message monitoring adapter framework

Hello,
We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
The blog does not mention what to do when the first message (sequential number) is not available anymore.
Is it possible to restart the messages in the queue in that case?
Thanks
Kind regards
Frank

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
resend or cancel the message to release the queue.
Regards,
Abhishek.

"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.

Message got struck in hold status in message monitoring.

Hi SDNers,
             I am doing Idoc to File scenario. I triggered an Idoc and it is successfully processed in XI and got struck in message monitoring with hold status.
             After repetetive attempts of restarting the message, still it is in hold status.
             Even if I tried to cancel the message, it is not cancelling as it is in hold status.
            Can anybody please help how to process the message or can anybody explain how to cancel the message from message monitoring, which is in hold status.
Regards,
Jayaram.G

Hi,
If the message that has not yet been delivered is not in error state, the problem cause is probably that the message is blocked in the QRFC queues of the Integration Engine.
Check queue status
Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:
u25CF     Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)
u25CF     Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)
u25CF     Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)
u25CF     Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.

Messages remain in Scheduled status in message monitoring in RWB

Hi PI experts,
I have got a situation where there are several messages showing in the Scheduled status. I followed the path RWB > Message Monitoring > Adapter Engine > Database (Overview) > Display.
QoS for these messages is EOIO, however there are no messages stuck in the queue. All other channels are running smoothly. Only with this particular channel the messages remain in Scheduled status for a long time.
I am neither able to make out the roor cause nor reprocess/resend these messages. Pleaes help.
Regards,
Dhawal

Hi Suraj,
What you said is absolutely correct. However, as I mentioned, the error message was not visible in RWB.
My problem just got resolved. What I did is this,
I followed the link http://<server>:<port>/MessagingSystem/monitor/monitor.jsp which is SAP Message Display Tool.
Here in EOIO Sequence Monitor I found the error message and it's predecessor. When I resent the erroneous message from here, all subsequent Holding messages got processed.
Thank you everyone for your help. Have a gr8 day...
Best Regards,
Dhawal

Want to access Status in Message Monitoring

Dear All,
I want to get access to the Status Parameter in Message Monitoring so that depending on the Status(Waiting or Syste Error),I can set my logic and send a mail to the developer.
I need help.
<b>1. Where can I find out the Parameter for status in RWB Message Monitoring?
2.Is there any method so that I can set some parameters and it will directly send mail to the developer or I have to use Mail Adapter and write my own scenario?
3.If I am to develop my own scenario,then how to automate the whole process for each of the New messages?</b>
Thank you in Advance.
Sugata

Hi Suresh,
Thank you for your reply.But this is not what I wanted.In my RWB,there are different Message monitoring Status parameters and I want to get hold of that,to be more open,I want that status to come as Subject of my mail.For that reason I need the Status Parameter,and I need to put that in my mail.How to do that?
Cheers..
Sugata

System Error in Comm channel monitoring of RWB

Dear all,
I have a Proxy to webservice scenario (HCM-PI-SuccessFactors). At receiver side i am using SOAP AXIS adapter. In RWB, the status of the channel is green and running. But when i ping the channel, it shows System Error.
I have made changes in respective communication channels, activated and cleared the cache. Still same error.
Later taken complete restart of system. Still same error.
How to overcome this ?
Note : 1) End to end scenario is working fine
2) Among the three trusted certificates installed, status of one certificate is showing warning (status: which will expire on may 5).
Regards
Uday

Hi Hareesh,
Thanks for you input. I have used the standard swc SFIHCM01. Here it is mentioned that it is applicable for SWC MESSAGING SYSTEM SERVICE 7.31 as shown below
What does this MESSAGING SYSTEM SERVICE mean exactly. In general is it our PI system.
plz correct me if i am wrong
Regards
Uday

System Errors in fault Message.

Hi All,
Is it required to capture the system errors in an Inbound proxy scenario from class CX_AI_SYSTEM_FAULT. , or the fault message will automatically get filled while a system error happen?
We are using the method CL_PROXY_FAULT=>RAISE to raise the application errorrs from BAPI return.
Regards,
Sunil

Hi,
   fault message are specific to application errors
    at inbound side and reported back to sender.
which is different from system error class i.e
   CX_AI_SYSTEM_FAULT.
please check the help content and blog on fault message types.
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
Fault Message Types - A Demo (Part 1)
warm regards
mahesh.

SOAP:Server, System Error SystemError , code MESSAGE.GENERAL /code

Hi!!!
I am testing a webservice and I am getting the following error
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context/>
               <code>MESSAGE.GENERAL</code>
               <text/>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Kindly help me with the same.
Thanking all of you in anticipation
Regards,
Kiran

Hi Michal,
Thanks for your prompt response. The above stated error is what I got after accessing it from soapUI.
I tried to access it from the browser and it gave the following message
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Thanks for your help.
Regards,
Kiran

Systems errors node in CCMS monitoring

Hello,
I try to build up CCMS monitoring in our XI system.
At the moment there is no error in the system.
When following the instructions from SAP and SDN everything looks fine except one issue.
E.g. in /people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2 from Aravindh (great blog series!)
in the first screen shot there is a node "System errors".
Such a node is missing in my configuration!
My question is: How to generate it, e.g. to implement a mail sender for upcoming errors in the category node?
Is this node generated automatically when the first error comes up for one of the different categories?
Best regards
Dirk

Dirk,
Go through the below links:
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
With the help of those you can configure and get System Erros node in CCMS.
Regards,
---Mohan

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

Similar Messages

Maybe you are looking for