SAP and Windows 2008

[Former Member]

Good evening SAP Guru's. I have a question regarding an upgrade we did just last week. We were running a beta version of Windows 2008 Enterprise with our SAP System and just bought a Tech License for the Final Release.

After performing an upgrade of the OS with our licensed copy our instances have stopped running. I mean the msg_server.EXE and disp+Work.EXE fail to start (they dont start at all).

Can anyone help and point me to logs i could check or maybe a better solution to this?

Thanks in advance.

Regards,

Darren.

[Former Member · Accepted solution]

Can you pls paste the logs dev_msg and dev_disp from your work directory.

[Former Member · Accepted solution]

yes thank you very much. i will post those details and check the rest after my paper tomorrow.

thanks for the start.

Regards.

[Former Member · Accepted solution]

Ok thank you for the guidance so far. I looked at the SAP Note (Note 1040931 - SAP Kernel on Windows Vista and Windows Server 2008). Where and how would i get these patches? It seems when i go to the download area, there isnt really a fix or patch. What confuses me is that the beta version of 2008 was running the SAP system fine. Now this technet download has confused things. So I went to the SysLog area of my instance/s that are troubling me and heres what the error messages report in their order.

Instance 40 Error Messages in SysLog of SAP MMC

1. Process Type: MS, Message ID : E10, SAP-Basis System: Buffer SCSA Generated with Length 4096

2. Process Type: MS, Message ID : Q01, SAP-Basis System: Start Msg Server, 1 times since system startup. PID 4932

3. Process Type: MS, Message ID : Q01, SAP-Basis System: Operating system call getservbyname_ failed (error no. 0 )

4. Process Type: MS, Message ID : Q02, SAP-Basis System: Stop Msg Server, PID 4932

5. Process Type: DP, Message ID : E10, SAP-Basis System: Buffer SCSA Generated with Length 4096

6. Process Type: DP, Message ID : Q00, SAP-Basis System: Start SAP System, SAPSYSTEM 40, Dispatcher Pid 1640

7. Process Type: DP, Message ID : GZZ, AP-Basis System: > 3 possible network problems detected - check tracefile and adjus

8. Process Type: DP, Message ID : Q0E, SAP-Basis System: Signal c00 received by operating system

I did not find the dev_disp and dev_msg logs in /wrk. But will double check on this. I really hope this is a simple fix. This is my test machine as well and I hope you nice people can help us solve this. Please do let me know.

Regards.

[Former Member · Accepted solution]

The error that you are receiving, 'call getservbyname_ failed', is a pretty generic message. I presume that this is a single system and not clustered?

The dev_disp and dev_msg files are located in the usr\sap\<sid>\<instance>\work\ directory of the sap installation folder.

[markus_doehr2 · Accepted solution]

Ok thank you for the guidance so far. I looked at the SAP Note (Note 1040931 - SAP Kernel on Windows Vista and Windows Server 2008). Where and how would i get these patches? It seems when i go to the download area, there isnt really a fix or patch.

http://service.sap.com/patches

What confuses me is that the beta version of 2008 was running the SAP system fine. Now this technet download has confused things. So I went to the SysLog area of my instance/s that are troubling me and heres what the error messages report in their order.

Yes - that´s why the software is called "beta" - it´s not a finished product and may change till the final version.

8. Process Type: DP, Message ID : Q0E, SAP-Basis System: Signal c00 received by operating system

signal c00 is a segmentation fault most likely caused by the software being incompatible to Windows 2008.

I did not find the dev_disp and dev_msg logs in /wrk. But will double check on this. I really hope this is a simple fix. This is my test machine as well and I hope you nice people can help us solve this. Please do let me know.

What exact software are you running? ERP? Netweaver?

Markus

[Former Member · Accepted solution]

Okay so here is my dev_ms file and dev_disp file from 1 of my instances. They come up with the same problem. To answer your question Jared, yes it is a single system, and to answer Markus, its running both ERP and Netweaver.

