cancel
Showing results for 
Search instead for 
Did you mean: 

Received XI System Error. ErrorCode: MSGGUID_EXISTING ErrorText: ErrorStack: Message ID for pipeline CENTRAL, version already exists in system

Former Member
0 Kudos

Hi Experts,

I am working on a file to soap (sync) async/sync scenario using modules. In this scenario a csv file as a request is sent from CRM to a 3rd party webservice and the response from the 3rd party is sent to the CRM sys using a file adapter. We have used "requestResponseBean" and responseOneWayBean" to achieve this. This scenario was working fine.

There is an authentication check using a cookie which we implemented using Java mapping. Recently the cookie got expired and we received another persistant cookie which we incorporated in the Java mapping and imported the jar file once again in the "Interface Mapping".

Once all changes are done we were getting "Linkage Error" in MONI. We again compiled the mapping in JDK 1.4 as we are using PI 7.0 and now we are getting error message as below:

<SAP:Code area="PERSIST">MSGGUID_EXISTING</SAP:Code> 

<SAP:P1>81FE88DB181848DE22289BB02A223A51</SAP:P1>

<SAP:P2>CENTRAL</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Message ID 81FE88DB181848DE22289BB02A223A51 for pipeline CENTRAL, version already exists in system</SAP:Stack>

   

In Sender CC the error shows:

06.08.2013 07:17:56.398SuccessChannel FILE_ProspectConsumerCRM_DFY_Sender_CC: Part of file content converted to XML format. Message split detected. Converted up to position 3
06.08.2013 07:17:56.399SuccessSend binary file "Sync_MAM_20130409_0642021.csv" from FTP server "c7qci.ford.com:/interface/C7Q/OUT/DRAGONFLY", size 1427 bytes with QoS EO
06.08.2013 07:18:11.410SuccessRRB: entering RequestResponseBean
06.08.2013 07:18:11.411SuccessRRB: suspending the transaction
06.08.2013 07:18:11.411SuccessRRB: passing through ...
06.08.2013 07:18:11.411SuccessRRB: leaving RequestResponseBean
06.08.2013 07:18:11.412SuccessApplication attempting to send an XI message synchronously using connection File_http://sap.com/xi/XI/System
06.08.2013 07:18:11.412SuccessTrying to put the message into call queue
06.08.2013 07:18:11.425SuccessMessage successfully put into the queue.
06.08.2013 07:18:11.430SuccessMessage retrieved from call queue
06.08.2013 07:18:11.444SuccessThe message status set to DLNG.
06.08.2013 07:18:13.955ErrorReceived XI System Error. ErrorCode: MSGGUID_EXISTING ErrorText: ErrorStack: Message ID 81FE88DB181848DE22289BB02A223A51 for pipeline CENTRAL, version already exists in system
06.08.2013 07:18:13.956ErrorReturning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
06.08.2013 07:18:13.956ErrorTransmitting the message using connection http://x7qci.ford.com:8040/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
06.08.2013 07:18:13.959ErrorThe message status set to FAIL.
06.08.2013 07:18:13.960ErrorReturning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
06.08.2013 07:18:13.963SuccessRRB: resuming the transaction
06.08.2013 07:18:13.963ErrorAttempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
06.08.2013 07:18:55.338SuccessChannel FILE_ProspectConsumerCRM_DFY_Sender_CC: Part of file content converted to XML format. Message split detected. Converted up to position 3
06.08.2013 07:18:55.339SuccessSend binary file "Sync_MAM_20130409_0642021.csv" from FTP server "c7qci.ford.com:/interface/C7Q/OUT/DRAGONFLY", size 1427 bytes with QoS EO
06.08.2013 07:18:55.344SuccessRRB: entering RequestResponseBean
06.08.2013 07:18:55.344SuccessRRB: suspending the transaction
06.08.2013 07:18:55.344SuccessRRB: passing through ...
06.08.2013 07:18:55.344SuccessRRB: leaving RequestResponseBean
06.08.2013 07:18:55.344SuccessApplication attempting to send an XI message synchronously using connection File_http://sap.com/xi/XI/System
06.08.2013 07:18:55.345SuccessTrying to put the message into call queue
06.08.2013 07:18:55.347SuccessMessage successfully put into the queue.
06.08.2013 07:18:55.355SuccessMessage retrieved from call queue
06.08.2013 07:18:55.356SuccessThe message status set to DLNG.
06.08.2013 07:18:55.483ErrorReceived XI System Error. ErrorCode: MSGGUID_EXISTING ErrorText: ErrorStack: Message ID 81FE88DB181848DE22289BB02A223A51 for pipeline CENTRAL, version already exists in system

Please help.

Partha Ghosh

Accepted Solutions (1)

Accepted Solutions (1)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Partha,

Check if you have the fix in note 1437660 Synchronous processing: Error MSGGUID_EXISTING. Also check these notes:

  1. 1614154 Error MSGGUID_EXISTING for synchronous messages
  2. 1474759 XI runtime: Error MSGGUID_EXISTING
  3. 1147287 XI runtime: Preventing duplicate persistence

Regards

Mark

Former Member
0 Kudos

Hi Mark,

Thanks for your help. We have resolved this issue today morning. The main issue was due to the Java program that we were using. As we are using 7.0 we need the java mapping to be compiled in JDK 1.4. Once we compiled it in JDK 1.4 and replaced the jar file. The issue (Linkage Error and MsgGuid_Existing) is resolved.

Thanks

Partha

Answers (0)