Saprouter's certificate upgrade

[odysseas_spyroglou]

Hi,

The previews week we received an email from sap notification service stating that sap router certificateu2019s validity will expire soon. We have started and completed the procedure of replacing our existing Certificate with a new one from the SAP Service Marketplace, following the steps described in http://service.sap.com/saprouter-sncadd. Now, when we are trying to use maintenance optimizer from solution manager to confirm files in download basket we receive this error: u201CError during call of SAP back end system (see long text)u201D. When we are trying the RFC connections u201CSAP-OSSu201D and u201CSAP-OSS-LIST-O01u201D we receive a connection error. All these were working before the certificate changes.

Can you help me with this issue? What do I have to do to correct this issue?

Thanks in advanced

[odysseas_spyroglou]

problem solved.

the PIN for the new local.pse file must be the same with the old local.pse

[Former Member]

Hi,

Please, go to transaction SM59 and check if the username and password for those RFCs are correct.

User: OSS_RFC

password: CPIC

I hope it could help you.

Best regards,

Tomas.

[odysseas_spyroglou]

HI,

Thnaks for your answer but do I have to change these information? The RFC connections were working before I renew the certificate with the user name and password that is saved. Do I have to change this user name and password?

Edited by: Odysseas Spyroglou on Nov 9, 2009 11:17 AM

[former_member185031]

check the dev_rout file under saprouter directory. I guess either your certificate has not been installed correctly or your Sap router has not been running properly. Check the file for infomation.

Regards,

Subhash

[odysseas_spyroglou]

This is my dev_rout contents, Can you help me?

-

---

trc file: "dev_rout", trc level: 1, release: "700"

-

---

Mon Nov 09 12:43:38 2009

SAP Network Interface Router, Version 38.10

command line arg 0: F:\usr\sap\saprouter\saprouter.exe

command line arg 1: -r

command line arg 2: -W

command line arg 3: 60000

command line arg 4: -R

command line arg 5: F:\usr\sap\saprouter\saprouttab

command line arg 6: -K

command line arg 7: p:CN=sap.inergo.gr, OU=0000867692, OU=SAProuter, O=SAP, C=DE

SncInit(): Initializing Secure Network Communication (SNC)

PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/64/64)

SncInit(): Trying environment variable SNC_LIB as a

gssapi library name: "F:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll".

File "F:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.

The internal Adapter for the loaded GSS-API mechanism identifies as:

Internal SNC-Adapter (Rev 1.0) to SECUDE 5/GSS-API v2

main: pid = 4772, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)

reading routtab: 'F:\usr\sap\saprouter\saprouttab'

Mon Nov 09 12:44:02 2009

• ERROR => SncPEstablishContext() failed for target='p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE'

[sncxxall3374]*** ERROR => SncPEstablishContext()==SNCERR_GSSAPI [sncxxall.c 3340]

GSS-API(maj): Miscellaneous failure

GSS-API(min): Invalid password (PIN)

Unable to establish the security context

target="p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"

<<- SncProcessOutput()==SNCERR_GSSAPI

• ERROR => NiSncIInitHdlSecurity: SncProcessOutput failed (rc=-4;00000000002B4810) [nisnc.c 1098]

• ERROR => NiSnc2Connect C1/-1, 194.39.131.34 (rc=-17) [nirout.cpp 2816]

• ERROR => NiRClientHandle: NiRExRouteCon for C1/-1 'solmanager.INERGO.LOCAL' failed (rc=-17) [nirout.cpp 2243]