Markus, my reason for asking about 2008 is that how come the beta version was first used and the system ran. Now after doing the upgrade the system fails. No other additional things were done to it to make the beta version run SAP.

-

---

trc file: "dev_ms", trc level: 1, release: "700"

-

---

[Thr 4420] Mon May 12 03:04:25 2008

[Thr 4420] MsSSetTrcLog: trc logging active, max size = 20971520 bytes

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 110

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 4504

[Thr 4420] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 4504) [msxxserv.c 1824]

[Thr 4420] ***LOG Q0I=> NiPGetServByName2: service 'sapmsZUL' not found: getservbyname_r [ninti.c 530]

[Thr 4420] *** ERROR => MsSCommInit: NiBufListen(sapmsZUL) (rc=NIESERV_UNKNOWN) [msxxserv.c 10114]

[Thr 4420] *** ERROR => MsSInit: MsSCommInit [msxxserv.c 1857]

[Thr 4420] *** ERROR => main: MsSInit [msxxserv.c 5886]

[Thr 4420] ***LOG Q02=> MsSHalt, MSStop (Msg Server 4504) [msxxserv.c 5934]

_______________________________________________________________________________________________________________________________________________________________________________________________________________

-

---

trc file: "dev_disp", trc level: 1, release: "700"

-

---

sysno 12

sid ZUL

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 114

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 4468

Mon May 12 03:04:25 2008

kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)

length of sys_adm_ext is 576 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (12 4468) [dpxxdisp.c 1239]

shared lib "dw_xml.dll" version 114 successfully loaded

shared lib "dw_xtc.dll" version 114 successfully loaded

shared lib "dw_stl.dll" version 114 successfully loaded

shared lib "dw_gui.dll" version 114 successfully loaded

shared lib "dw_mdm.dll" version 114 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3912

• WARNING => DpNetCheck: NiServToNo(sapdp12) failed (rc=-3)

• ERROR => DpNetCheck: NiServToNo(sapgw12) failed (rc=-3) [dpxxtool2.c 5223]

Mon May 12 03:04:30 2008

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

***LOG GZZ=> 3 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5361]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >mars2_ZUL_12 <

DpShMCreate: sizeof(wp_adm) 31088 (1480)

DpShMCreate: sizeof(tm_adm) 5584592 (27784)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

DpShMCreate: sizeof(comm_adm) 552080 (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1864)

DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DE50050, size: 6286976)

DpShMCreate: allocated sys_adm at 000000000DE50050

DpShMCreate: allocated wp_adm at 000000000DE52150

DpShMCreate: allocated tm_adm_list at 000000000DE59AC0

DpShMCreate: allocated tm_adm at 000000000DE59B20

DpShMCreate: allocated wp_ca_adm at 000000000E3AD1F0

DpShMCreate: allocated appc_ca_adm at 000000000E3B2FB0

DpShMCreate: allocated comm_adm at 000000000E3B4EF0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000E43BB80

DpShMCreate: allocated gw_adm at 000000000E43BC00

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000E43BC30

DpShMCreate: allocated wall_adm at 000000000E43BC40

MBUF state OFF

DpCommInitTable: init table for 500 entries

• ERROR => DpIPCInit2: NiServToNo failed ((null)--3) [dpxxtool2.c 511]

• DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

• DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Mon May 12 03:04:40 2008

NiISelect: TIMEOUT occured (10000ms)

dump system status

Workprocess Table (long) Mon May 12 08:04:40 2008

========================

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table

-

---

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

0 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

1 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

2 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

3 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

4 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

5 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

6 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

7 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

8 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

9 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

10 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

11 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

12 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

13 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

14 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

15 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

16 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

17 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

18 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

19 ? -1 Free no 0 0 0

• ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c 785]

20 ? -1 Free no 0 0 0

Dispatcher Queue Statistics Mon May 12 08:04:40 2008

===========================

--------

---

+

---

+

---

+

---

+--

---

+

