SAP Solution Manager 7.1 Support Release 1 disp+work Fail to start.

[Former Member]

Hi

I am installing solman 7.1 SR1, and in the 26th step Start Instance it gives following error -

An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > MaxDB > Central System > Central System( Last error reported by the step: ABAP processes of instance XXX/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.). You can now: 

 Choose Retry to repeat the current step. 
 Choose Log Files to get more information about the error. 
 Stop the option and continue with it later. 

 Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/ADA/CENTRAL/AS.     

While investigating through logs I found below mentioned details -

From sapstartsrv -

WIN-Q8BOMFF2BOJ\Administrator is starting SAP System at 2014/02/04  8:20:04
SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 213]
SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 920]

From dev_ms -

---------------------------------------------------
trc file: "dev_ms", trc level: 1, release: "720"
---------------------------------------------------


[Thr 5060] Tue Feb 04 08:20:04 2014
[Thr 5060] ms/http_max_clients = 500 -> 500
[Thr 5060] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    101
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
pid        968


[Thr 5060] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 968) [msxxserv.c   2278]
[Thr 5060] load acl file = D:\usr\sap\XXX\SYS\global\ms_acl_info.DAT
[Thr 5060] MsGetOwnIpAddr: my host addresses are :
[Thr 5060]   1 : [10.203.136.14] WIN-Q8BOMFF2BOJ.ec2.internal (HOSTNAME)
[Thr 5060]   2 : [127.0.0.1] WIN-Q8BOMFF2BOJ (LOCALHOST)
[Thr 5060] MsHttpInit: full qualified hostname = WIN-Q8BOMFF2BOJ
[Thr 5060] HTTP logging is switch off
[Thr 5060] set HTTP state to LISTEN
[Thr 5060] *** HTTP port 8101 state LISTEN ***
[Thr 5060] *** I listen to internal port 3901 (3901) ***
[Thr 5060] *** HTTP port 8101 state LISTEN ***
[Thr 5060] CUSTOMER KEY: >B1166352916<
[Thr 5060] build version=720.2011.10.26

From SAPinst -

name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server.EXE, MessageServer, GREEN, Running, 2014 02 04 08:47:07, 0:10:09, 2464
disp+work.EXE, Dispatcher, GRAY, Stopped, 2014 02 04 08:47:07, 0:00:06, -1
igswd.EXE, IGS Watchdog, GREEN, Running, 2014 02 04 08:47:07, 0:10:09, 4212


ERROR 2014-02-04 08:57:16.966
CJS-30149  ABAP processes of instance SM1/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.


ERROR 2014-02-04 08:57:17.153
FCO-00011  The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_CI_Instance_Start|ind|ind|ind|ind|start|0|start was executed with status ERROR ( Last error reported by the step: ABAP processes of instance XXX/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.).


INFO 2014-02-04 08:57:17.543
Creating file C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\ADA\CENTRAL\AS\__instana_tmp.xml.

I fail to understand the reason for disp+work.exe to stop, need your suggestions/pointers to proceed ahead.

Thanks & Regards

Jeetendra

[rokinglj]

I got the same error.Did you solve?

[Former Member]

Have you increased your swap memory?

Recommended value is 20 gb, yo can try with 35 gb if this doesn't work

Increase it and re try the step

[DirkM]

Hello Juan Carlos,

great advice. I raised the memory and it worked fine.

Thanks for sharing,

Dirk

[Former Member]

Hello!

I face absolutely the same issue. Did you solve it?

[manish_kumar8]

Hi Jeetendra,

Could you please run a sappfpar check for the profiles in /sapmnt/<SID>/profiles directory :

sappfpar check pf=<Instance profile name>

Check if you are getting any errors in this check. In case of shared memory errors, check for the pool utilization and fix it by taking a key out of the pool.

Once you fix it, try starting the system manually.

Regards,

Manish

[do_thikimdung]

Hi All

I am installing solman 7.1 SR1, and in the step 21 Start Instance it gives following error -

i hope you help me

Tks all

Best rgds

[Former Member]

Hi Thi,

In your case might be oracle server is shut down. Start the oracle server and re-run the process.

Regards

Mohammed

[Former Member]

Hi,

Try to start the system manually and post dev_w0 and dev_disp errors.

Regards,

Nick Loy

[Former Member]

Hi Nick,

