cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start NSP database after XP system restore

former_member210563
Participant
0 Kudos

Hello,

I had some problems with the network today and decided to do a system restore of XP. Later, I have tried to start the database for use. It stops the starting process at yellow light and these messages are logged:

SAP-Basis System: Signal c00 received by operating system

SAP-Basis System: > 3 possible network problems detected

- check tracefile and adjus

SAP-Basis System: Operating system call

getservbyname_ failed (error no. 0 )

If anyone has an idea of a solution to this, it would much appreciated.

/Peter

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

we have two instances in one server(SM1 & NSP). i uninstall NSP successfully. but after that SM1 intance not up.

error as follows

SAP-Basis System: Signal c00 received by operating system

SAP-Basis System: > 3 possible network problems detected

- check tracefile and adjus

Former Member
0 Kudos

Check the instance profile and parameter PHYS_MEMSIZE, and down the value

Former Member
0 Kudos

Hallo Peter,

a bit late, but for reference I still post the solution :

include a sapmsNSP 3600/tcp in your services file (See note 39227 below)

Regards

Jan

getservbyname error

SAP Note Number: 39227

Symptom

Entries in system log or trace files

OS call getservbyname failed

services sapmsYYY not found.(or unknown)

Additional key words

sapms<SID> /etc/services getservbyname NIESERV_UNKNOWN (NI -3)

Cause and prerequisites

TCP/IP configuration: services not defined in /etc/services on UNIX resp. %windir%/system32/drivers/etc/services on NT.

Solution

Include the following entry in the /etc/services

sapmsYYY

36xx/tcp

where xx = 2 digits, e.g. 00 (independent from system/instance no.)

YYY = SAPSYSTEMNAME (in capital letters!)

Important:

  • service names (TCP/IP) are case sensitive.

  • sapms<SID> must have an unique value (e.g. 3600/tcp) for all related R/3 instances (the message server is the "network dictionary" for one single R/3 system).

  • all changes to the TCP/IP configuration will be noticed by R/3 only after process restart (see note 25917).

former_member229109
Active Contributor
0 Kudos

Hello Peter,

Why do you think it's database error? What version of the database do you have on your system?

From the information, you provided, you had network problems...

->Please run the connection tests in /nSTMS transaction first.

->Please check the errors in the log files in /nst11 ( dev_rfc* & dev_rd).

->Check errors in the system logs & corresponding dev log of the WP ( what was exactly in the trace).

-> Did you change the 'services' entries?

If you've got access to OSS/Service Market Place, then please take a look at notes 712594 & 52959.

Are you are the official SAP customer?

Thank you and best regards, Natalia Khlopina