6/6/2017 TroubleshootingSAPstartupproblemsinWindows

TroubleshootingSAPstartupproblemsinWindows

SAPSystemstartupProblems:

Twoplacesyouneedtocheck:EventViewer(ApplicationandSystemlogs)andtheSAPManagement
Console(MMC).
EventViewercanprovideusefulinformationanditmayhelpyoupinpointwheretheproblemresides.
TheSAPMMCgivesyouthe
abilitytovisuallyseethesystemstatus(green,yelloworredlights),viewtheworkprocessesstatusand
viewthedevelopertraces,
whicharestoredinthe"work"directory.Example:/usr/sap/TST/DVEBMGS00/work.
ForacentralSAPinstancetostartsuccessfully,boththemessageserverandthedispatcherneedto
start.Ifoneofthemorbothfail
tostart,userscannotlogintothesystem.Thefollowingscenarioswillillustratepossiblecausesofwhy
anSAPinstancemightnot
startandthereasonofthemessage:
"DISPATCHEREMERGENCYSHUTDOWN".
DeveloperTraces:
dev_dispDispatcherdevelopertrace
dev_msMessageServerdevelopertrace
dev_wp0Workprocess0developertrace
The"services"file,whichcontainsTCPandUDPservicesandtheirrespectiveportnumbers.Thisplain
textconfigurationfileis
locatedunderwinnt/system32/drivers/etc.
WindowsTaskManager(TASKMGR.exe),EventViewer(EVENTVWR.exe).
DispatcherMonitor(DPMON.exe),whichislocatedunder/usr/sap//sys/exe/run.Databaselogs.

1.Dispatcherdoesnotstartduetoaportconflict

Noworkprocesses(disp+work.exe)existinTaskManager.
Dispatchershowsstatus"stopped"intheSAPMMC.
Errorsfoundin"dev_disp":
LOGQ0I=>NiPBind:bind(10048:WSAEADDRINUSE:Addressalreadyinuse)[ninti.c1488]
***ERROR=>NiIBind:servicesapdp00inuse[nixxi.c3936]
***ERROR=>NiIDgBind:NiBind(rc=4)[nixxi.c3505]
***ERROR=>DpCommInit:NiDgBind[dpxxdisp.c7326]
***DP_FATAL_ERROR=>DpSapEnvInit:DpCommInit
***DISPATCHEREMERGENCYSHUTDOWN***

http://sureshchowdarysapbasiss.blogspot.in/2013/01/troubleshootingsapstartupproblemsin.html 1/5
6/6/2017 TroubleshootingSAPstartupproblemsinWindows

ProblemAnalysis
Ihighlightedthekeywordsintheerrormessagesabove:AddressalreadyinuseServicesapdp00inuse
TheTCPportnumber
assignedinthe"services"fileisbeingoccupiedbyanotherapplication.Duetotheconflict,the
dispatchershutsdown.
OutputasPDFfilehasbeenpoweredby[UniversalPostManager]pluginfromwww.ProfProjects.com|
Page1/4|
ThispagewasexportedfromSAPADMIN
Exportdate:TueNov67:04:242012/+0000GMT
Solution
Ifyourserverhasafirewallclient,disableitandattempttostarttheSAPinstanceagain.
Iftheinstancestartssuccessfullyyoucanenabletheclientfirewallbackagain.
Ifthereisnofirewallclientatall,orifdisablingitdidnotresolvetheproblem,editthe"services"fileand
checkwhatportthe
appropriate"sapdp"isusing.
Iftheinstancenumberis00,lookforsapdp00.Iftheinstancenumberis01lookforsapdp01andsoon.
Youcanusethefollowing
OScommandtohelpyouresolveportconflicts:
netstatpTCPTherearealsoutilitiesontheInternetthatcanhelpyoulistalltheTCPandUDPportsa
systemisusing.

2:Dispatcherdiesduetoadatabaseconnectionproblem

Nodatabaseconnections.
Noworkprocesses
SAPMMC>WPTableshowsallprocessesas"ended".
Errorsfoundin"dev_disp":
Csetuser'tst'failedconnectterminated
Cfailedtoestablishconn.0
M***LOGR19=>tskh_init,db_connect(DBConnect000256)[thxxhead.c1102]
Min_ThErrHandle:1
M***ERROR=>tskh_init:db_connect(step1,th_errno13,action3,level1)[thxxhead.c8437]
***ERROR=>W0(pid2460)died[dpxxdisp.c11651]
***ERROR=>W1(pid2468)died[dpxxdisp.c11651]
***ERROR=>W2(pid2476)died[dpxxdisp.c11651]...
***ERROR=>W11(pid2552)died[dpxxdisp.c11651]
***ERROR=>W12(pid2592)died[dpxxdisp.c11651]
mytypeschangedafterwpdeath/restart0xbf>0x80
***DP_FATAL_ERROR=>DpEnvCheck:nomoreworkprocesses

http://sureshchowdarysapbasiss.blogspot.in/2013/01/troubleshootingsapstartupproblemsin.html 2/5
6/6/2017 TroubleshootingSAPstartupproblemsinWindows

