SAP GUI 'sapdp00' error

[Former Member]

When I try to connect through sapgui640 I get the following error:

Service 'sapdp00' unknown

Component: NI

Release: 640

Version: 37

Module: ninti.c

line: 494

Method: NiPGetServByName2: service 'sapdp' not found

Return code: -3

Counter: 1

I had no problem logging on yesterday. I did install Norton Anti-Virus which I have subsequently uninstalled. I also uninstalled and reinstalled SAP GUI but the same problem continues to occur. Anyone have any suggestions?? Help!!

[Former Member]

Message error:

'partner 127.0.0.1:sapdp00 MS Loopback Adapter err 10061'

not reached WSAECONNREFUSED: Conection refused.

'partner 192.160.1.10:sapdp00 not reached err 10061'

WSAECONNREFUSED: Conection refused.

u2022 OS: Vista

u2022 Iu2019ve installed SAPNWABAP701SR1_TRIAL (SAP NetWeaver 7.01 Application Server ABAP Trial)

but it doesnu2019t work:

The installation has created 2 account:

u2022 SAPServiceNSP

u2022 Nspadm

My steps were the following:

1) Installation SAPNWABAP701SR1_TRIAL:

D:\sapnw_7.01\SAPNWABAP701SR1_TRIAL\SAP_NetWeaver701SR1_2008_Installation_Master\IM_WINDOWS_I386

2) Installation Max Db application server: MAX DB (7.7.6.7):

D:\sapnw_7.01\SAPNWABAP701SR1_TRIAL\Additional_Tools\maxdbtools701SR1\DBM76.exe

3) Open MaxDB  istance NSP doesnu2019t appear:

4) Execute Max DB Installation manager (installing Serve+Client):

D:\sapnw_7.01\SAPNWABAP701SR1_TRIAL\MaxDB_77_SP6_Build07_RDBMS\DATA_UNITS\MAXDB_WINDOWS_I386\SDBSETUP.exe

5) Start Database manager  NSP Online appear:

6) Just to try I Saved :

C:\Users\nspadm\Documents\sdb\DBM\NSP

7) Close: Database manager

😎 Open Database manager: "C:\Program Files\SDB\DBM\DBMGui3.exe"  istance NSP doesnu2019t appear:

9) Installation Ms loopback adapter

10) Active Microsoft loopback adapter : I've put an IP fix (es: 192.168.1.10)

10) To change file host :

C:\WINDOWS\system32\drivers\etc\hosts

127.0.0.1 localhost  192.168.1.10 localhost

11) To change file services:

C:\WINDOWS\system32\drivers\etc\services

To add:

sapdbni72 7269/tcp

sapmsNSP 3600/tcp # SAP System Message Server Port

There were already:

#sapdp00 3200/tcp

#sapgw00 3300/tcp

12) Connect SAPGUI 7.10 (with application server: 192.168.1.10):

Message error:

'partner 127.0.0.1:sapdp00 MS Loopback Adapter err 10061'

not reached WSAECONNREFUSED: Conection refused.

13) ...after installing the application server you can log into the system via web gui at http://localhost:8000/sap/bc/gui/sap/its/webgui?sap-client=000 with user bcuser and password minisap.

It doesn't work!

I'm sorry I'm new of this forum..

Please help me!

Thanks to all in advance!

[Former Member]

thanks the idea of changing the registry file, with the expandable string and giving the value of win32 really works

thanks a lot

regards

vivek

[Former Member]

Hi Everybody

I tried all the possible solutions u all have given but "none work". I am afraid I may have goofed up some register entries in the process of trouble shooting.

I also uninstalled MSN 7.5 and reinstalled SAP checked the register for DataBasePath etc all are intact, downloaded Regmon and followed the steps..............but the problem persists.

"PLEASE HELP" do add in as much details and steps as possible.

Regards

PKR

[Former Member]

Hi All,

Previously I have changed the databasepath entry to c:\windows\system32\drivers\etc and it works for a few days and failed.

I have not tried changing the registry type to REG_EXPAND_SZ yet.

