Symptom:

case I

• I get ObjectNotExistsException when clicking on a service in the Application Communication UI after updating to a newer SP.
• I get ObjectNotExistsException when clicking on a service in the Application Communication UI after redeploying an application/DC.

case II

• I get ObjectNotExistsException when clicking on a service definition in the Single Service Administration UI.

case III

• The configuration of the Service Group fails with ObjectNotExistsException

case IV

• I can see re-occuring errors in the default traces like this one:

  Message: Could not get default logical port
  [EXCEPTION]
  com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: No default logical port.

case V

• I get ObjectNotExistsException when deploying an application with service references and at least one of these service references points to a service group, which is declared in another application/development component.

case VI

• I get ObjectNotExistsException in the trace files similar to this:

  Caused by:
  com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException:
  SOAObjectId
    type = CONSUMER_GROUP
    local = new_undefined_sg_2
    ns    = sap.com/tc~bpm~myapp~main
    processingState = INITIAL
    delete = false
    (processingTraceId=null, processingLogId=null)
  at com.sap.esi.esp.service.server.SOAConfigurationManagerImpl.read
  (SOAConfigurationManagerImpl.java:178)
  at com.sap.esi.esp.service.server.mass.SOAObjectAccessor.readSOAObject
  (SOAObjectAccessor.java:191)
  

  In NWA, Business Scenario Communication view I can see similar error messages.

Problem Description:

case I

This issue occurs only in case of an application containing both a service reference and a Web Service.

After deployment I assigned a communication profile to the service in the Application Communication UI. The configurations were generated successfully and could be seen in the UI. After redeployment of the application when I clicked on the same service in the same UI, I get the exception.

case II

The combination of the name of the service and the name of the application/DC is too long, which causes this failure.

case III

After redeployment of an application/DC containing a JAX-WS Proxy or a CAF application and a Service Group (which was already assigned to a provider system before the redeployment) the configuration of the Service Group fails with an exception com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException

case IV

There is no default logical port for the ServicesRegistrySi proxy.

case V

The application that is being deployed contains a service reference that points to a Service Group, which is declared in a different application/DC. In order this to work at deployment, one needs to have a deploy and a runtime dependency to the application that contains the service group.

case VI

The default Business Scenario contains Service Group(s) with invalid service references.

Solution:

case I

1. Update your system as follows:
   • For NetWeaver CE 7.2, to SP6 (or later).
   • For NetWeaver 7.3, to SP4 (or later).
2. There is also a workaround to undeploy the application completely, then deploy it, and create the provider assignment again (assign the service to the profile).

case II

See SAP Note #1496077 – Missing service definition

case III

See SAP Note #1383750 – After update of WSClinetApp with ServiceRef, assignment fails

case IV

In general this will not stop your system from working properly.
In order to get rid of the error messages in the default traces, you have to set a default logical port.
Go to NWA -> SOA Management -> Application and Scenario Communication -> Single Service Administration -> Consumer Proxies tab -> Search for "ServicesRegistrySi" proxy -> set the logical port as default.

case V

You have to add a deploy+runtime dependency to the application that deploys the Service Group.

case VI

1. Go to NWA -> Troubleshooting -> Logs and Traces -> Log Configuration and set Debug severity for the tracing location com.sap.esi.esp.itsam.ui.soa.biz. If that location is not visible use some parent location (com.sap.esi.esp.itsam.ui, com.sap.esi.esp.itsam, etc.). Then click "Copy to Subtree" button and save the configuration.
2. If you do so and visit again Business Scenario Communication then you will see a default configuration appearing.
3. Edit and save any entry here. This will regenerate the business assignments, and so the error should not appear any more.
4. Revert the severity you have set in point 1.

Additional Information

case I

The system displays the following error:

case IV

The system displays the following error:

case V

The system displays an error whose root cause is: