Transporting OSS Notes from Dev to QA returns error

[jack_wong]

Hi,

I have implemented all these notes in Dev:

1448397

1453128

1462423

1465685

1472991

1478699

1486208

1490183

1495277

1512748

1540869

1550964

1558355

1564254

1568563

1575454

I don't get any error during implementation in Dev.

When transport to QA, it returns error like:

Authorization check CP_USER_INCL:
Navigation path 48469D158E5D0117E10000000A421694 does not exist
Authorization check O_INCL_1:
Navigation path 488D143E21166CB2E10000000A421693 does not exist
Authorization check S_ALL_1:
.....

Errors occurred during post-handling ESH_OM_TRANSPORT_IMPORT for SEST L
ESH_OM_TRANSPORT_IMPORT belongs to package S_ESH_ENG_OBJ_MOD_REP
The errors affect the following components:
   BC-EIM-ESH (NetWeaver Enterprise Search)

After the transport failed, I couldn't access ESH_COCKPIT anymore.

It will return a dump saying:

System with connection GUID xxx has no connection data.

I tried to delete search connector via SE38 ESH_ADM_INDEX_ALL_SC also return the same error.

Anyone experienced this before?

I have already raised an OSS message to SAP waiting for their reply.

Thanks

Jack

[Former Member]

Hi Jack,

do you get an answer from SAP to your OSS Message?

Can you please poste me the answer?

Thanks Alex

[lukemarson]

Hi Jack,

Do you have the authorization to make the changes in these notes in QA? Maybe you can ask Basis to import your transport into QAS?

This is not the correct forum for this so I will ask the moderator to move it to SAP HCM. In the meantime I'll see if I can help.

Thanks,

Luke

[jack_wong]

Hi Luke,

Thanks for your reply.

The transport process is done by BASIS. I don't have authorization to do this.

I raised my question here because I hope if someone has the same error as mine could share the solution

For further information, all the OSS notes are in the same transport request.

I hope this will not jeopardize the sequence...

Regards

Jack

[lukemarson]

Hi Jack,

No it should not. Did you check if any of the SAP notes require manual fixes? Maybe there is a manual fix that is required before you import the SAP notes - this is possible for 1 or 2 of the SAP notes you have implemented.

Please review them all and make any manual changes in the target system before import, especially if the SAP note requires this.

Best regards,

Luke

[jack_wong]

Problem is solved by BASIS after implementing several OSS notes suggested by SAP.

[lukemarson]

Hi Jack,

What were the SAP notes SAP asked you to implement?

Thanks,

Luke

[jack_wong]

Quote from the OSS message:

1457940 Transporting software components: Error in after-import
1476894 Transporting software components: Paths are lost
The reason for the error messages was a problem with the sequence
of the handling of the involved entities like templates, authorization
checks etc.
I see no harm in implementing the following additionally
1465481 Transporting software components: Dump in after import
1441080 Termination when importing Enterprise Search models

Regards

Jack

[lukemarson]

Thanks for posting Jack, hopefully this will help the community.

I am aware of the first 2 notes already - I should've known they were related!

Best regards,

Luke