In ESH_COCKPIT, while creating Search Object Connectors my job getting fail in sm37

[Former Member]

Hi Experts,

I am creating Search Object Connectors from ESH_COCKPIT, and when i am doing it my connector is going in error.

When i have checked the job in sm37 i found below log.

This is the log when i have created search connector for SRMNXP02_CATALOG

Job started

Step 001 started (program ESH_SE_CONNECTOR_MOD_BGD, variant &0000000000012)

Process Step: Preparation

Information Messages (1)

Environment Details: TREX Version 7.10.65.00, Destination: TREX_DR1, SAP Release 740

Process Step: Change inactive Connector Metadata

Warning Messages (8)

Object type SRMNXP_CAT_HIER, node CAT_TEXT:

There is a field with the same name as the alias CATEGORY_TEXT

Authorization check ESH_CONN_AUTH, auth. obj. field assignments:

Not all authorization fields are mapped to node fields or constants

Object type SRMNXP_CAT_HIER, node CAT_TEXT:

There is a field with the same name as the alias CATEGORY_TEXT

Authorization check ESH_CONN_AUTH, auth. obj. field assignments:

Not all authorization fields are mapped to node fields or constants

Process Step: Update Search Runtime Storage

Information Messages (1)

Prepare search object connector  (COMRUNTIME)

Success Messages (1)

   ODP Indexes 07.01.2016 14:16:57

Error Messages (2)

An exception with the type CX_RODPS_OBJECT_NOT_FOUND occurred, but was neither handled locally, nor declared in a RAISING clause

Error while accessing metadata

Success Messages (1)

   ODP Indexes 07.01.2016 14:16:57

Process Step: Rollback

Error Messages (1)

An exception was raised

Error(s) occurred during connector creation

Job cancelled after system exception ERROR_MESSAGE

Can any body tell me why this is coming?

Thanks,

JP

[Former Member · Accepted solution]

Hi,

Any body have any input here?

Thanks,

JP

[former_member217429 · Accepted solution]

Hi Jay Prakash,

could you please check if the note 2057219 is suitable for you. If this doesn't help I would like to
recommend to create an OSS incident.

Best regards,
Mikhail

[Former Member]

Hi Mikhail,

This is the correct note , I have already implemented this.

Thanks,

JP