SAP XI 3.0 - Error while reading the ID of own business system from the SLD

Error while reading the ID of own business system from the SLD for system Quality (QOC) and Client 100.
I get this error in the SXMN_MONI. The business process is that the Interface to send master schedule and finished inventory from the legacy system to SAP to create planned orders in SAP for all Plants.
I could able to get "SUCCESSFULLY PROCESSED" in development and production. But only in Quality I getting this error. Could anyone help me to fix this issue.
thanks...

Probably, its due to incorrect RFC Adapter properties in config.
Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click on Service-->Adapter Specific Parameters.
Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
After this, you can retry sending the message.
Rgds
R Chandrasekhar

Similar Messages

Error while reading the ID of own business system from the SLD for system

Hello,
I try to send master material data from a 4.7 system via XI 3.0 to an autoID Infrastructure system 2.1. All Communication Channels, Receiver Agreements, Receiver and Interface Agreements are configured. The IDOC gets propper into the XI, Inbound Message is "green". Now, I get the following 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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>ZTA</SAP:P1>
<SAP:P2>013</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading the ID of own business system from the SLD for system ZTA and client 013</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody help me?

Probably, its due to incorrect RFC Adapter properties in config.
Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click on Service-->Adapter Specific Parameters.
Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
After this, you can retry sending the message.
Rgds
R Chandrasekhar

Error while reading ID of own business system from the SLD

HI guys when trying to send Idoc from my R/3 system to SUS i am getting the following error in XI
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>DSM</SAP:P1>
<SAP:P2>900</SAP:P2>
<SAP:Stack>Error while reading ID of own business system from the SLD for system DSM and client 900</SAP:Stack>
I checked in sxmb_adm on both the ends on Xi as well as on my SUS server in Xi the role is the Integration server and on the SUS it is Application server also checked SLDAPICUST which is configured rite. Plz help me to come out of the problem.
Regards,
Anand

Hi Anand,
check the two thing's in XI.
1. First created technical system in XI to identify your XI server (Web as ABAP and Web AS Java)
2. Create the business system based on above technical system and select the role of business system is Integration server.
URL : http://<hostname>:<ICM Port>/sap/xi/engine?type=entry.
3. Create the technical system based on your SAP R/3 system.
4. Create the business system based on your SAP R/3 system.
here you need to select role of business system : Application system.
related integration server is : <XI System SID has to come>
and try to refresh the initical cache once ...
http://<hostname>:<j2ee stack port>/CPACache/refresh?mode=full
after all the things post what is the problem you are faceing.
Regards,
Venu.

Error while reading ID of own business system from the SLD for system D18

Dear guru's,
I have almost completed a file2proxy scenario but I'm stuk on the following.
When sending a message the outbound adapter says:
<b>Error while reading ID of own business system from the SLD for system D18 and client 200</b>
What's the problem? I'm using a HTTP connection in the comm. channel. In this http connection a user with SAP_ALL is defined.
Any suggestions?
<?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">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>D18</SAP:P1>
<SAP:P2>200</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading ID of own business system from the SLD for system D18 and client 200</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Login to system D18 and client 200 and check the TC SLDCHECK and also as per my pervious message check the entries in the SLDAPICUST, it should point to the Server on which SLD is present usually XI server https.
Actually what happens in this error is when you are done with the configuration part in the ID, you are trying to eceute the scenario File to proxy, when it comes to identify the receiver system which is D18 clnt 200, it goes to SLD to check it and SLD is trying to ping to the machine D18 this connection is set from the TC SLDAPICUST on the machine D18.
here the problem is that either the D18 is not able to ping to the SLD and also try refreshing the SLD cache.
Hope you problem is fixed

Error while reading ID of own business system from the SLD for system DPI

Hi All,
My sceanrio is Proxy to JDBC. and its B2B. am sending the data from BI system and based on the country field from the source, table is decided and value is updated in the table.
In RWB->Component Monitoring->Adapter Engine->Test Message, I have given the Sender component,Receiver Party,Receiver component,Interface,Interface Namespace,userid and password,Quality of Service and pasted the payload.
Now I am getting the error :Error While Sending Message: Error stack from response: Error while reading ID of own business system from the SLD for system DPI and client 001 Internal error in Landscape Directory
Please help me out.
Thanks
Kiruthi
Edited by: kiruthiga balusamy on Nov 24, 2009 4:02 PM

Hi,
Check transaction SLDAPICUST for correct SLD configuration.
http://help.sap.com/saphelp_nw70/helpdata/EN/0b/8512417301ee6fe10000000a1550b0/content.htm
~Sanv...

SLD Error in IE:Error while reading ID of own business system from the SLD