Thanks for the response, I searched in other threads before posting the question and I was not able to locate the dev_disp logs, can you please point me to which directory i should look for these logs. I tried to start server manually from Sap MMC and every time it start message server and other starts properly but disp+work fails to start and gets into gray state.

Thanks

Jeetendra

[Former Member]

Check /usr/sap/SID/D*/work for dev_disp and dev_w0 logs.

Regards,

Nick Loy

[Former Member]

Right-click on disp+work process in SAP MMC and select Developer Trace. Upload it with message as file attachment.

[Former Member]

Hi Roman,

I tried to do that as very first analysis but strangely the Developer Trace is not opening at all. So no luck with developer trace.

Thanks

Jeetendra

[Former Member]

Hi Nick,

In the work directory the dev_disp and dev_w0 logs are not available. The only log is dev_ms which I have already posted.

Thanks

Jeetendra

[Former Member]

Please check or upload sapstart.log from work directory.

[Former Member]

Hi Roman,

I found these two sapstart.log from work directories -

SAP-R/3-Startup Program

Starting at 2014/02/04 10:50:40
Startup Profile: "\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\START_SCS01_WIN-Q8BOMFF2BOJ"
Starting Programs
(3256) Execute: D:\usr\sap\SM1\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_SCS01_WIN-Q8BOMFF2BOJ list:D:\usr\sap\SM1\SYS\exe\uc\NTAMD64/scs.lst
(3552) CreateProcess: D:\usr\sap\SM1\SCS01\exe\msg_server.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_SCS01_WIN-Q8BOMFF2BOJ
(3468) CreateProcess: D:\usr\sap\SM1\SCS01\exe\enserver.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_SCS01_WIN-Q8BOMFF2BOJ
(2032) Parent Shutdown at 2014/02/04 15:56:39
(2032) Cannot terminate child processes.

SAP-R/3-Startup Program

Starting at 2014/02/04 15:18:48
Startup Profile: "\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\START_DVEBMGS00_WIN-Q8BOMFF2BOJ"
Starting Programs
(3876) Execute: D:\usr\sap\SM1\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WIN-Q8BOMFF2BOJ list:D:\usr\sap\SM1\SYS\exe\jvm\NTAMD64\sapjvm_4.1.016/sapjvm_4.lst source:D:\usr\sap\SM1\SYS\exe\jvm\NTAMD64\sapjvm_4.1.016
(3288) Execute: D:\usr\sap\SM1\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WIN-Q8BOMFF2BOJ
(3892) Execute: D:\usr\sap\SM1\SYS\exe\uc\NTAMD64\strdbs.cmd SM1
(468) CreateProcess: D:\usr\sap\SM1\DVEBMGS00\exe\msg_server.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WIN-Q8BOMFF2BOJ
(4088) CreateProcess: D:\usr\sap\SM1\DVEBMGS00\exe\disp+work.EXE pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WIN-Q8BOMFF2BOJ
(2444) CreateProcess: D:\usr\sap\SM1\DVEBMGS00\exe\igswd.EXE -mode=profile pf=\\WIN-Q8BOMFF2BOJ\sapmnt\SM1\SYS\profile\SM1_DVEBMGS00_WIN-Q8BOMFF2BOJ
(2024) Parent Shutdown at 2014/02/04 15:50:30
(1968) Parent Shutdown at 2014/02/04 15:56:39
(1968) Cannot terminate child processes.

Waiting for your suggestions.

Thanks

Jeetendra

[former_member4224]

You should be able to see the dispatcher and work process traces in

D:\usr\sap\SM1\DVEBMGS00\work

Attach the dev_disp and dev_w0

Regards

Clebio

[Former Member]

Hello,

Please check the permission of the files in the kernel and see whether it works.

BR

Bakhtiyar Jaikbayev

[Former Member]

Hi Bakhtiyar,

Thanks for the response, where should i look for the kernel files to check the permissions? I mean which directory?

Thanks

Jeetendra

[Former Member]

cd /sapmnt/<SID>/exe

owner: sidadm

grp: sapsys

perm: 775

Note: brarchive, brbackup, brcheck is orasid owner.

BR

Bakhtiyar Jaikbayev

[Former Member]

Hi Bakhtiyar,

I checked the permission and it looks perfectly fine but the problem is still same dispatcher failed to start message server and watchdog are started.

Thanks

Jeetendra