Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from medhaindia on Jun 23 at 1:34 PM Hi All,
After Raising an OSS Message to SAP they will just ask you to check the below things. Same Problem i have raised to SAP and they have provided the same commands to execute in our server
1) Connection of Public IP (Check Ping from your Server and Ping of IP provided by SAP)
2) SM59---OSS---connection Test--If the connection Test is Ok then Test the SNote Transaction to download a Note for confirmation from your side.
3) OSS1-----Technical settings----Change the Public IP to what ever you connected and SAP router IP in its Fields (It is Not Mandatory when the SAP is Not connected from this Transaction it will ask Publi/Germany or any Other sap is not recommending this now too)
4)saprouttab file in saprouter folder
5) saprouter -r -V 2 -K "p:CN=vm-bet-saprtr, OU=0000275347, OU=SAProuter, O=SAP, C=DE" (check distinguished name is Ok)---it will just say wild character and no login active
6)Go to service.sap.com/system-data---Systems Data overview---Run Report---You can see your SAP systems in that Overview---click on system which you want to connect to router to SAP
---Maintain your system data in that system which you want router to connect to SAP
-----In that you can find the SAP Licenses,To Renew Maintainence Certificates, SAP Router Tab -----Enter Public IP and Ports,
------Enter Public IP of your Router connection in the Router Fields-----Port(3299)----
---------Go for Maintain service connection----you can see several thing just click on R3 Support-----save ome back
-------You can R3 Support in Open/Close Connection-----Click on R3 support there---- Provide No of Days and Hours to connect router----Open connection
7)Install Service connection.exe file in your Desktop system
8) you can also see in that maintain service connection tab (SEMI AUtomatic opening-----click on that and also provide no of Days----switch on SOA and it is allowed
9) if the Old saprouter certificate is expired you require .der file to re-install of Old Certificate with new One as in the earlier mail mentioned about it.
After all these router needs to be started and if still any thing than this SAP OSS is already raised by you they will look after this if all the above are not cleared your problem
--
Thanks,Regards,
P.E.Harsha.,
| | | ---------------Original Message---------------
From: EJ1
Sent: Tuesday, June 23, 2015 1:12 PM
Subject: SAP via SNC Fails With A Connection Error
I had also opened an incident with SAP, I was asked by SAP to do the following:
Dear Customer,
Could you stop the saprouter process (saprouter -s) and restart it
temporarily using the following options?
saprouter -r -V 2 -K "p:CN=vm-bet-saprtr, OU=0000275347, OU=SAProuter,
O=SAP, C=DE"
Try to test the RFC connection to SAPOSS (SM59 -> R/3 / Abap
Connections -> SAPOSS) and send us the following information, in order
for us to troubleshoot the connection problem:
o Output of the command 'sapgenpse'
o Output of the command 'sapgenpse get_my_name -n all'
o Output of the command 'sapgenpse seclogin -l'
o Output of the commands
saprouter# niping -c -O -S 3299 -H 194.39.131.34
saprouter# niping -c -H /H/<SR_LAN_IP>/H/ 194.39.131.34/H/localhost
o Files dev_rout (after the test access to SAPOSS) and saprouttab
o Technical settings in Tcd OSS1 (Parameter -> Techn. Settings)
I provided all the information requested and waiting for a response. Once resolved I will post the resolution in the hopes it may help others. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