My question is: Why does the problem gradually occur, does it mean that everytime MSN 7.5 is activated, it will gradually changed the registry type to REG_SZ.

Moreover I have users with MSN 7.5 and their SAP GUI is running fine. (Is MSN 7.5 connection troubleshooter really the root of the problem... because shouldn't it happen immediately instead of gradually ?)

Will SAP come out with a patch for this problem ?

Please advise. Thank you

[Former Member]

Hi All,

Can anyone help ? My users are facing the same problem as well. I had changed the registry entry: Databasepath to C:\WIndows\System32\Drivers\Etc instead of

%SystemRoot%\System32\drivers\etc and the users were able to login but after 1 or 2 weeks they can't login as well, even after changing the registry entry again.

Can anyone help ? Is there a permanet solution to the problem ? Is MSN Messenger 7.5 the cause of the problem ?

Please help.

Thank you

[Christian_Cohrs]

Hi,

as John mentioned there is an OSS note on this, number 882741.

I've posted the content below. Please have a look and let us know if the problem is not fully solved when following the note instructions.

Best regards,

Christian

SAP Note No. 882741 29.09.2005 Page 1

________________________________________________________________________

Number 882741

Version 10 from 26.09.2005

Status Released for Customer

Set on 26.09.2005

Language EN

Master language EN

Short text SAP Logon: Logon balancing error, service 'sap...'

unknown

Responsible

Component BC-FES-GUI

Graphical User Interface

________________________________________________________________________

Long text

Symptom

Some users cannot longer connect SAP GUI to any SAP systems e.g. via SAP

Logon, SAPShortcut etc. although they have not made any update to either

SAP GUI or SAP system. The attempt to connect to the SAP system ends

with error messages like this: "Logon balancing error: could not

connect to message server (rc=9)", "service sapmsXXX unknown" or

"service sapdp## unknown".

The detailed error information is as follows:

Error: service 'sap...' unknown

...

Component NI (network interface), ...

rc = -3, module ninti.c, line 463

Detail NiPGetServByName: service 'sap...' not found

System Call getservbyname

Other terms

service sapmsXXX unknown,logon balancing,service sapdp## not found

error,etc/services,drivers\etc\services,getservbyname, sapdpxx

MSN Messenger 7.5,Connection Troubleshooter

Reason and Prerequisites

The reason for this malfunction is, that the datatype of the registry

value

HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\DatabasePath

was changed from REG_EXPAND_SZ to REG_SZ.

The following programs are currently known to cause this registry

change:

- Starting MSN Messenger 7.5 "Connection Troubleshooter" (Build

7.5.0299).

- Installation of MSN Messenger 7.0 or MSN Messenger 7.5 with

the option automatic scanning and configuration of ports.

This modification prevents the expansion of environment variables in the

value of the parameter. Therefore,

%SystemRoot%\system32\drivers\etc

is not translated to

c:\windows\system32\drivers\etc

and the services database is not found by the API function

Page 2

getservbyname().

If you have checked the datatype of registry value DatabasePath and it

is REG_EXPAND_SZ, apply SAP Note 52959 to check the appropriate settings

in the services file.

Solution

Start the registry editor and rename the registry value

HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\DatabasePath

Create an Expandable-String Value (REG_EXPAND_SZ) with the same name and

value.

If more PCs are affected, you can export the correct value to a .reg

file and import the .reg to other PCs.

If you have the same problem although you have not installed Microsoft

MSN Messenger 7.5, create a customer message, collect the following

information and attach it to the message according to note 541726 or

upload it to sapservX (see note 40024):

o Scan your workstations for spyware and viruses with up-to-date

virus definitions. If you already did that what was the result ?

o What software has been installed recently ? (client software,

Firewall)

Create a registry export of the following key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Unin

stall

on the affected and the unaffected PC respectively and attach the

two .reg files to the customer message.

o Are the users on the affected workstations logged on with

administrative credentials (local administrator ) ?

o Create an MPS Report Networking and Setup Perf of an affected

workstation so that we can check if they use an software in

common.

You can download the Networking MPS Reporting Tool at:

http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-

a579-30b0bd915706/MPSRPT_Network.exe

You can find a short description about the features of the tool

at:

http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-

a579-30b0bd915706/MPSRPT_Network_Readme.txt

The Setup Perf MPS Reporting Tool is located at:

http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-

a579-30b0bd915706/MPSRPT_SETUPPerf.EXE

Run this report too on identically configured workstations, which

are not affected.

Page 3

If you have already changed back the DatabasePath parameter and if after

a while the value was switched back to REG_SZ perform the following

steps to help us to identify the reason for this problem:

o Switch the datatype back to REG_EXPAND_SZ

o Download Regmon from http://www.sysinternals.com on the affected

machines

o Enable auditing on the affected clients

o Modify the settings of the eventlog so that no important entry is

deleted!

Open Regedit and highlight

HKLM\System\CCS\Services\TCPIP\Parameters

Right-click on "Parameters" and choos "Permissions" and click

"Advanced".

Choose "Auditing" and "Add".

Add "Everyone" and select "this key only" under "Apply onto".

Check the boxes "Set Value" and "Delete" and click "OK".

Apply these settings

o Start Regmon and apply the correct filter settings:

Press the "magnifying glass" button to stop the monitoring.

Press the rubber button to delete all logged entries.

Go to "Options Filter/Highlight".

Copy the following value to the include field:

tcpip\parameters\databasepath and click "Apply".

Start Regmon by pressing the magnifying glass button

o Verify that logging starts when you double-click the TCPIP Key in

regedit!

If the datatype will be changed again, provide us the output of the

monitoring tools.

________________________________________________________________________

Note is release independent

Further components

BC-OP-NT

Windows NT

________________________________________________________________________

Reference to related Notes

Number Short text

____________________________________________________________

52959 sapms..., sapdp.., sapgw.. unknown (or not found)

________________________________________________________________________

[Former Member]

Hi,

I made the necessary changes in terms of registry editorby name type and data . Currently DataBasePath shows Type as REG_EXPAND_SZ and Data at c:\windows\system32\etc.

<b>I removed MSN 7.5 and disabled my firewall .</b>

But still I am getting the following messages :

service 'sapdp00' unknown

Time : Current time

Component NI(network interface)

Release 640

Version 37

Module ninti.c

Line 505

Method NIPGetservByName2: service 'sapdp00' not found

Return Code -3

Systemcall getservbyname_r

Counter 1

Any suggestions will be welcomed .

Thanks

[JPReyes]

Have you tryed to use saprouter string and replace sapdp00 for 3200 to see if you have a Name resolution problem?? i have seen this issue several times.

Usually

\H\Server\S\sapdpXX\H\

You can try with

\H\server Ip\S\32XX\H\

where XX is the system number.

Hope this help

Juan Reyes

[Former Member]

Hi,

Thanks for your reply but sorry to ask a silly question . Where can I find the server details. Please note that I am trying to logon from my home and have a ADSL router.

Thanks

[JPReyes]

If you're connected from home... i guess you're using some sort of VPN tunnel and you have the sapgui in your PC...

Then... on the Gui click on the system and click on properties, then change SAP Router String.

[Former Member]

Hi Juan,

Indeed I have a SAP GUi logon where the SAP Router String is empty .

Thanks

[JPReyes]

Ok...

you can try with adding this on the SAP Router String field.

/H/<saproutername>/S/sapdpXX/H/

or

/H/<SAP_router_IP_Address>/S/32XX/H/

Been XX the system number

[Former Member]

Hi,

Now I am getting a different message with a slight delay :

Host unknown

Rest of the message is same as before .

In the SAP_Router_IP I put the hosting server ip address .

I am trying to connect a sandbox testing server in the US .

I checked the connectiong thru telnet and its working fine.

Regards

Sanjay

[former_member273310]

I can't remember if I've seen this solution before, but one could update the saplogon.ini file in c:\Windows.

Match the item number in the MSSrvPort section with the item in the Database section. If you are using the standard port numbers then you would just hardcode the port number in each MSSrvPort line entry.

Atis

[Former Member]

Hi,

Many thanks for your suggestion . But it is still not working .

Message : Server Unknown

Which can't be true because when I try to check through telnet it is responding .

Don't know what to do .

Regards

[Former Member]

Hi, Finally it worked . Renamed the services file and it worked . Thanks to all you for your kind support in solving this issue .

Regards

Sanjay

[RonieO]

Hi,

had the same problem with Vista and Windows 7. Solution was :

go to C:\Windows\System32\drivers\etc and edit the services file like this (add)

sapdp00 3200/tcp #SAP Server

sapgw00 3300/tcp #SAP Gateway

Using SAP Gui 710 Final Release Patch level 7.

Ron

[Former Member]

Does anyone know what might cause the Registry Entry "HKEY_LOCAL_MACHINE/SYSTEM/controlset001/Services/Tcpip/Parameters - DataBasePath" to change from type REG_EXPAND_SZ to REG_SZ? This is causing the %SystemRoot% resolution problem as mentioned above, and it seems to be happening to more and more of our users. We have a standard PC image and a fairly well controlled software management system at our company, but we're getting more and more of our users reporting problems connecting and this registry value type issue is more and more often the cause. We can't seem to find any commonality between these users besides the registry value type. I was wondering if anyone knows what could be causing this change and creating the %SystemRoot% resolution problem?

[almahdi_benabdesselam]

thank you michael for the solution, i've been blocked by this problem several days and found nothing on OSS.

Regards.

Al Mahdi BENABDESSELAM

[Former Member]

Hi,

there are some programs that change the registy type of %SystemRoot%. One example you can find here: http://support.microsoft.com/kb/317206/en-us "MMS Lotus Notes Plug-In Alters the Windows Path Environment"

So each user might have to detect himself which application has made the type-change.

Best regards

Uwe

[Former Member]

we have about 5 messages within the last 3 days concerning this issue. (REG_EXPAND_SZ has been changed to REG_SZ).

Perhabs could some find out what happened (patch installations, product installations) on these workstations.

[Former Member]

Hallo, this is my first post here.

A collegue of mine has the same problem. Yesterday she used a computer just bought (so completely new) for the first time. She could log on to SAP without any problem. Her computer has Windows XP Professional SP2, Microsoft Office 2003 and SAP GUI 6.40 without any patch and I think no more programs.

Few hours later, she installed the latest version of Microsoft Messanger and she change user name from Administrator to hers. After that, she found sapdp00' error and she can't log on to SAP.

I don't know any relationship between Messanger, user change and SAP, but this is what happen.

As the computer is so new, maybe it could be a hint for discover the reason.

However, I couldn't solve the problem: I changed the registry as described here, but she still can't log on to SAP.

Hallo,

Guido

[Former Member]

Guido,

I recommend to isolate your problem.

Try the following :

1 - Look out in services file, for the port number corresponding to the failing port name ( ie: sapxxyy )

2 - run the following command from a cmd windows :

telnet < saphost ip > < port number >

This can give 2 results :

a ) you get a connection error: meaning that SAP server is not running or, you can't reach that IP or, ...etc. Resolve this first and start over.

