Symptom
- Resource usage is high on the address server.
- Real-time jobs are running long and the calling application times out.
- Long running jobs that do address correction and standardization.
- Possible Address Server error: "CommandHandler::executeAdminConfigProfile 0 Profile '<number>_emea' already exists!"
- Various errors in access server and web server logs if using real-time.
- Catalina log error: "XML document structures must start and end within the same entity."
- Webservices Error: "[ SEVERE ] Could not retrieve the body of the SOAP request. Error: XML document structures must start and end within the same entity."
- Webservices Error: "[ SEVERE ] Error after call to ProcessRequest. Exception: Could not retrieve the body of the SOAP request. Error: XML document structures must start and end within the same entity."
- Webservices Error: "[ SEVERE ] Web Service call failed. Fault returned to client: Unable to connect to access server <access server host>:<access server port>. Error: Timeout waiting for idle object. Ensure the access server and the SAP BusinessObjects Data Services service are configured and running properly."
- Access server Error: "Unknown: ERROR: Broker could not find the destination client: (BODI-48) (BODI-300001)"
- Access Server error: "Flow became invalid during waiting for request (BODI-300137)"
- Access Server error: "Unknown: ERROR: Problem killing Jobs: Error: RWSocketError: in RWSocket::connect: CONNREFUSED (BODI-300001)"
Read more...
Environment
- SAP BusinessObjects Data Services 12.2.2.x and earlier
- AIX
Product
SAP Data Services XI 3.2
Keywords
DSXI, BODS, 0150723, 150723, ADAPT , KBA , EIM-DS , Data Services , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.