on 11-05-2007 1:21 PM
Hi,
SAP-OSS connection (as tested through SM59) suddently failed to work and constantly throws the following error message:
Error Details Error when opening an RFC connection
Error Details ERROR: SNC processing failed: ?
Error Details LOCATION: SAProuter 37.11 on sapdev
Error Details COMPONENT: NI (network interface)
Error Details COUNTER: 44
Error Details MODULE: nisnc.c
Error Details LINE: 502
Error Details RETURN CODE: -104
Error Details SUBRC: 0
Error Details RELEASE: 640
Error Details VERSION: 37
Our server's name is "sapdev".
My question: can this error be related with SAP side or is it strictly our company's networking issue? I've contacted our IT office already; however, they didn't notice anything suspicious.
Also, where can I find a table with error return codes listed? To decipher what -104 in this case means?
Thanks
Janek
Hi Janek,
could you please provide us more information regarding the configuration of your SAProuter?
In the meantime the SAP Note 30289 contains a lot of technical information.
Regards,
Loukas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let's see the issue from the beginning:
Have u followed this procedure for your installation of SAP router?
http://help.sap.com/saphelp_nw04s/helpdata/en/4f/993172446d11d189700000e8322d00/frameset.htm
Is the relevant service running?
Could you find whether a routing permission table has been defined? Normally this is some entries like:
P/S/D <source host> <dest host> <dest serv> <password>
<source-host> and <dest-host> could be SAProuters.
SAProuter checks its route permission before the connection is set up. If the password and route SAProuter has received correspond to the entries in the route permission table, SAProuter sets up the connection.If not it thows a denial message. unfortunately the error u have appended is not much of help for the moment.
You are probably talking about the "saprouttab" file. Yes, it's defined and has the following contents:
SNC-connection from and to SA
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 3299
SNC-connection from SAP to local R/3-System for Support
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" XXX.XXX.XXX.XXX *
P sapdev 194.39.131.34 3299
P sapdev YYY.YYY.Y.YY PORTNUMBER
P * * *
I also checked "dev_rout" file (the log file), which lists the following error message:
LOCATION SAProuter 37.11 on sapdev
ERROR GSS-API(maj): <b>The referenced credentials have expired</b>
GSS-API(min): Validity date of certificate is invalid
target="p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"
TIME Tue Nov 06 08:48:54 2007
RELEASE 640
COMPONENT SNC (Secure Network Communication)
VERSION 5
RC -4
MODULE sncxxall.c
LINE 3411
DETAIL SncPEstablishContext
SYSTEM CALL gss_init_sec_context
ERRNO
ERRNO TEXT
DESCR MSG NO
<b>DESCR VARGS GSS-API(maj): The referenced credentials have expired;;;;
;;;;GSS-API(min): Validity date of certificate is invalid;;;;</b>
;;;;target="p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"
DETAIL MSG N
DETAIL VARGS
COUNTER 3
<<- ERROR: SncProcessOutput()==SNCERR_GSSAPI
ERROR => NiSncInitiate: SncProcessOutput (rc=-4) [nisnc.c 502]
ERROR => NiSnc2Connect C0, 194.39.131.34 (rc=-17) [nirout.cpp 2607]
It seems you are using SNC and most likely you are using external product (secude?). The certificate used for the secure logon seem to also have expired.
Could you check with the admin who did install it ? Definitely it is an issue with the third party security software which is used for the secure communication using the certification.
Rgds,
Loukas
Hi,
Clearly we can see that your snc certificate is expired.So pleae do the neccessory steps for renewing thesnc.get back to me if you need more clarrifaction
ERROR GSS-API(maj): The referenced credentials have expired
GSS-API(min):<b> Validity date of certificate is invalid</b>
target="p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"
TIME Tue Nov 06 08:48:54 2007
Regards,
Arun
Points are back, points are assigned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Janek,
Check the settings at OSS1 -> Paremeter -> Technical settings
Make sure that the name, ip address, and instance number are ok... then try the connection again.
Regards
Juan
Please reward with points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.