SAP Knowledge Base Article - Preview

2927353 - Known issues with Process Servers not starting - INVALID, DISABLED destinations

Symptom

  1. After an upgrade to 9.1.0.5 you receive error
    • <SID>_ProcessServer; stopped unexpectedly. Details: java.lang.IllegalStateException: No SAP system object on process server <SID>_ProcessServer or JCoException: (106) JCO_ERROR_RESOURCE: Destination Redwood_<SID>....does not exist (in pre 9.1.0.6)
  2. After process server re/start you are seeing errors similar to
    • SAP Service for instance<SAP SYSYTEM NAME> on process server <PS name>## Initialization of repository destination Redwood_<SAP SYSYTEM NAME> failed: Connect from SAP gateway to RFC server failed Connection parameters: TYPE=B DESTINATION=Redwood_<SAP SYSYTEM NAME> MSHOST=<HOST NAME> SYSNR=<system number> TRACE=0
    • The word INVALID appears in front of connect string e.g INVALID MSHOST=<HOST NAME> SYSNR=<system number> TRACE=0
  3. The word DISABLED appears in front of connect string e.g DISABLED MSHOST=<HOST NAME> SYSNR=<system number> TRACE=0 and you can no longer edit the SAP System conenct string
  4. Upgrades to 9.1.1.x or adding a new SAP system you are seeing
    • Operator Message Service "SAPR3Service" on process server <PS name> stopped unexpectedly. Actions Partition GLOBALFull Text Service "SAPR3Service" on process server <PS name> stopped unexpectedly.Details:Exception: 104: Destination <SAP SYSTEM NAME> does not existat


Read more...

Environment

SAP Business Process Automation by Redwood

Product

SAP NetWeaver 7.5

Keywords

JCO_ERROR_RESOURCE, Destination Redwood, DISABLED, INVALID, INVALID MSHOST, does not exist, process server, starting, Exception: 104 , KBA , XX-PART-REDWOOD-BPA , SAP Business Process Automation by Redwood , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.