Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from EJ1 on Jun 26 at 9:43 AM Still waiting on a response from SAP. In the mean time I continue to research. Looking at the error message in the dev_rout file, it appears the breakdown is the SAP application server I'm trying to connect to is not SNC enabled.
NiSncGetPeer: hdl 18 not SNC enabled where I can see earlier in the log hdl 18 is the application server I am initiating the SM59 connection test from.
I don't recall this being an issue in the past to use transaction snote. I found this link that talks about enabling SNC on the application Server but I am stuck on the snc/identity/as parameter value.
http://documents.software.dell.com/authentication-services/4.1/quest-single-sign-on-for-sap-integration-guide/sap-server-configuration/enabling-snc-on-the-sap-server
Is this a requirement to connect to sapserv2 or is this only if someone want to configure single sign on?
If it is a requirement, in a Windows environment can anyone point me to a good guide to configure and determine the snc/identity/as parameter?
Thanks!
| | | ---------------Original Message---------------
From: EJ1
Sent: Wednesday, June 17, 2015 9:13 AM
Subject: SAP via SNC Fails With A Connection Error
I've searched for an answer to my issue, tried following Note 33135 to no avail. I feel I've successfully followed the guide "Installing the SAPCRYPTO LIBRARY and Starting the saprouter."
However, If I go to transaction SM59 on any server within our landscape and attempt to test my connection to SAP via SNC, it fails with a connection error. I used tcode oss1 to configure the parameters for the OSS connection. Not sure if I put in the public or private ip address for our saprouter. I've seen conflicting information about this.
People can connect from outside our private network to SAP using our router so this seems to be an outbound issue only.
I asked our network person if our firewall could be at fault and was told we do not block anything outbound but our SAP Router server's public ip only allows inbound traffic on ports 3299. I recently updated our SNC certificate and believe I have installed this correctly. Any help would greatly be appreciated. If I need to copy log files here or provide any additional information to help resolve this I will do so. I have opened a system message with SAP, but I we all know how long it takes since this is not a production down situation.
I discovered this issue while attempting setup of a new Solution Manager 7.1 Server in step 2 of SOLMAN_SETUP when it failed on Check Service Connection.
In the saprouttab, for the SNC entry to SAP should I use the sapserv2 ip or "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"?
Thanks in advance for everyone's help and guidance! |
| Reply to this email to post your response. __.____._ |   _.____.__ |