Dear Champs,
Scenario : JDBC to Proxy(APO system)
We are getting below error in MONI UAT Box. All other interface are working fine but we are facing issue for a particular Bussiness System also logical system are maintained properly.the same interface is working fine in other UAT box.
- <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">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>R/3 Sys ID</SAP:P1>
<SAP:P2>"Client"</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading ID of own business system from the SLD for system "R/3 Sys ID"and client "Clnt no"</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards,
Manikandan

Hi Mani,
Solution 1:
Check if the techncal system has associated Business system. I think there is something wrong in your SLD configuration and try to correct it.
Solution 2:
Create a Business system in the ID, and create the communication channel do the respective changes in ID ( I.e Receiver agreement, Receiver determination & Interface).

Error while reading ID of own business system from the SLD for system

Dear all,
We running on a SAP PI 7.1 enhancement pack 1.I know that there some threads about this subject, but unfortunately all suggestions found so far didn't solve my problem:
- SLDCHECK reports no errors
- SLAPICUST: pointing to the SLD
- SXI_CACHE with full refresh: no result.
Does anyone have a clue for me?
Kind regards,
John.

I hope you are facing this prolem with one particular Business System.. Since you have checked all the points and still facing this issue then try below options..
1. First try to clear full SLD cache and then test.
2. If cache doesn't solve the issue then delete the Business System from SLD and Integration Directory first then re-create the BS in SLD and "Clear SLD Data Cache" from "Environment" menu in Integration Directory and then import the Business System and test your scenario.

Error when reading the ID of the business system from the SLD

Hi,
I am working on a scenario JDBC - XI - BW (ABAP Proxies). I configured all the steps required to connect XI & BW systems. The SLDCHECK transaction is all green. I was able to connect to SLD from BW using SXMB_IFR tcode too. I was able to look at all the XI Repository interfaces from SPROXY tcode in BW. Created a new ABAP proxy (class interface and method) for the message interface in XI from BW (SPROXY Tcode). Created all required config in XI Directory. Got the message from JDBC adapter, mapping done successfully, and the message failed in the CALL Adapter Step.
The error is "Error when reading the ID of the business system from the SLD for system BWS and client 100."
What could have gone wrong. Thanks in advance.
Srini

Hi,
:::::::One Should Have the Following Roles AS A XI Developer With Out Admin Rights ::::::
1) SAP_XI_Developer_ABAP +
2) SAP_XI_Developer_J2EE +
3) SAP_XI_MONITOR_ABAP +
4) SAP_XI_MONITOR_J2EE +
5) SAP_SLD_ADMINISTRATOR +
6) SAP_XI_BPE_MONITOR_ABAP +
7) SAP_XI_DEMOAPP
8) SAP_XI_DISPLAY_USER_ABAP +
9) SAP_XI_DISPLAY_USER_J2EE +
Regards
Sesh

Sharepoint 2013: Workflow Error , while trying to publish a Sharepoint 2013 Workflow, from the Sharepoint Designer 2013

I don't know what might be wrong but I have tried everything possible I suppose.
Configuration: 1 App Server SharePoint Standard 2013 + SQL Server. On App Server, I have installed Workflow Manager as well.
Installed Sharepoint Designer 2013 on my laptop.
Before I was able to publish the workflows, but now it refuses, thwroing me the following error:
System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : ac85cf9c-053a-e0db-1f47-608050559d31. ---> System.Net.WebException:
The request was aborted: The request was canceled. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). ---> System.IO.PipeException: There was an error reading from
What I have tried so far:
a. Re-installed Workflow, Service Bus, Windows Fabric, Sharepoint Designer... no luck
b. Run the configuration script... -Force enabled... no luck
c. Remove WF Manager, SB, etc... Deleted all WF and sb Databases from SQL, and re-installed all icluding updates... no luck
d. Tried to run services using Farm account, still no luck.
e. All services on the Server are running as well
f. The workflow is checked that it is associated with the site collection.
I don't know what else to try... seems like I am experiencing unique issue here... please help!

One last thing I can suggest - In case if you have installed CU Update for WF manager 1.0 and service bus. Some time that creates problem, [Please take backup before make any changes] -
- Clear everything, WF config , SharePoint WF setting, un register WF from SP , You can delete and recreate WF service Apps
- IISreset at WF and SP server
- Uninstall CU update for Workflow manager 1.0 and Service Bus from WF server [Control Panel - Programs - Update], you can delete all update installed
- ReStart WF server
- Reconfigure WF manager , Test WF sites , should return XML
Get-WFFarm | ft HttpPort
- Reconfigure WF at SP , Make sure should have enough free memory
Register-SPWorkflowService –SPSite "http://SPsite/" –WorkflowHostUri "http://WFServer:12291" –AllowOAuthHttp
http or https , depend on your configuration
And retest from SPD again.
Good luck:)
Thanks
Ganesh Jat [My Blog |
LinkedIn | Twitter ]
Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

