IDOC Posting To XI Failed With Status Text "::000" in SM58

Hello Gurus
Can u please suggest me how to overcome the problem with Custom Idocs while trying to send from SAP R/3 to SAP PI(XI).
The status text is displaying as "::000" with no other details, in SM58 of the sender system i.e. SAP R/3.
The Idocs status in the sender system is showing as 03 with the message "Idoc sent to sap system" in transaction BD87.
So I am getting confused where I missed the configuration.
Please suggest how I can troubleshoot the above.
<<Text removed>>
Regards,
Rk.K
Thanks in advance .
Edited by: Matt on Jun 24, 2011 9:58 AM

Thanks a lot for your support.
I have tried all the suggested solutions......but my problem was not solved.
The Metadata should be automatically created when the IDOCS successfully received by the XI server.
If it is not created then we should clear the SLD Cache in XI and try to create a new Metadata by giving the Custom IDOC Name and Port.
Even I tried with a Standard Idoc ORDERS05 , but I failed to do so.
After doing the above step I am getting the Information pop-up message "I::000".
Regarding RFC, I have created 2 users in both the systems with the same name(ALEREMOTE) of type "System".But,I am unable to Remote Login from XI to R/3 whereas the vice -versa is successful.
Are there any chances for this being the reason for failure of Idoc processing?
Such information message"I::000" is completely inexplainable.
Kindly, suggest a solution for it.
Thanks.

Similar Messages

IDOCs in trfc with status text as error

Hi,
I have IDOCs in trfc queue with status text as 'The ABAP/4 Open SQL array insert results in duplicate database records'.
How to reach this error point and rectify the same.
Regards,
Sheetal

Hi Sheetal,
Please refer the link,
Successfully posted IDOC from XI but not reflected in Receiver R/3 system
Best Regards.
Reward points if it is useful.

Windows Server 2008 SP2 randomly reboots due to lsass.exe failed with status code 255

Hello,
Any help on this issue would be greatly appreciated. I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
during business hours. Looking into the event logs, I have found the following:
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066d9669a3e1c.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
A few hours later, the crash happened again, with a slightly different error:
The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066fa9d74c5d7.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.
The security package Kerberos generated an exception. The exception information is the data
I have been unable to find a reason for these exceptions and the server rebooting. Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again? .
Thank you,
Ben

Hello,
Any help on this issue would be greatly appreciated. I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
during business hours. Looking into the event logs, I have found the following:
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066d9669a3e1c.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
A few hours later, the crash happened again, with a slightly different error:
The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.
Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
time 0x01d066fa9d74c5d7.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.
The security package Kerberos generated an exception. The exception information is the data
I have been unable to find a reason for these exceptions and the server rebooting. Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again? .
Thank you,
Ben

CMPControlManager::PublishInDNS: DnsReplaceRecordsInSet() failed with status 9005 in MPControl.log and MP is showing in critical state

CMPControlManager::PublishInDNS: DnsReplaceRecordsInSet() failed with status 9005 error message in mpcontrol.log and management point showing critical state in Monitoring-Site status
Please help to resolve the same.

Based on this thread ---> http://social.technet.microsoft.com/Forums/systemcenter/en-US/f66a8f0f-31df-49b1-b385-450c522aac0f/cmpcontrolmanagerpublishindns-dnsreplacerecordsinset-failed-with-status-9005-getting-this?forum=configmgrinventory
a possible workaround is:
1. Start DNS
2. Navigate to following DNS SRV record: _mssms_mp_<SMS_SiteCode>._tcp.AD_FQDN
3. Right click on this record; and add all MP Machines Account and provide Full Control permissions on this DNS SRV Record.
4. Restart "SMS_EXECUTIVE" service on all MPs
You will then see that each MP will successfully register each DNS SRV records successfully.

Function module ZBAPI_DELV_HU_DETAILS is failing with status TARGET_METHOD_

