Dispatcher - Running but Dialog Queue info unavailable

[former_member912992]

Dear all,

I just upgraded a kernel patch for an SAP ECC 5 on Windows x64 - MSSQL, from patch level 155 to 175. SAP system is able to run and looks fine. But, on SAPMMC the dispatcher remains yellow. Status 'Running but Dialog Queue info unavailable'. I found notes 722248 and 396309, but they didn't help.

There is no suspicious logs on both SAP, neither OS. Users are still able to logon and work as usual.

Additional info. On SAPMMC, WP Table is empty.

Please help.

Regards,

Agoes

Message was edited by:

Agoes Boedi Poerwanto

[Former Member]

81> sapcar -tvf dw_186.sar

SAPCAR: processing archive dw_186.sar (version 2.01)

-rwx------ 36744240 05 Jun 2007 06:27 disp+work.exe

-rw------- 29903872 04 Jun 2007 21:19 disp+work.pdb

-rwx------ 1763376 05 Jun 2007 06:27 dpj2ee.exe

-rw------- 1502208 04 Jun 2007 21:29 dpj2ee.pdb

-rwx------ 1383984 05 Jun 2007 06:27 dpmon.exe

-rw------- 1313792 04 Jun 2007 21:29 dpmon.pdb

-rw------- 7126064 05 Jun 2007 06:28 dw_gui.dll

-rw------- 15150080 04 Jun 2007 21:05 dw_gui.pdb

-rw------- 256048 05 Jun 2007 06:28 dw_mdm.dll

-rw------- 355328 04 Jun 2007 21:11 dw_mdm.pdb

-rw------- 1101872 05 Jun 2007 06:28 dw_stl.dll

-rw------- 2739200 04 Jun 2007 20:16 dw_stl.pdb

-rw------- 2132528 05 Jun 2007 06:28 dw_xml.dll

-rw------- 5090304 04 Jun 2007 20:21 dw_xml.pdb

-rw------- 2822704 05 Jun 2007 06:28 dw_xtc.dll

-rw------- 6319104 04 Jun 2007 20:29 dw_xtc.pdb

-rwx------ 1963056 05 Jun 2007 06:27 enqt.exe

-rw------- 1256448 04 Jun 2007 22:03 enqt.pdb

-rw------- 621363 05 Jun 2007 06:28 FRFCLIB64.SAR

-rwx------ 955952 05 Jun 2007 06:27 gwmon.exe

-rw------- 863232 04 Jun 2007 21:26 gwmon.pdb

-rwx------ 3200560 05 Jun 2007 06:28 gwrd.exe

-rw------- 2034688 04 Jun 2007 21:26 gwrd.pdb

-rw------- 121199 05 Jun 2007 06:28 icmadmin.SAR

-rwx------ 3651120 05 Jun 2007 06:28 icman.exe

-rw------- 2927616 04 Jun 2007 21:30 icman.pdb

-rwx------ 1000496 05 Jun 2007 06:28 icmbnd.exe

-rwx------ 1480752 05 Jun 2007 06:28 icmon.exe

-rw------- 1532 04 Jun 2007 22:52 instance.lst

-rwx------ 4271152 05 Jun 2007 06:28 msg_server.exe

-rw------- 2378752 04 Jun 2007 21:34 msg_server.pdb

-rw------- 6254 04 Jun 2007 19:11 rspo0lib.lib

-rwx------ 222256 05 Jun 2007 06:28 sappfpar.exe

-rw------- 314368 04 Jun 2007 21:49 sappfpar.pdb

-rwx------ 5438512 05 Jun 2007 06:28 sapstartsrv.exe

-rw------- 5438512 05 Jun 2007 06:28 sapstartsrv.exe.new

-rw------- 4934656 04 Jun 2007 22:13 sapstartsrv.pdb

-rwx------ 2955824 05 Jun 2007 06:28 sapwebdisp.exe

I assume that you didn't stop the SAP Service when extracting dw_186.sar directly in to the sys\exe\run directory.

Executables of running processes cant be extracted from sapcar.

Stop sap System.

Stop all SAP Services

Close all SAPMMCs (as they will automatically restart the SAP Services).

unpack the archive again.

regards

Peter

[former_member433984]

is sapstartsrv.exe the same date as disp+work.exe?

[former_member912992]

Hi Yaroslav,

No. The new kernel patch doesn't have sapstartsrv.exe. I couldn't find the single patch, either. But there is one in DW_186 patch.

During the transition, I also stopped sapstartsrv.exe and saposcol.exe. Even restart the whole server. Nothing helped.

Regards,

Agoes

Message was edited by:

Agoes Boedi Poerwanto

[former_member433984]

Hi Agoes,

it cannot be. sapstartsrv.exe always comes with disp+work.exe patches in dw_.sar. Could you please check it?

Best regards,

Yaroslav

[Former Member]

Hi,

Assuming ur using 64bit unicode kernel

<a href="https://websmp208.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=LIST&HEADER=&FUNCTIONBAR=&EVENT=LIST&ONR=01200314690200004052&NTYPE=T_CV_DELO&V=MAINT&TA=ACTUAL&U=S0003454968&AI=SWTYPSC|&AI=PECCLSC|PLTFRM&AI=PECU_OS|NT_X64&AI=PECU_DB|DBINDEP&AI=">Chk here</a>

SAP KERNEL 6.40 64-BIT UNICODE -> #Database independent -> Windows Server on x64 64bit

Regrds, Umesh K

[former_member433984]

sapcar -tvf dw_186-20001181.sar

SAPCAR: processing archive dw_186-20001181.sar (version 2.01)

-rwx------ 42913840 05 Jun 2007 06:25 disp+work.exe

-rw------- 29977600 04 Jun 2007 23:07 disp+work.pdb

-rwx------ 2589744 05 Jun 2007 06:25 dpj2ee.exe

-rw------- 1633280 04 Jun 2007 23:12 dpj2ee.pdb

-rwx------ 2026032 05 Jun 2007 06:25 dpmon.exe

-rw------- 1461248 04 Jun 2007 23:12 dpmon.pdb

-rw------- 8430640 05 Jun 2007 06:25 dw_gui.dll

-rw------- 15272960 04 Jun 2007 22:57 dw_gui.pdb

-rw------- 359984 05 Jun 2007 06:25 dw_mdm.dll

-rw------- 371712 04 Jun 2007 23:00 dw_mdm.pdb

-rw------- 1196592 05 Jun 2007 06:26 dw_stl.dll

-rw------- 2739200 04 Jun 2007 20:27 dw_stl.pdb

-rw------- 2230320 05 Jun 2007 06:26 dw_xml.dll

-rw------- 5098496 04 Jun 2007 20:33 dw_xml.pdb

-rw------- 2923056 05 Jun 2007 06:26 dw_xtc.dll

-rw------- 6327296 04 Jun 2007 20:40 dw_xtc.pdb

-rwx------ 2855472 05 Jun 2007 06:25 enqt.exe

-rw------- 1420288 04 Jun 2007 23:29 enqt.pdb

-rw------- 704555 05 Jun 2007 06:26 FRFCLIB64.SAR

-rwx------ 1434160 05 Jun 2007 06:25 gwmon.exe

-rw------- 994304 04 Jun 2007 23:11 gwmon.pdb

-rwx------ 4473904 05 Jun 2007 06:25 gwrd.exe

-rw------- 2165760 04 Jun 2007 23:11 gwrd.pdb

-rw------- 121199 05 Jun 2007 06:26 icmadmin.SAR

-rwx------ 4844592 05 Jun 2007 06:25 icman.exe

-rw------- 3058688 04 Jun 2007 23:13 icman.pdb

-rwx------ 1000496 05 Jun 2007 06:25 icmbnd.exe

-rwx------ 2143792 05 Jun 2007 06:25 icmon.exe

-rw------- 1569 05 Jun 2007 00:40 instance.lst

-rw------- 112688 05 Jun 2007 06:26 libsapu16vc71.dll

-rwx------ 2957360 05 Jun 2007 06:25 msg_server.exe

-rw------- 2026496 04 Jun 2007 23:16 msg_server.pdb

-rw------- 6574 04 Jun 2007 19:21 rspo0lib.lib

-rwx------ 382000 05 Jun 2007 06:25 sappfpar.exe

-rw------- 429056 04 Jun 2007 23:28 sappfpar.pdb

-rwx------ 4466224 05 Jun 2007 06:25 sapstartsrv.exe

-rw------- 4466224 05 Jun 2007 06:26 sapstartsrv.exe.new

-rw------- 4557824 04 Jun 2007 23:36 sapstartsrv.pdb

-rwx------ 3816496 05 Jun 2007 06:25 sapwebdisp.exe

[former_member912992]

Hi all,

Finally I found the root cause. The problem was the .CAR files wasn't fully uncared, because I put SAPCAR in the same folder as the .CAR file. When it tried to uncar SAPCAR, it stopped and didn't continue with the rests.

Moving SAPCAR to another folder helped. Now I have a complete uncared kernel. This problem only happens on Windows platform, since I never found it before on others.

Thanks to Yaroslav for giving me an idea.

Best Regards

Agoes

[Former Member]

Hi,

Use sapcar -xvf abcd.sar -R .\run_new

this will extract the abcd.car to a new directorey called run_new in same root

Regards

Umesh K

[Former Member]

because they may contain executables or DLLs registered as Type-Library or Com-Object in the Windows registry.

depending on the tool your are using to rename the directory these objects in the registry are automatically changed or not.

the right way to do backups is to save the contents of the run directory to a different directory and unpack the archives into the run directory.

watch the output of sapcar.exe!

you are not able to replace files which are currently in use.

therefore you have to stop all services and programs running executables from within the target directory.

sapstartsrv.exe and sapcar.exe are typical candidates (because sapcar.exe may not overwrite itself and sapstartsrv.exe (executable of SAPSID_XX Windows Service) is automatically started when you have SAPMMC still running.

peter

[Former Member]

Hi,

Change the disp+work.exe and check

Regards

Umesh K

[former_member912992]

Hi Umesh,

Thanks for the reply.

It is already the new disp+work.exe from patch 175.

Or may be I misunderstood?

Regards,

Agoes

Message was edited by:

Agoes Boedi Poerwanto

[Former Member]

Hi,

Upgrade to this

SAR dw_186-20001181.sar d isp+work package 186 Info 54167 05.06.2007

also update the r3trans (patch 177), tp (patch 177) and

Regards

Umesh K