Typ

now

high

max

writes

reads

--------

---

+

---

+

---

+

---

+--

---

+

• ERROR => DpMQueueInfo: DpQueueInfo [dpxxtool.c 1870]

Dump of tm_adm structure: Mon May 12 08:04:40 2008

=========================

Term uid man user term lastop mod wp ta a/i (modes)

call semaphore clean-up function ...

SemCleanup: Reset blocking on semaphore (Key:4/Slot:3)

***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c 432]

-

---

C-STACK -

---

SAP (R) - R/3(TM) Callstack, Version 1.0

Copyright (C) SAP AG. All rights reserved.

-

---

Application exception occurred:

Exception : c0000005 (Access Violation)

App : disp+work.EXE (pid=4468)

When : 5/12/2008 3:4:41.114

Threads : 2

-

---

Computer Name : XXX

User Name : SAPServiceZUL

-

---

Number of Processors: 8

Processor Type: Intel64 Family 6 Model 23 Stepping 6

Windows Version : 6.0 Current Build: 6001

-

---

State Dump for Thread Id 7e0

--> (FAULT) Stack Back Trace <--

FramePtr ReturnAd Param#1 Function Name

0000000007b2f2c0 000000000045149a 0020002000200020 disp+work!DpWpBlksInQueue [dpxxqueu.c (1141)]

0000000007b2f3b0 000000000041cbe6 0000000000000015 disp+work!DpTrcWpCaInfo [dpxxtool.c (1944)]

0000000007b2fbf0 000000000042160b 0000000002574e70 disp+work!DpFatalErr [dpxxdisp.c (17696)]

0000000007b2fe90 000000000042d150 ffffffff00000006 disp+work!DpSapEnvInit [dpxxdisp.c (1388)]

0000000007b2fec0 0000000000401087 ffffffff00000002 disp+work!DpMain [dpxxdisp.c (1076)]

0000000007b2fef0 0000000001929621 0000000000000000 disp+work!nlsui_main [thxxanf.c (82)]

0000000007b2ff50 000000007741495d 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]

0000000007b2ff80 0000000077618791 0000000000000000 kernel32!BaseThreadInitThunk

0000000007b2ffd0 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart

-

---

State Dump for Thread Id 11e0

--> Stack Back Trace <--

FramePtr ReturnAd Param#1 Function Name

000000000de4fdf0 00000000773fb930 00000000000011e0 ntdll!NtFsControlFile

000000000de4fe60 000000000181cb3f fffffffffffffffe kernel32!ConnectNamedPipe

000000000de4fef0 000007feff13356b 000000000847fa90 disp+work!SigIMsgFunc [signt.c (611)]

000000000de4ff20 000007feff136cc1 000007feff1be740 msvcrt!free_dbg

000000000de4ff50 000000007741495d 0000000000000000 msvcrt!beginthreadex

000000000de4ff80 0000000077618791 0000000000000000 kernel32!BaseThreadInitThunk

000000000de4ffd0 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart

-

---

-

---

Mon May 12 03:04:41 2008

call clean-up function ...

SigICallExitRoutine: call exithandler (DpHalt)

DpHalt: shutdown server >XXX_ZUL_12 < (normal)

DpJ2eeDisableRestart

Switch off Shared memory profiling

ShmProtect( 57, 3 )

