Beruflich Dokumente
Kultur Dokumente
1 of 6
http://wiki.scn.sap.com/wiki/display/SI/SAP+does+not+start
Welcome, Guest
Login
Register
1 0 17:39:33
If the sapstartsrv process doesnt exist, please consult following SAP notes and start up.
1762827 - Startup of Instance Service failed in UNIX or Linux environment
05/12/15 6:01 PM
2 of 6
http://wiki.scn.sap.com/wiki/display/SI/SAP+does+not+start
The OS command PS or the taskmanager shows the process. But the sapstartsrv doesnt respond to any actions. Then, most likey, the UNIX domain socket (/tmp/.sapstream<port-no>) or Windows
named pipe (\\<host>\pipe\sapcontro_<xx>) may be broken. If it still exists, please manually delete. And start the sapstartsrv service again.
Other cases
Case 1:
Found the following error information in the startsap.log.
exec(): 0509-036 Cannot load program disp+work because of the following
errors:
rtld: 0712-001 Symbol ixml_iXMLParser_IsNormalizingAtt was referenced
from module disp+work(), but a runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol ixml_iXMLParser_SetNormalizingAtt was referenced
from module disp+work(), but a runtime definition
Root cause:
The library path was not configured correctly after upgrade.
Solution:
Configure the library path.
SAP Note 1265456 SAP system does not start after kernel upgrade
SAP Note 1104735 Upgrade to the new instance-specific directory on UNIX
Case 2:
The sapstartsrv service is up but the dispatcher doesnt startup.
sapcontrol -nr 00 -function GetProcessList
30.11.2013 18:46:21
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
disp+work, Dispatcher, GRAY, Stopped, , , 26680
igswd_mt, IGS Watchdog, GREEN, Running, 2013 11 30 12:57:32, 5:48:49,
26681
Root cause:
The zombie process of the dispatcher existed.
Solution:
Kill the zombie process.
Case 3:
On NT, frequently failover in few minutes.
Root cause:
The version of the sapstartsrv.exe was different between DIR_CT_RUN and DIR_EXECUTABLE.
Solution:
Copy the sapstartsrv.exe from DIR_CT_RUN to DIR_EXECUTABLE.
SAP Note 1043592 MSCS: Cluster Resource Monitor Crashes on W2K3 SP2
SAP Note 1345206 Handling and preventing sapstartsrv.exe corruptions
SAP Note 1375494 SAP system does not start after applying SAP kernel patch
Case 4:
Startsap.log says:
(1159276) Starting: local /usr/sap/ABC/SYS/exe/run/igswd_mt mode=profile pf=/usr/sap/ABC/SYS/profile/ABC_DVEBMGS00_walldorf
(442404) Waiting for Child Processes to terminate.
(442404) **** 2010/04/10 08:07:11 Child 1155152 terminated with Status
255 . ****
(1155152) **** 2010/04/10 08:07:11 No RestartProgram command for
program 2 ****
The information above is very generic. stderr5 file shows more detailed information.
Command: /usr/sap/ABC/SYS/exe/run/igswd_mt
-mode=profile
pf=/usr/sap/ABC/SYS/profile/ABC_DVEBMGS00_walldorf
05/12/15 6:01 PM
3 of 6
http://wiki.scn.sap.com/wiki/display/SI/SAP+does+not+start
Root Cause
Incorrect setup of the loopback address.
Solution:
#1054467 Local host name refers to loopback address
Case 7:
The dispatcher went down right after startup. The dev_disp shows:
*** ERROR => gateway (pid 29622344) died [dpxxdisp.c 16763]
*** DP_FATAL_ERROR => Gateway died with status 2 - I better exit now
3740]
05/12/15 6:01 PM
4 of 6
http://wiki.scn.sap.com/wiki/display/SI/SAP+does+not+start
13096]
Root Cause:
The service port 3300 was declared twice in the /etc/services file.
sapgw00
3300/tcp
sapgw00s
3300/tcp
Solutoin:
Make sure only one service is available.
sapgw00
#sapgw00s
3300/tcp
3300/tcp
Case 8:
The dispatcher went down right after startup. The dev_disp shows:
sapstart.log
(11925) Starting local Command:
Command: dw.sapPIP_DVEBMGS00
pf=/usr/sap/PIP/SYS/profile/PIP_DVEBMGS00_unjspfsappip
dev_disp
*** ERROR => NiDgHdlBindName: invalid hostname 'localhost' (rc=-2;hdl 1) [nixx.c
4341]
Root Cause:
hosts file was modified and localhost was misconfigured.
Solution:
Configure localhost in the hosts file correctly.
Case 9:
The sapstartsrv is up.
When you execute sapcontrol without host opetion, you get: NIECON_REFUSED (WSAECONNREFUSED) error. However, it success with -host opetion.
For example:
sapcontrol -nr 00 -function GetVersionInfo
FAIL: NIECONN_REFUSED (WSAECONNREFUSED: Connection refused),
NiRawConnect failed in plugin_fopen()
but
sapcontrol -nr 00 -host saphost.sap.co:50013 -function GetVersionInfo -> works!
Root Cause:
Please refer SAP Note 2062508 sapcontrol commands fail with error "NIECONN_REFUSED (WSAECONNREFUSED: Connection refused)" during upgrade
Solution:
Comment out parameter service/hostname for the SAP start service and restart sapstartsrv.
The sapstartsrv exisits. -function GetProcessList doesn't show programs like dispatcher, gateway, etc.
In normal case, you will see something like this:
---sapcontrol -nr 00 -function GetProcessList
05/12/15 6:01 PM
5 of 6
http://wiki.scn.sap.com/wiki/display/SI/SAP+does+not+start
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, GREEN, Running, 2014 02 25 05:45:24, 0:00:53, 7326
disp+work, Dispatcher, GREEN, Running, Message Server connection ok, Dialog Queue time: 0.00 sec, 2014 02 25 05:45:24, 0:00:53, 7327
igswd_mt, IGS Watchdog, GREEN, Running, 2014 02 25 05:45:24, 0:00:53, 7328
---->here, you can see programs (message server, disp+work and IGS) are up and running.
But in this problematic situation, something like....
---sapcontrol -nr 00 -function GetProcessList
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
-----> No programs are listed .
This is because 'Start_Program_n' command with the program is missing in the profile file which sapstartsrv starts with.
For this 'Start_Programm_n", please refer the following link:
http://help.sap.com/saphelp_nw74/helpdata/en/9c/ac0d50a40af26be10000000a423f68/frameset.htm
(NOTE!!! since kernel 74x release, 'Start Profile' is obsolated. You cannot use 'Start Profile' like ealier release. All the information in Start Profile can be marged to Instance Profile)
05/12/15 6:01 PM
6 of 6
http://wiki.scn.sap.com/wiki/display/SI/SAP+does+not+start
A trace file called sapstartsrv_ccms.log was generated in work dir. The content of i ends with the information:
INFO: Checking lock file.....
Root Cause:
Please refer SAP note 1916333 sapcontrol error "FAIL: NIECONN_REFUSED" due to agent.log file
Solution:
set ccms/enable_agent = 0 in the instance profile.
No labels
Contact Us
Privacy
Legal Disclosure
Copyright
Follow SCN
05/12/15 6:01 PM