Basis Errors and Solutions

SR Provider system does not find IS services

July 12, 2009 at 2:15 am

[a] [be] [can] [configured] [consumed] [Enterprise] [from] [need provider] [not] [provider] [provider sqloledb] [Services] [SR] [System] [to] [use] [wmi provider host]

1. Proxy for data provider services is incompleteSymptom The proxy for the data service of the data provider services is incomplete. Other terms DPS, data provider services, Enterprise Search Reason and Prerequisites See above. Solution o SAP NetWeaver 7.20...
2. Termination when indexing Data Provider Services (DPS) dataSymptom When indexing Data Provider Services data, the termination “OBJECTS_OBJREF_NOT_ASSIGNED” occurs in the class CL_ESH_DPS_TOOLS method COMPLETE_MES_HANDL_ERR_PROV_DA. Other terms DPS, Data Provider Services, Enterprise Search Reason and Prerequisites See above. Solution o...
3. Can not import / export deleted objects in PI DirectorySymptom The import of deleted configuration objects fails when the imported object has a reference to an already deleted configuration object. For instance, if one performs an import of configuration object /e.g....
4. BW Upgrade Errors : System changeability errorSymptom An error occurred while activating BW object. When you check the logs in RSTCO_ADMIN , you find the following error message: “System is set to not changeable; objects cannot be changed”...
5. Further corrections in DPS scenario if NextByTimestampSymptom During indexing of data provider service data, among other things, the termination GETWA_NOT_ASSIGNED occurs in the class CL_ESH_DPS_D_NEXT_BY_TIME_RES, method GET_DATA_NEXT_BY_TIME_RESPONSE. Other terms DPS, data provider services, Enterprise Search Reason and Prerequisites...

Symptom

Enterprise Services published in the Services Registry from the PI directory can not be found from a provider system configured to use the same services registry as the one where the enterprise services have been published.
Other terms

Enterprise services can not be consumed from a provider system configured to use SR
Reason and Prerequisites

The reason for this failure is that the type of the provider (IS)
Solution

The issue has been fixed in 711 Support Package 4. Patches have been produced for SP2 and SP3.
In Netweaver 711 Enterprise services should be consumed from a provider system which has type “Non SAP”. The administrator should configure the provider system the following way: Its type should be set to “Non SAP”.
The System name should match the name of the IS phsyical system published in the SR and the System ID should match the SLD ID of the published system.
For isntance if there is a physical system of type IS published the SR.
With the following system details:
Name: XYZ_XPI
SLD ID: XYZ.SystemHome.samplehostname
Logical key: XYZ.SystemHome.samplehostname#XPI
The provider system should be maintained with the following settings:
System name: XYZ_XPI
System ID: XYZ.SystemHome.samplehostname

Permalink