b ) you get a black screen ( meaning that you reach the port number 😞 SAP is listening on that port, go to step 3.

3 ) run the following :

telnet < saphost ip > < port name >

a) you get a connection error : meaning that your services file is not working. Go back to the registry.

b ) You get a black screen : problem should be solved.

[Former Member]

At least some of our users who have been struggling with service sapdp<xx> unknown or service sapms<SID> unkown errors have seen the error after running MSN Messenger 7.5 Connection TroubleShooter. It appears that the data type of HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > tcpip > Parameters > DataBasePath is changed from REG_EXPAND_SZ to REG_SZ once the MSN Messenger 7.5 Connection TroubleShooter runs. We reported the situation to Microsoft and have been using workarounds (like changing the value of that entry from %SystemRoot%\System32\drivers\etc to C:\Windows\System32\drivers\etc or deleting that registry entry altogether and recreating it with the correct data type which is REG_EXPAND_SZ.)

[Former Member]

Just replying to confirm the report: the MSN Messenger 7.5 Connection Troubleshooter contains a "Repair" button the causes the unwanted change.

[Former Member]

Great, it works!

Thank you very much!

Ciao,

Guido

[Former Member]

I have de same trouble, is the same but i have 5 machines with this problem, i need help, please ricalde12@hotmail.com

