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

Similar Messages

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.

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   !

Hi all,
We are working on SRM 5.0(SP12) and Extended classic scenario.
The problem is that after the PO ís ordered it gives the message " Error while reading PO in backend system Inform system administrator" .
When I check the PO number in R/3 it does not exist.
The number range is correct both in SRM and R/3 (external no. range is ticked).
In RZ20,i find the log:
The error ocurred by processing event SENT_AGAIN with GUID 490F3C0834351AC6E10000000AE48838 and object_id= 3000000307
The R/3 System Version is 4.6C.
Any help is highly appreciated.

Hi,
Thanks for the response.
This problem is hapeening for all PO's in the system.
The no range is smae in both the systems.In SPRO ,howevre we have not maintained the no range in SRM for R/3 system.
Here is the config details:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Number Ranges>SRM Server Number Ranges-->Define Number Range for Local Purchase Orders
EC     3000000000     3999999999     3000000320
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Number Ranges>SRM Server Number Ranges-->Define Number Ranges per Backend System for Follow-on Documents
SAPE02_050     EC            RS
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings-->
Define Transaction Types
ECDP     PO: Direct Material     03     02
ECPO     Purchase Order     EC
I have already gone thorugh note Note 1258634 - Certain events cannot be de-activated.
This note is however valid for SRM 6 and 7.
PO is not reaching R/3 system.
No error in sm58/sm12.
The status in BBP_PD for the PO is :
Stats:
           Status         Description                    Inact
HEADER     I1009          Held                           X
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1043          Ordered
HEADER     I1080          In Transfer to Execution Syst. X
HEADER     I1180          Document Completed
Awaiting your inputs.

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

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

MDS-00521 - error while reading the document in Oracle ADF at Runtime

Hi All,
we are using Jdeveloper Version : Oracle JDeveloper 11g 11.1.1.5.0
we are getting below error message while opening the page at run time.
MDS-00521 : error while reading the document app1/screen1.jsff from metadata repository.
MDS-00569 : unable to read document app1/screen1.jsff from file "D:Oracle/Middleware11115_1/user_projects/domains/j2eeprd1/servers/app1j2eeprd1/.....
WEB-INF/Lib/ADFViewControllerapp1.jar!/app1/screen1.jsff
Note : we disable 1) Enable User Customizations and 2) Enable seeded customization in Project properties -> ADF View
can you please help us to resolve this issue.!
Thanks,

This seems issue with MDS schema. You can try two things:
- Restart everything again (database and admin server as well)
- If above doesn't solve you problem. then there must problem while creating schema using RCU. Run RCU utility again, drop and recreate schema and reconfigure OIM.
This is what I suspect. Other experts can jump in with better solution.
regards,
GP

Message failing in SXMB_moni----Error while reading from the secure store

Hi,
The scenario is as below
A file is picked up from a folder and processed to enrich it.This enriched file is then written back in a different folder.
The message is failing in sxmb_moni while trying to write the file in the folder.
The PI system is a system copy of another system and few of the configuration objects are transported through a tpz file to this PI system.The file receiver channel used to write this file is also transported through this tpz file.
Below is the error seen in 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">AE_DETAILS_GET_ERROR</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText>Error while reading from the secure store: ERROR_U: No service user password found for Adapter Engine</SAP:AdditionalText><SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
Below is Trace log:
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP"></Trace>
<Trace level="1" type="T">error reading secstore:Error while reading from the secure store: ERROR_UNKNOWN: System-dependent data for entry changed: / (SECSTORE,031) </Trace>
<Trace level="1" type="System_Error">Error while reading access data (URL, user, password) for the Adapter Engine </Trace>
</Trace>
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
Is this because PI system is a system copy of another system ?
Regards,
Sneha

Error while reading access data (URL, user, password) for the Adapter Engine
Check out Michal's reply:
Re: URL for Central Adapter Engine
As you said there was a system copy it may be the case that some things were not configured properly

Error while reading access data (URL, user,password) for the Adapter Engine

Hi,
Any idea on below message? I am doing file to file scenario and got the below tarce from 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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.pi1.piserver1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.pi1.piserver1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.pi1.piserver1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Balaji

It looks like the adapter engine is not able to register him self on SLD, you have to check in the SLD the "Exchange Infrastructure" domain, you have to verify restarting the J2EE the adapter engine update the entries in the SLD related to the specific XI Domain.
Launch Visual Administrator >> Server >> Services >> SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Sandro

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 access data (URL, user, password) for the Adapter Engin

Hi all,
I encountered a red flag in sxmb_moni and when I click on the flag, I get the following message:
Error while reading access data (URL, user, password) for the Adapter Engine
Is there any way I can resolve this? thanks all
Regards,
IX

Possible reason is Adapter engine is not registered on SLD. Check in SLD.
You can also try restarting J2EE adapter engine and update SLD entries specific to XI domain.
Lauch Visual admin go to Server > services > SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Finally, if all the above seem to be correct check the userID / pwd for user ID : PI*.

DPM encountered an error while reading from the recovery point used for recovery.

Hi Guys I'm getting this error:
DPM encountered an error while reading from the recovery point used for recovery. Either the recovery point no longer exists or, if you
selected a share for recovery, the path to its contents is missing from the recovery point. (265)
The DPM Server is on Windows 2012 DPM is 2012R2 4.2.1273.0
The Server being backed up is 2012 R2 with DPM Agent 4.2.1273.0
The Server has 3 Data Volumes (C: Drive) and D and E its the D and E drive that i get this error if i try and recover data from DPM. the C Drive is fine. the D and E Drive are different
in that 1 De-dupe is enabled and 2 the Shadow Copies for these Volumes are stored on separate Disks F and G respectively.
I've removed the Protection from drives D and E and reinstated it but every recovery point created
brings up the same error message. I'm not sure where to go next do I need to Protect the Disks that have the Shadow copies on also? Many thanks in advance Gordon.

Hi,
It seems you are in a configuration where the Windows 2012 based DPM server does not understand how to read Windows 2012 R2 Dedup data structure which is what the DPM replica volume is.
See the DPM supported and unsupported scenarios
here under the deduplication issues section.
We have a fix in DPM2012 R2 UR5 that will protect the Windows 2012 R2 dedup volume in a non-dedup state on the DPM Server, but unfortunately that will not allow previous recovery points to be read.
KB3021791-Description of Update Rollup 5 for System Center 2012 R2 Data Protection Manager
Backup job for dedupe-enabled volume on Windows 2012 R2 fails. For example, Data Protection Manager backup might fail for following setup:
Data Protection Manager2012 R2 is installed on Windows Server 2012.
Data Protection Manager is protecting a dedupe-enabled volume on Windows Server 2012 R2.
This also applied to restores as the above was for D2D2T backup that may fail as it needs to read the recovery point to back it up to tape.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

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

Similar Messages

Maybe you are looking for