The error message is Partner "saperp:sapdp00" not reached. This tells us that the SAP Front End cannot find an SAP instance on a server/system called saperp that is communicating via service name sapdp00. These values are derived from the entry you make in the front end software; In this case, saperp is the value from Application Server, and the 00 part of sapdp00 is the value from the Instance Number.
Resolution
1) Find the DNS name or IP address of the machine that is running your SAP instance. This is the value you should use in Application Server. Note that it must be an IP Address or DNS name; a windows hostname (that you would use for sharing windows folders across a network) will NOT work !!!.
2) Find the Instance Number of the SAP system that you wish to connect to (it's fairly rare these days because of virtualisation, but you can install multiple SAP instances on the one logical / physical server).
Additional background:
The ABAP instances communicate over TCP ports 3200 - 3299. The Instance Number of the SAP Instance determines the last 2 digits of the port to be used, so that an Instance Number of 00 uses 3200, an Instance Number of 01 would use port 3201 and so on. However, when you tell the front-end to look on Instance Number 00, it uses the Service Name sapdp00 (and so on). To add to the confusion, in other configurations of the front-end software, the front-end software may look for the Service Name sapABC where ABC is the System Number of the Instance it looking for - In these cases, the last two digits of the port must still equal the System Number the SAP instance was installed under. HOWEVER, when you installed the front-end software it should have updated a file C:\Windows\System32\drivers\etc\services to include a range of Service Names (sapdp00 to sapdp99, plus a bunch of others).
hth
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.