[Former Member]

SAP has created OSS Note # 882741 on this problem.

John

[Former Member]

Since there are so many posts on this I thought I'd go into more detail on our solution. We basically don't use the services file.

We code the TCP port # into the saplogon.ini file. See OSS Note # 99435 for more information. Add a section to the file like this:

[MSSrvPort]

Item1=3600

Item2=3600

Item3=3600

Item4=3620

Spell out the port # for each server entry.

I can delete all the SAP created entries in my services file and still connect to all our systems. I didn't test with a bad registry key though.

We did something similar for connecting through Portals, the port was included in the URL generated by Portals. I don't have the OSS # handy for that one though.

Regards,

John

[Former Member]

I DO, BUT IT DOESNT WORK, ERROR CODE -6

I CANT CONECT TO SAP. THANKS!

IF YOU NEED MY .INI OR ANY ARCHIVE I SEND YOU.

THANKS!!! VERACRUZ-MEXICO.

Message was edited by: Pedro Ricalde Hernandez

Message was edited by: Pedro Ricalde Hernandez

Message was edited by: Pedro Ricalde Hernandez

[Former Member]

Thank you very much!

Adeu,

David

[Former Member]

hello in Windows XP when we executed Start- Run- regedit, go to this reg node changes a: HKEY_LOCAL_MACHINE/SYSTEM/currentcontrolset/Services/Tcpip/Parameters, change DataBasePath value from %systemroot%\system32\drivers\etc to c:\windows\system32\etc