Hi,
Function module ZBAPI_DELV_HU_DETAILS is failing with status TARGET_METHOD_EXCEPTION external server. What could be the reason for this?
This Function Module will be called within program ZMWXO011. This program will be configured in the output determination for HU's. It will be triggered whenever a relevant HU is created. The BAPI will extract Delivery & HU level data that is required by Exacta & Scan code and send to a predefined TRFC Queue.
Thanks & Regards,
Srinivas Reddy.

Hi Efren,
Go to transaction ST22 and check for any dump.
The work item is in process, so there will be a dump in the system.
The Function module parameters could be a problem.
ST22 transaction will give you details about the dump.
Thanks,
Viji.

Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time when trying to set custom property.

Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time, when trying to set custom property.
anyone have any idea

Hi
Stumbled upon the resolution myself. The Bean Area item needs to be set to Visible=Yes in the property palette for the bean within Forms Builder, and also the implementation class also in the bean's properties must match exactly the package & class name specified in the PJC (my full implementation class string had to be set to oracle.forms.demos.runApplication).
As this bean has no user interface component, and since the Visible property has to be set to Yes, to avoid having a random square shape for the bean sitting on the form's canvas, I also set the Width and Height properties for the bean to 0.001. This does show a very small dot on the form, but that will be acceptable.
So in summary there has been a change for PJC / Bean Areas between 6i and 10g Forms, in 6i you could have the Bean Item to be set Visible=No, and the SET_CUSTOM_ PROPERTY built-in would work, however in 10g Forms the Bean Item must be set to Visible=Yes for the SET_CUSTOM_PROPERTY built-in to work.
Daryl

Profile Manager: Service has failed with status 500?

I am getting a "Service has failed with status 500" error when trying to enroll a device with profile manager. Does anyone have a resolution for this?

In OS X Server 2.1.1 there seems to be an error, according to: https://discussions.apple.com/thread/4365626?start=0&tstart=0

Status Text 000

Hello
I tried an Idoc. It doesn't reach XI. It does not appear in SXMB_MONI. In SM58, I see status text 000. What does that mean ?
However when I go to WEO2 I see Current Status as 03.
What should I do and how woiuld I proceed ?
Midhun

Hello Ravi
When I double click on it, I get this : : 000
I don't find anything more
I went to SM59, RFC Destination from QAS of XI, then did a Utilities -> Test -> Authorization Test
I got this as a result.
Logon Cancel
Error Details Name or Password is incorrect (repeat logon)
So there is an Error with SM 59 that I created to ECC from XI.
Midhun

Idoc failed with status 51 for Warning/Information messages

Hi All,
We are trying to create some Sales Orders with the help of Idocs. We are facing some problem as mentioned below.
1.There are some warning messages/information messages written in standard Sales Order User Exit USEREXIT_SAVE_DOCUMENT_PREPARE
2.As soon as the Idoc processing reaches any of these messages, it considers them as ERROR message and Idoc fails with the status as 51 which is not expected.
3.Also, I see that the Sales Order is saved with the data that has been passed in the Idoc.
Is this the standard behavior ?? (Or) Is there any EDI related configuration setting which can be used to suppress these kind of messages in Idoc Processing ??
Any help on this would be highly appreciated.
Thanks,
Babu Kilari

if your IDOC has status 51 then it is not posted, hence your sales order cannot be created from this IDOC. of course this error behaviour can be originated by the user exit.
please read OSS note Note 747631 - Some tips when testing idoc_input_orders

Failed with status 400 creating new room.

Hi,
I am using the server API to create a new room, but I fail with a response code of 400. Can you tell me what I am doing wrong?
I'm using the sample Java server integration code to do this.
Thanks.