***DISPATCHEREMERGENCYSHUTDOWN***
DpModState:changeserverstatefromSTARTINGtoSHUTDOWN
ProblemAnalysis
AconnectiontothedatabasecouldnotbeestablishedbecauseeithertheSQLloginspecifiedin
parameter"dbs/mss/schema"isset
incorrectlyortheSQLloginwasdeletedfromthedatabaseserver.Thisparameterneedstobesetinthe
DEFAULT.pflsystem
profile(under/usr/sap//sys/profile).Inthemessagesabove,weseethattheSQLlogin'tst'isexpected
butitdoesnotexistatthe
databaselevel.
Solution
Settheentrytotheappropriatedatabaseowner.IfthesystemisbasedonBasis

3:SAPdoesnotstartatall:nomessageserverandnodispatcher

ThemessageserverandthedispatcherdonotstartatallintheSAPMMC.Thefollowingerrorwhen
tryingtoviewthedeveloper
traceswithintheSAPMMC:Thenetworkpathwasnotfound.Nonewdevelopertraceswrittentodisk
(underthe"work"directory.)
ProblemAnalysis
Thenetworkshares"saploc"and"sapmnt"donotexist.Thatexplainsthe"networkpathnotfound"
messagewhenattemptingto
viewthedevelopertraceswithintheSAPMMC.
OutputasPDFfilehasbeenpoweredby[UniversalPostManager]pluginfromwww.ProfProjects.com|
Page2/4|
ThispagewasexportedfromSAPADMIN
Exportdate:TueNov67:04:242012/+0000GMT
Solution
Recreatethe"saploc"and"sapmnt"networkshares.Bothneedtobecreatedonthe/usr/sapdirectory

4:Usersget"Nologonpossible"messages
Workprocessesstartbutnologinsarepossible.
Usersgettheloginscreenbutthesystemdoesnotlogthemin.Instead,theygetthiserror:Nologon
possible(nohwIDreceivedby
mssgserver).
IntheSAPMMC,themessageserver(msg_server.exe)showsstatus"stopped".
Thedev_msfilereportstheseerrors:
[Thr2548]***ERROR=>MsCommInit:NiBufListen(sapmsTST)(rc=NIESERV_UNKNOWN)[msxxserv.c
8163]

http://sureshchowdarysapbasiss.blogspot.in/2013/01/troubleshootingsapstartupproblemsin.html 3/5
6/6/2017 TroubleshootingSAPstartupproblemsinWindows

[Thr2548]***ERROR=>MsSInit:MsSCommInit[msxxserv.c1561]
[Thr2548]***ERROR=>main:MsSInit[msxxserv.c5023]
[Thr2548]***LOGQ02=>MsSHalt,MSStop(MsgServer2900)[msxxserv.c5078]
ProblemAnalysis
Workprocesseswereabletostartbutthemessageserverwasnot.Thereasonisbecausethe
"services"fileismissingtheSAP
SystemMessagePortentry.Example:SAPmsTST3600/tcp
Solution
Editthe"services"fileandaddtheentry.Then,restarttheinstance.Makesureyouspecifythe
appropriateTCPport(e.g.3600)for
themessageserver.

5:Themessageserverstartsbutthedispatcherdoesn't
Thedispatchershowsstatus"stopped"intheSAPMMC.
The"dev_disp"fileshowstheseerrors:
***LOGQ0A=>NiIServToNo,service_unknown(sapdp00)[nixxi.c2580]
***ERROR=>DpCommInit:NiDgBind[dpxxdisp.c7326]
***DP_FATAL_ERROR=>DpSapEnvInit:DpCommInit
***DISPATCHEREMERGENCYSHUTDOWN***
ProblemAnalysis
Thekeywordinthemessagesaboveis"serviceunknown"followedbytheentryname"sapdp00".The
dispatcherentry"sapdp00"is
missinginthe"services"file.Example:sapdp003200/tcp

Solution
Addthenecessaryentryinthe"services"file.Example:sapdp003200/tcpThen,restarttheinstance.

6:Workprocessesdiesoonaftertheystart
Allworkprocessesdierightaftertheinstanceisstarted.
TheSAPMMCshowsworkprocesseswithstatus"ended".
OutputasPDFfilehasbeenpoweredby[UniversalPostManager]pluginfromwww.ProfProjects.com|
Page3/4|
ThispagewasexportedfromSAPADMIN
Exportdate:TueNov67:04:242012/+0000GMT
Onlyoneworkprocessshowsstatus"wait".
AnABAPdumpsaying"PXA_NO_SHARED_MEMORY"isgeneratedassoonasauserlogsin.
TheSAPMMCSyslogshowsthefollowingerrormultipletimes:"SAPBasisSystem:SharedMemoryfor
PXAbuffernot
available".

http://sureshchowdarysapbasiss.blogspot.in/2013/01/troubleshootingsapstartupproblemsin.html 4/5
6/6/2017 TroubleshootingSAPstartupproblemsinWindows

ProblemAnalysis

Theinstanceprofilecontainsmisconfiguredmemoryrelatedparameters.Mostlikelythe
"abap/buffersize"instanceprofile
parameterissettohigh.

Solution
EdittheinstancesystemprofileattheOSlevelunder/usr/sap//sys/profileandlowerthevalueassigned
to"abap/buffersize".Then,
restarttheinstance.Also,it'simportanttofindoutifanyothermemoryparameterwerechanged.Ifnot,
thesystemshouldstartonce
theadequatememoryallocationhasbeensettothethe"abap/buffersize"parameter.
Output

http://sureshchowdarysapbasiss.blogspot.in/2013/01/troubleshootingsapstartupproblemsin.html 5/5