Can't start Mini SAP: error "MSG_SERVER died"

[former_member185943]

Hello!

I have succesfully installed Mini SAP version 4.6D. When I try to start it, I get error messages "MSG_SERVER died" and later "DISPATCHER died". I can't figure out what could be wrong. Please help!

Below is a detailed command-prompt and SLOG00 file content. Although the content of the SLOG00 file is to me completely unreadable, maybe it means something to someone. Or, is there any log viewer for this?

Thanks in advance for all inputs!

Kind regards,

Igor Barbaric

COMMAND-PROMPT ECHO:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

C:\MBS>runmbs

C:\MBS>set DBMS_TYPE=mss

C:\MBS>set DIR_LIBRARY=.

C:\MBS>set MSSQL_DBNAME=MBS

C:\MBS>rem del pxastat

C:\MBS>start /B msg_server.exe pf=MBS_D00.pfl

C:\MBS>disp+work.exe break pf=MBS_D00.pfl

dp Ctrl-C enabled

rslgwr1(21): Searching for overlap point in pre-existing SysLog file...

***

• MSG_SERVER died => main: MsSInit

Thu Feb 10 13:37:23 2005

SemSpinning: 2200 usec for 27339 loops -> 12 loops per usec

rslgwr1(21): Searching for overlap point in pre-existing SysLog file...

***

• DISPATCHER died => DpSapEnvInit: DpCommInit

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SLOG00 content:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

aE002005021013372300 2140 0MS 0 046D 20.1--

---

180--

---

iE102005021013372300 2140 0MS 0SCSA 4096 mQ012005021013372300 2140 0MS 0Msg Server 1 2140 MsSInitMSStartmsxxserv1212mQ0I2005021013372300 2140 0MS 0 getservbyname 0 NiPServgetservninti.c 0457mQ0A2005021013372300 2140 0MS 0 sapmsMBS NiIServNiPServnixxi_r.2303mQ022005021013372300 2140 0MS 0Msg Server 2140 MsSHaltMSStop msxxserv3931iE102005021013372400 2112 0DP 0SCSA 4096 mQ002005021013372400 2112 0DP 000 2112 DpSapEnDPStartdpxxdisp0863mQ0I2005021013372400 2112 0DP 0 WSASocket10091 NiPSockWSASockninti.c 1174mQ052005021013372400 2112 0DP 0 2112 DpHalt DPStop dpxxdisp6216

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

[achim_hauck2 · Accepted solution]

take a look at the trace files dev_ms & dev_disp in the work directory.

what does they say?

kr, achim

[former_member185943 · Accepted solution]

Achim!

Thanks for a hint!

This is far more readable. I can see some error messages, but still don't know what to do. What might "network subsystem" mean?

Anyway, here's what the files say.

Kind regards,

Igor

DEV_MS:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

-

---

trc file: "dev_ms", trc level: 1, release: "46D"

-

---

Thu Feb 10 13:37:23 2005

***LOG Q0I=> NiPSocket: WSASocket (10091: WSASYSNOTREADY: Network subsystem is unavailable) [ninti.c 1174]

• ERROR => NiILocalCheck: NiPSocket (rc=-1) [nixxi_r. 1758]

***LOG Q0I=> NiPSocket: WSASocket (10091: WSASYSNOTREADY: Network subsystem is unavailable) [ninti.c 1174]

• ERROR => NiILocalCheck: NiPSocket (rc=-1) [nixxi_r. 1758]

relno 4640

patchlevel 0

patchno 194

intno 0

pid 2140

***LOG Q01=> MsSInit, MSStart (Msg Server 1 2140) [msxxserv 1212]

***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 457]

***LOG Q0A=> NiIServToNo, NiPServToNo ( sapmsMBS) [nixxi_r. 2303]

• ERROR => MsCommInit: NiListen(sapmsMBS) (rc=NIESERV_UNKNOWN) [msxxserv 6800]

• ERROR => MsSInit: MsSCommInit [msxxserv 1254]

• ERROR => main: MsSInit [msxxserv 3892]

***LOG Q02=> MsSHalt, MSStop (Msg Server 2140) [msxxserv 3931]

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

DEV_DISP:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

-

---

trc file: "dev_disp", trc level: 1, release: "46D"

-

---

Thu Feb 10 13:37:24 2005

relno 4640

patchlevel 0

patchno 242

intno 0

pid 2112

***LOG Q00=> DpSapEnvInit, DPStart (00 2112) [dpxxdisp 0863]

MtxInit: -2 0 0

MBUF state OFF

MBUF opmode USE

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation std

<ES> Memory Reset enabled as NT default

<EsNT> EsIUnamFileMapInit: Initialize the memory 64 MB

<ES> 63 blocks reserved for free list.

ES initialized.

***LOG Q0I=> NiPSocket: WSASocket (10091: WSASYSNOTREADY: Network subsystem is unavailable) [ninti.c 1174]

• ERROR => NiIListen: NiPSocket (rc=-1) [nixxi.c 0488]

• ERROR => DpCommInit:: NiBufListen (rc=-1) [dpxxdisp 5707]

• ERROR => DpSapEnvInit: DpCommInit [dpxxdisp 11011]

***LOG Q05=> DpHalt, DPStop ( 2112) [dpxxdisp 6216]

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<,,,

[achim_hauck2 · Accepted solution]

Igor,

take a look at your services file (located in $WINDIR$/system32/drivers/etc or /etc). there should be an entry:

sapmsMBS 36<Systemnumber, most likely 00>/tcp

additionally try to ping your hostname, that you've used during installation:

ping <hostname>

if you don't get answers, add an entry in the hosts file in the same directory, with:

127.0.0.1 <hostname>

kr, achim

[former_member185943 · Accepted solution]

Hi, Achim!

I resolved it - it was either a SAP or a Windows bug.

Thanks to your suggestion, I used error messages from the trace files and found a SAP note which suggests that there might be some problems with Win 2000 and certain SAP functionalities.

The troublesome functionalities should therefore be disabled by setting the environment variable QOSDISABLE to any value.

Although I'm on XP I tried it and it worked.

Thanks once again!

Kind regards,

Igor

[Former Member · Accepted solution]

Hi Igor,

I have the same error while starting Mini SAP 4.6D in Windows XP.

As mentioned , i have created the environment variable and assigned value 1. Still it is not working.

If you have the notes number / steps of how to solve this , please send it.

Thanks

Anand

[Former Member]

I have added "QOSDISABLE" to environment variables and had set its value to "NO". Now the problem has been resolved and I am able to use my Mini Sap.

Regards,

Nageswara Rao

[Former Member]

Hi,

I recieve the same error Msg_server died ....kindly tell me the note number to resolve this problem.

regards

[Former Member]

Try the solution in this post <a href="http://groups.google.co.uk/group/comp.os.ms-windows.networking.tcp-ip/browse_thread/thread/45a10054afbeb07c/6ff556f870698fe5?lnk=st&q=tcpservicesnotrecognized&rnum=4#6ff556f870698fe5">http://groups.google.co.uk/group/comp.os.ms-windows.networking.tcp-ip/browse_thread/thread/45a10054afbeb07c/6ff556f870698fe5?lnk=st&q=tcpservicesnotrecognized&rnum=4#6ff556f870698fe5</a>.

Seems that MSN Messenger upgrade messes with the ability of SAP to read the services file.