ShmProtect(SHM_PROFILE, SHM_PROT_RW

ShmProtect( 57, 1 )

ShmProtect(SHM_PROFILE, SHM_PROT_RD

DpWakeUpWps: wake up all wp's

_____________________________________________________________________________________________________________________________________________________

Really hoping that this can be resolved, without doing drastic things. I looked in the patches area, unfortunately there arent any resolves for this 2008 OS. So going to start digging more here and on Google. hope u guys can help. And thanks so much, so far.

[Former Member · Accepted solution]

The problem with the upgrade from beta Windows Server 2008 to released Windows Server 2008 is, that it is not really an upgrade. It overwrites some files (one of it is %windir%\system32\drivers\etc\services) where the sap installation is creating some lines.

I do not completely remember the details, but system environment variables may also be lost during the upgrade.

therefore it is better to perform a fresh install and not upgrade the existing windows server 2008 to the released version.

regards

Peter

[markus_doehr2 · Accepted solution]

> Markus, my reason for asking about 2008 is that how come the beta version was first used and the system ran. Now after doing the upgrade the system fails. No other additional things were done to it to make the beta version run SAP.

Because a "beta software" is work-in-progress. Apparently something was changed that prevents the instance from starting.

> relno 7000

> patchlevel 0

> patchno 114

> intno 20050900

> make: multithreaded, Unicode, 64 bit, optimized

> pid 4468

You are running patchlevel 114, I suggest you upgrade your kernel to the latest one (use SAPEXE + SAPEXEDB from 146 and then patch up to patchlevel 157.

> --> (FAULT) Stack Back Trace <--

> FramePtr ReturnAd Param#1 Function Name

> 0000000007b2f2c0 000000000045149a 0020002000200020 disp+work!DpWpBlksInQueue [dpxxqueu.c (1141)]

> 0000000007b2f3b0 000000000041cbe6 0000000000000015 disp+work!DpTrcWpCaInfo [dpxxtool.c (1944)]

> 0000000007b2fbf0 000000000042160b 0000000002574e70 disp+work!DpFatalErr [dpxxdisp.c (17696)]

> 0000000007b2fe90 000000000042d150 ffffffff00000006 disp+work!DpSapEnvInit [dpxxdisp.c (1388)]

> 0000000007b2fec0 0000000000401087 ffffffff00000002 disp+work!DpMain [dpxxdisp.c (1076)]

> 0000000007b2fef0 0000000001929621 0000000000000000 disp+work!nlsui_main [thxxanf.c (82)]

> 0000000007b2ff50 000000007741495d 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]

> 0000000007b2ff80 0000000077618791 0000000000000000 kernel32!BaseThreadInitThunk

> 0000000007b2ffd0 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart

It seems, that the main startup is failing due to some incompatibilities. I again suggest you upgrade your kernel.

> Really hoping that this can be resolved, without doing drastic things. I looked in the patches area, unfortunately there arent any resolves for this 2008 OS.

Yes - because the OS is not yet released

> So going to start digging more here and on Google. hope u guys can help. And thanks so much, so far.

I doubt that you will find something usefull The problem is the SAP kernel, it is programmed to run on Windows 2003 (and built on that platform) and some modifications had to be done to make it work under Windows 2008.

Markus

[Former Member]

well, an update from beta Windows Server 2008 to the final version isn't really an update.

I have recognized that same parts are deleted or exchanged to original version files (example %windir%\system32\drivers\etc\services, firewall configuration).

so you have at least to edit the services file and provide all the sap specific entries which are typically in there (see a different computers services file where an SAP system is installed on and running.

regards

peter

[Former Member]

Hi All...any resolve on this?

EXACTLY same promblem!

Tony.

[markus_doehr2]

Are you running at least kernel patch 114?

Markus

[Former Member]

Hey guys a big thanks out there for your input, seems the problem has been resolved, and it was to do with the services file in system32/drivers/etc -> From what you guys told me that all the services for the SAP System had been kept but in backup services files. All it meant was re-inserting them back into the newly created 1.

I would like to know more about patching a system though. When, where and how it is done.

Thanks so much again.

Regards,

Darren.

[markus_doehr2]

For patching check

http://service.sap.com/patches

--> SAP Support Packages in Detail

There you will get an overview about the different patches (Kernel/binary, ABAP, Java) and further references to notes.

Markus

[markus_doehr2]

Windows 2008 is schedule for Q3 of this year (check http://service.sap.com/nw2004s --> Availibility)

To solve your problem:

Check note 1040931 - SAP Kernel on Windows Vista and Windows Server 2008

Markus