[Former Member]

Hi,

please check the type of the Registry Entry "DataBasePath". %SystemRoot% is only resolved if it is from type REG_EXPAND_SZ.

I think you have REG_SZ -> this won't work! Whenever you want to resolve environment variables in the registry you have to use a registry key of type REG_EXPAND_SZ Unfortunately i found it nowhere documented.

Best regards

Uwe

[Former Member]

Yes, administrator please give 10 points to UWE. This should be included in some sort of OSS Note. Thank you SAP and Micro$oft!

[Former Member]

We code the TCP/IP ports into the SAPLOGON.ini file. Prevents a lot of these types of problems.

Regards,

John

[Former Member]

Thanks zhao ym,

It does work now. need to change it to C:\Windows\System32\drivers\ect .

Still, there is very strange, why %SystemRoot% does not work now. I can even cd %SystemRoot% to goto the c:\windows

I met this problem just few day before, last friday. Is there any virus or something effected it?

Message was edited by: Avie Woo

[Former Member]

Start->Run->regedit,

go to this reg node:

HKEY_LOCAL_MACHINE/SYSTEM/Services/Tcpip/Parameters,

change DataBasePath value from %systemroot%\system32\drivers\etc to c:\windows\system32\etc

(your windows dir is C:\WINDOWS).

[Former Member]

Thanks Zhao ym

The solution you suggested works perfectly. I was using msn messenger 7.5

[Former Member]

Hi all

I am sorry but I hav e the same problem. I am running SAP, oracle 102 hp-ux

I have changed the port sapdp00 3200/tcp to

sapdp00 3600/tcp because I could telnet srvmap20 3600 but not able to connect srvmap20 3200.

I am sitll not able to connect via sapgui 730.

The oracle and sap are up and running

Ernesto

[Former Member]

Hi,

Correction

sapdp00 <b>3600</b>/tcp

Anand.M

[gregorw]

Hello Mark,

is the service Name sapdp00 in your services File?

Regards

Gregor

[Former Member]

Yes

sapdp00 3200/tcp

Any other thoughts?