Hi Raff,
Here are the logs when I set Utils.DEBUG = true;
http_get: http://connectnow.acrobat.com/xoomxo?mode=xml&accountonly=true&
Redirecting to https://na2.connectnow.acrobat.com/xoomxo?mode=xml&accountonly=true&
http_get: https://na2.connectnow.acrobat.com/xoomxo?mode=xml&accountonly=true&
Content-Type: text/xml;charset=UTF-8
Content-Length: 177
http_post: https://services.acrobat.com/account/wsapi/auth/v1 <request><username>[email protected]</username><password>bizzybaz1</password></request>
{Content-Type=text/xml}
Content-Type: text/xml;charset=UTF-8
Content-Length: 127
http_get: https://na2.connectnow.acrobat.com:443/xoomxo?mode=xml&accountonly=true&gak=cmVuZ2EqbmExci oxMjcwYzUwMDgyMipFQ1E5WjdHMkpENUE1NDlLUFpDUVA4UU1OUg==
Content-Type: text/xml;charset=UTF-8
Content-Length: 323
http_post: https://na2.connectnow.acrobat.com:443/xoomxo mode=xml&room=xoomxoroom2.15_Room&template=dateroomtemplate&gak=cmVuZ2EqbmExcioxMjcwYzUwM DgyMipFQ1E5WjdHMkpENUE1NDlLUFpDUVA4UU1OUg==
HTTP error 400
Does this show what might be causing the error?
Thanks,
Barry

Metachain failed with status 'X'.

Hi experts,
I have an issue with the meta chain which has been canceled with the status 'X'.And some of the local process chains are not getting triggered.
Please help me.
Regards
Sam

Hi Sam,
Could you please explain your issue in detail. At what step your process chain got failed.
open the chain in RSPC1 --> goto logs view ---> right click on step which got failed --> select display messages
here check the log, you will find the error or post the log here.
You told you local chain have not triggered, is the above step got completed. make sure your local chains start condition is immediate.
check you have enough back ground processes in SM50 and SM51.
Regards,
Venkatesh.

File to convert to IDOC from bus.service failes with ALE#LI

Hello,
we habe implemented a scenario:
Non SAP system sends a structure to be uploaded to an R/3 system as IDOC.
All config looks fine.
We followed this description:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
So system is identified in adapter specific data as log.sys. LS test1 .
But we have this error:
Unable to convert partner abc / ALE#LI into an IDOC partner (message in german, only translated)!
Does anybody has an idea what is wrong?
Is it necessary to have the log.sys name in the message e.g. in SNDPRN?
Here we have after mapping:
<SNDPOR>testABC</SNDPOR>
<SNDPRT>LI</SNDPRT>
Best regards
Dirk
Message was edited by: Dirk Meinhard
Message was edited by: Dirk Meinhard

Hi Nimrod,
looks like I am not totally wrong here, but working together with externals who provide the outbound side is not really easy for testing.
Here is the EDI_DC-40 segment AFTER the Mapping, so the XML for the inbound IDOC:
- <PORDCR05>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>010</MANDT>
<DIRECT>1</DIRECT>
<IDOCTYP>PORDCR05</IDOCTYP>
<MESTYP>PORDCR</MESTYP>
<SNDPOR>A000000039</SNDPOR>
<SNDPRT>LI</SNDPRT>
<SNDPRN>0005354880</SNDPRN>
<RCVPOR>SAPK10</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>LOG10</RCVPRN>
</EDI_DC40>
Here is the error message:
<?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="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>Partner_ABC</SAP:P1>
<SAP:P2>ALE#LI</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Sender XI Party Partner_ABC / ALE#LI / could not be converted to IDoc Partner </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In my opinion we have to implement in WE20 of receiver R/3 system a partner LI with this number A000000039 from the EDI DC 40 segment? And we need to add it as identifier LOGICAL with ALE#LI and this number A000000039.
R/3 consultant says he cannot do this in the receiver R/3 system because the sender is no supplier in his system!
regards
Dirk

Email on Idoc Failure with Status 56 64 68 69 70

We have standard inbound idoc processing for Basic Type : DELVRY01 and Message Type : DESADV using the function module IDOC_INPUT_DESADV1.
We currently have a requirement to send an email, when any of these type of Idocs fail with status 56, 64, 68, 69 and 70.
Where would be best place to provide this solution to send an email to a particular user when the Idoc fails with the above status?

