Information Steward Metadata initialization error

[former_member799084]

Hi experts,

Since a few days I get the following error message when I want to create a new connection (via CMC) for SAP Information Steward or add tables to an existing connection. This problem came all of a sudden, our system was running without errors before and was an operational application. The system is managed via the HEC, so I have little access, only via CMC

Here the error message from CMC:

Here is an overview of the services caterories and their assigned servers:

Core services:

Enterprise Information Management:

Promotion Management Services:

I also checked those to blog post:

https://me.sap.com/notes/0002046768:

1. Go to Servers => Service Categories => Core Services
2. Right-click EIMAPS
3. Select Properties (stop the process)

I have done that and stopped all the listed core services with APS in name, afterwards I checked the port entered under the Data Services Metadata Browsing Service Configuration section. Right now there is "4010" maintained, I just let it untouched.

4. Go to the Data Services Metadata Browsing Service Configuration section In Listener Port - set this to your choice of a permitted port.

5. Save and close

6. Start the EIMAPS again and retest.

I started everything again, but unfortunately with no success the error message remains the same.

https://me.sap.com/notes/0002815606:

"There were two EIM Adaptive Process servers started in this environment, both with the same services added to them. One of the EIM APSs indicated bad health."

So I checked the running APS servers and regoniczed that there are really two of them having exactly the same services assigned. The APS.Auditing and APS.Data having both the services below assigned. Both servers having good health, nevertheless I stopped one and restarted the other etc. but this didnt helped at all.

To my question:

Is anyone aware of this problem and does anyone know a workaround? Is there a certain order in which services have to be stopped and started or does the job server have to be restarted at the end?

Could the port setting possibly be wrong?

Please, I am glad about every hint!

KR

Lukas

[DayaJha]

Thanks Lukas for the update.

In that case raise an OSS message with SAP shared all details and request SAP HEC team to fix this issue or shared the logs for further investigation.

Regards,

Daya Jha