Error while exporting/transporting the Business system from Dev to Quality

Hi,
We are getting the following error whil exporting/trsnporting the Business system from development(SLD) env to quality(SLD) environment. The error is
404 Not Found
The requested resource does not exist.
Details: Go to main page of this application!
We have followed the following procedure to export :
1. opened the business system.
2. Clicked on export option
3. tried to download
then we got the above error message.
Please provide your precious inputs to resove our problem.
Thanks
Ramesh

Go through the following links for transporting XI objects.
https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
ere's a good link for what you are looking.
Re: Transport design and configuration objects
Here are some blogs.
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
Pls reward if useful

Creating a Business system in the SLD

I am receiving an error message when trying to create a business system in the SLD. The error is "The selected client has an associated logical system nae that is already used for another business system. Select a different client."
Here is my issue. The business system that I am creating is for our R/3 4.6C production system. I currently have a business system for our R/3 4.6C quality system. Our prodution and quality R/3 systems do have the same logical system name and client number. This is because we recreate our qaulity R/3 system from our production system.
So, the question is, How do I create a business system in the SLD for my production R/3 system when the logical system name is used assoicated with and business system.
I should add that all my R/3 systems have been created as technical systems without any problems.
Thanks,
Jim

It is recommended to have all ALE names unique.
If it is not possible the following workaround can be used.
Create one system in SLD (business system/technical system) which contains the ALE name. Proposal: The production system
Create the other systems(dev/QA) without the ALE name
During configuration the production system will be configured as usual.
For Dev/QA systems: Define in the receiver agreement the header mapping and use The Receiver service to reference the production system. Because you reference the production system the ALE name of the production system will be used to fill the idoc.

Registration of Business system for the Integration Engine Java in the SLD issue

Hi,
We have completed the installation of PI-AEX 7.4 SR1 then we ran the below wizards successfully.
- Configuration Wizard: PI-AEX initial setup
- Configuration Wizard: PI Self Test for AEX
However when we were Checking the AEX Configuration as per help.sap.com
Check the registration of a business system for the Integration Engine Java in the SLD:
    Enter https://<host>:<port>/sld .
    Choose Start of the navigation path Business System Next navigation step Integration Engine Java <SID> Next navigation step Integration End of the navigation path.
    The pipeline URL must be: http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet?ximessage=true .
More information: SAP Note 1435392
for us the Pipeline URL is as below
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
and the rest " ?ximessage=true " is not there.
Also we ran the below wizard
Configuration Wizard: PI Self Test for AEX
and it finished successfully without any issue.
Any Suggestions what could be missing.
Thanks,
Regard
Ahmed Mohammed

Hi,
I found the below SAPNOTE which confirms that the Pipeline URL should be
http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
1564449 - PI CTC Wrong Pipeline Url after AEX Initial Setup
However on help.sap.com it is different.
Any one experienced the same ?
Regards
Ahmed Mohammed

Unable to Log-in *SAP System Message : Error while reading a Dynpro*

Hi,
We are facing issues while logging-in through SAP logon 710.
The system throws an error dialog box with the below message:
SAP System Message : Error while reading a Dynpro
At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

Hi Please find the contents of std_server.out below.
stdout/stderr redirect
node name   : server0
pid         : 4124
system name : KEC
system nr. : 01
started at : Mon Jul 27 15:44:57 2009
[Thr 5656] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
Loading: LogManager ... 250 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 93 ms.
Loading: LockingManager ... 32 ms.
Loading: ConfigurationManager ... 1032 ms.
Loading: LicensingManager ... 0 ms.
Loading: CacheManager ... 93 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (16 ms).
Service cross started. (31 ms).
Service file started. (31 ms).
Service memory started. (31 ms).
Service timeout started. (16 ms).
Service trex.service started. (32 ms).
Service userstore started. (0 ms).
Service jmx_notification started. (15 ms).
Service p4 started. (62 ms).
Service classpath_resolver started. (16 ms).
Service deploy started. (3722 ms).
Service MigrationService started. (31 ms).
Service bimmrdeployer started. (0 ms).
Service log_configurator started. (5177 ms).
Service locking started. (0 ms).
Service http started. (126 ms).
Service naming started. (157 ms).
Service failover started. (16 ms).
Service appclient started. (31 ms).
Service javamail started. (47 ms).
Service ts started. (47 ms).
Service jmsconnector started. (47 ms).
Service licensing started. (15 ms).
Service connector started. (93 ms).
Service iiop started. (94 ms).
Service configuration started. (16 ms).
Service webservices started. (265 ms).
Service dbpool started. (1204 ms).
Service UT started. (0 ms).
Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Error while reading the PO in the Backend system. Inform system admin