Hello Saleem,
One approach would be to consider workflow based on object type IDOCAPPL. The start condition for the workflow could be the triggering of the event errorProcessCompleted. You could filter further by status and your message type (DESADV ) to only start the workflow for the errors that you mentioned. The workflow could then send an email.
You will need to verify the details for your own scenario.
Good luck,
Greg Kern

SM13 Update Request Failed entries with status "Enqueques deleted"

Hi Experts,
I viewed transaction SM13 and there are entries whereas the updated request is failed and the status is "Enqueque deleted". Unlike with other updated request failed with status "Error", error message is provided. However for those with "Enqueque deleted" there's NO error. Do you have any idea what went wrong having such status? Thanks in advance!
Best Regards,
Kurtt

Hi Royit,
Thank you very much for your response. are there any means of tracing who deleted/released it? Thanks in advance!
Best Regards,
Kurtt

GetItemsRequest failed with HTTP status 400

At one of our customers we've got a strange error.
The Login/Logout request works fine, but the getItemsRequest fails with status 400.
Here is the soap request:
------- SoapRequest at 13:29:22 -------
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><session xmlns="http://schemas.novell.com/2005/01/GroupWise/types">BbOOBFebTkAxSffn</session></soap:Header><soap:Body><getItemsRequest xmlns="http://schemas.novell.com/2005/01/GroupWise/methods"><view>default id container @type message subject startDate endDate attachments recipients status</view><filter><element xsi:type="FilterGroup" xmlns="http://schemas.novell.com/2005/01/GroupWise/types"><op>and</op><element xsi:type="FilterEntry"><op>contains</op><field>subject</field><value>*</value></element></element></filter><items><item xmlns="http://schemas.novell.com/2005/01/GroupWise/types">4ECE5BEE.GWDOMNM.GWPOSTNM.100.1333466.1.16E BA.1</item></items><count>-1</count></getItemsRequest></soap:Body></soap:Envelope>
POA is 8.0.2, any suggestions?

There is not enough information.
You could check the POA log file.
You can turn on logging the soap requests in the POA log file
to see if that shows the error around the time on the soap
request.
If you get an 8.0.x build after 98083, we put the engine
error in an HTTP header line:
X-GWError-Code: xxxx
Preston
>>> On Wednesday, January 04, 2012 at 6:26 AM,
hkunze<[email protected]> wrote:
> At one of our customers we've got a strange error.
> The Login/Logout request works fine, but the getItemsRequest fails with
> status 400.
>
> Here is the soap request:
>
> ‑‑‑‑‑‑‑ SoapRequest at 13:29:22 ‑‑‑‑‑‑‑
>
> <?xml version="1.0" encoding="utf‑8"?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema‑instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><session
> xmlns="http://schemas.novell.com/2005/01/GroupWise/types">BbOOBFebTkAxSff
> n</session></soap:Header><soap:Body><getItemsRequest
> xmlns="http://schemas.novell.com/2005/01/GroupWise/methods"><view>default
> id container @type message subject startDate endDate attachments
> recipients status</view><filter><element xsi:type="FilterGroup"
>
xmlns="http://schemas.novell.com/2005/01/GroupWise/types"><op>and</op><eleme
nt
>
xsi:type="FilterEntry"><op>contains</op><field>subject</field><value>*</valu
e></elemen
> t></element></filter><items><item
> xmlns="http://schemas.novell.com/2005/01/GroupWise/types">4ECE5BEE.GWDOMN
>
M.GWPOSTNM.100.1333466.1.16EBA.1</item></items><count>‑1</count></getItems
Request></s
> oap:Body></soap:Envelope>
>
> POA is 8.0.2, any suggestions?

IDOC Posting To XI Failed With Status Text "::000" in SM58

Similar Messages

Maybe you are looking for