Hi All,
We are having a peculiar issue of 'Error while reading the PO in the Backend system. Inform system admin'.
The P.O is in ordered status in SRM but the same is not getting transferred to backend ECC system.
No error messages or logs in RZ20, SLG1 any where.
All programmes like BBP_GET_STATUS_2 and CLEAN_REQREQ_UP are running fine.
Tried pushing the P.Os manually using function module (BBP_PD_PO_TRANSFER_EXEC_V2) to backend ECC.
It was working fine till a week ago and suddenly this problem is coming.
We had implemented few OSS notes suggested by SAP for the issue of 'shopping carts appearing in sourcing cockpit even after P.O creation' in both development and test system.
Now this issue is coming up in test system where as development system is working fine.
Please let us know where to look and how to resolve this issue.
A quick response would be highly appreciated.
Regards,
Teja

I am facing the same issue with one PO in the Production system.
SRM 5.0 , R/3 4.6C Extended classic scenario.
I checked the status of other PO's created today. I see them in R/3. There is one PO which was created a week back which shows up as "ordered" in SRM but the PO is missing in R/3. When clicked on the details on the web, system throws the error
Error while reading the PO in the Backend system. Inform system admin.
Message no. BBP_CF010
I checked RZ20, SLG1 no errors were found. I checked RFC connection, it was working fine too.
I tried pushing the PO using the FM BBP_PD_PO_TRANSFER_EXEC, it did not solve the problem.
In SRM WEBGUI Process PO - Item data -->follow on documents --> PO status is shown as Archived.
Any inputs would be greatly appreciated. Please throw some light on this issue.
Krishna

Error while reading file entries from the database

Hi there,
We are running a instance of xmii 12 in a VM (VMware) and after somebody shutdown the host machine without shutting down the VM (great idea isn't it?) we keep getting this message when trying to access xMII:
"Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Error while reading file entries from the database."
Any clue? Any suggestion on how we can recover from that?
Thanks a whole lot,
Dom
Server log:
#1.5 #000C29A3B1F20002000000C400000F2800044829A35270F8#1205243578005#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl####n/a##60152160ef7211dcb7a5000c29a3b1f2#SAPEngine_System_Thread[impl:5]_17##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tcmonitoringsysteminfo' application started successfully.#
#1.5 #000C29A3B1F20002000000C500000F2800044829A3527A6C#1205243578005#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer####n/a##60152160ef7211dcb7a5000c29a3b1f2#SAPEngine_System_Thread[impl:5]_17##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###application [] Start of application [sap.com/tcmonitoringsysteminfo] finished successfully on Web Container.#
#1.5 #000C29A3B1F20002000000C600000F2800044829A3527DB5#1205243578005#/System/Server##com.sap.engine.services.deploy####n/a##60152160ef7211dcb7a5000c29a3b1f2#SAPEngine_System_Thread[impl:5]_17##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp over application sap.com/tcmonitoringsysteminfo finished successfully on server 305221750#
#1.5 #000C29A3B1F20002000000C700000F2800044829A3527E03#1205243578005#/System/Server##com.sap.engine.services.deploy####n/a##60152160ef7211dcb7a5000c29a3b1f2#SAPEngine_System_Thread[impl:5]_17##0#0#Info#1#com.sap.engine.services.deploy#Plain###
Operation startApp on application sap.com/tcmonitoringsysteminfo finished on current cluster node for 221 ms.#
#1.5 #000C29A3B1F20002000000C800000F2800044829A3528B49#1205243578005#/System/Server##com.sap.engine.services.deploy####n/a##60152160ef7211dcb7a5000c29a3b1f2#SAPEngine_System_Thread[impl:5]_17##0#0#Error#1#com.sap.engine.services.deploy#Plain###Error occurred while initially starting application sap.com/xappsxmiiear:Error while reading file entries from the database.#
#1.5 #000C29A3B1F20002000000CA00000F2800044829A352922B#1205243578015#/System/Server##com.sap.engine.services.deploy####n/a##60152160ef7211dcb7a5000c29a3b1f2#SAPEngine_System_Thread[impl:5]_17##0#0#Info#1#com.sap.engine.services.deploy#Plain###The synchronization of applications with DB completed for 39304 ms.#
#1.5 #000C29A3B1F200040000000200000F2800044829B290A4F8#1205243834341#/System/Server/SLDService##com.sap.sldserv.DataCollector####n/a##0da42150ef7311dcb908000c29a3b1f2#SAPEngine_System_Thread[impl:5]_7##0#0#Warning#1#com.sap.sldserv.DataCollector#Plain###Communication configuration is incomplete. No data transfer possible until corrected.#

Well thanks for the hint. Actually, the DB was up but corrupted. I managed to solve the bug by re-deploying xMII (using the SDM tool) which kept all my data but redeployed both the config db of (x)mii and the class files.

SAP XI 3.0 - Error while reading the ID of own business system from the SLD

Similar Messages

Maybe you are looking for