Domino 7.0.3 crash

hcl-bot · December 3, 2007, 6:56am

Hi!

Really need some help here…

First of all, i’m a Domino newbie, but here goes:

We have got a Domino 7.0.2, that crashed, so we upgraded it to 7.0.3 - But it didnt help… Ive got some NSD log files, with some errors. So i hope someone knowns what the error is

I can be up and running for 5 minutes, or 5 hours… But then it crashes.

Here’s the first log (Last 10 lines of the file, where it says “ERROR/WARNING”…):

WARNING (0): [nservice: 0b4c] is accessing data directory d:\lotus\Domino\Data but is not in the process list

WARNING (0):

Instruction Pointer is NULL!! Will attempt to extract first address from stack context

WARNING (0): failed to match open view DBH=28

ERROR (0): Bad chunk desc 0

ERROR (0): Bad memchunk desc 0 (256)

ERROR (0): NSD thread b60 got system exception: ACCESS_VIOLATION (3221225477)

ERROR (0): exception(0): NSD thread b60 got system exception: ACCESS_VIOLATION (3221225477)

Please send the following files:

            NSD Log : d:\lotus\Domino\Data\IBM_TECHNICAL_SUPPORT\nsd_W32I_ntserver_2007_12_02@10_45_45.log

          Core Dump : d:\lotus\Domino\Data\IBM_TECHNICAL_SUPPORT\core_nSERVER_W32I_ntserver_2007_12_02@10_45_45.dmp

And the second NSD log file (Only the FATAL stuff):

############################################################

FATAL THREAD 1/3 [ nSERVER: 0b9c: 0bcc]

FP=0x0007d0b8, PC=0x60176b81, SP=0x0007c944

stkbase=00080000, total stksize=28672, used stksize=14012

EAX=0x01390648, EBX=0x0000000c, ECX=0x00d50000, EDX=0x00d50000

ESI=0x60b15dbc, EDI=0x00000000, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010206

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x60176b81 nnotes.Panic@4+417 (60b15dbc)

@[ 2] 0x6008b4f5 nnotes.AllocSharedRegion@12+1685 (c,800000,0)

@[ 3] 0x60002474 nnotes.DPoolAlloc@16+1588 (d50014,401128,18438,19008ac)

@[ 4] 0x60004246 nnotes.AllocObject@24+294 (d50014,60dff020,190089e,401128,0,0)

@[ 5] 0x60007424 nnotes.OSMemoryAllocate@12+132 (18438,401122,2bf2be2)

@[ 6] 0x605efac0 nnotes.OSCreateBPoolExtended2@44+464 (8a08,a8e,40000000,20,0,0,0,0,0,0,0)

@[ 7] 0x600b4730 nnotes.OSCreateBPoolExtended@36+48 (8a08,a8e,40000000,20,0,0,0,0,0)

@[ 8] 0x60029dc9 nnotes.NetInit@0+1625 ()

@[ 9] 0x606eeefb nnotes.LogAddTextVCtx@32+75 (1,4,60b25258,0,0,0,0,0)

@[10] 0x600cc506 nnotes.LogAddTextV@28+38 (1,4,60b25258,0,0,0,0)

@[11] 0x60118719 nnotes.LogEventTextVExt@20+41 (0,7e214,0,0,0)

@[12] 0x601186ea nnotes.LogEventText+26 (7e214,0,0,0,0)

@[13] 0x601cfc4c nnotes.AddInLogErrorText@12+28 (7e214,0,0)

[14] 0x035c15b9 nEMPNOTIFY.DllUnregisterServer+217 (601223ae,0,1)

[15] 0x035c1c57 nEMPNOTIFY.MainEntryPoint+43 (3d62dc,141000e,0)

@[16] 0x6001377c nnotes.InitializeNSF@0+3244 ()

@[17] 0x60046559 nnotes.NSFDbSetMode@16+25 (0,e,0,0)

@[18] 0x600528cd nnotes.NIFNSFInitialize@0+13 ()

@[19] 0x100010c0 nserverl.FirstProcessMain@8+16 (1,3d62dc)

@[20] 0x100013b6 nserverl.ServerMain@8+550 (1,3d62dc)

@[21] 0x00401ccd nSERVER.WinMain@16+557 (400000,0,2,a)

@[22] 0x0040205d nSERVER.WinMainCRTStartup+388 (0,0,7ffde000,0)

[23] 0x77e6f23b kernel32.ProcessIdToSessionId+521 (401ed9,0,78746341,20)

############################################################

PASS 2 : FATAL THREAD with STACK FRAMES 1/3 [ nSERVER: 0b9c: 0bcc]

FP=0007d0b8, PC=60176b81, SP=0007c944

stkbase=00080000, total stksize=28672, used stksize=14012

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

Disassembly of c. 10 instructions before and after faulting address 60176b81:



    60176b5a 56               push    esi

    60176b5b 0506520400       add     eax,0x45206

    60176b60 680c48b060       push    0x60b0480c

    60176b65 50               push    eax

    60176b66 e815dce9ff       call    60014780

    60176b6b 83c40c           add     esp,0xc

    60176b6e e83d3d0000       call    6017a8b0

    60176b73 a14c9fd460       mov     eax,[60d49f4c]            ds:60d49f4c=01390648

    60176b78 8388b614000002   or     dword ptr [eax+0x14b6],0x2 ds:01391afe=0000000a

    60176b7f 6a01             push    0x1

FAULT ->60176b81 c605ffffffff00 mov byte ptr [ffffffff],0x0 ds:ffffffff=??

    60176b88 ff154833b060     call    dword ptr [60b03348]      ds:60b03348=77e668f1

    60176b8e cc               int     3

    60176b8f cc               int     3

    60176b90 55               push    ebp

    60176b91 8bec             mov     ebp,esp

    60176b93 8b4508           mov     eax,[ebp+0x8]             ss:0173805e=00000000

    60176b96 8b0d04f0df60     mov     ecx,[60dff004]            ds:60dff004=00d50000

    60176b9c 6800010000       push    0x100

    60176ba1 50               push    eax

    60176ba2 81c1a15a0400     add     ecx,0x45aa1

    60176ba8 51               push    ecx

Can anyone tell me whats causing this error?

Thanks!

/Carsten

hcl-bot · December 3, 2007, 8:11am

Subject: Domino 7.0.3 crash

Hi Carsten,

it seems to be related to a Non-Notes process (Lines 14 and 15)

[14] 0x035c15b9 nEMPNOTIFY.DllUnregisterServer+217 (601223ae,0,1)

[15] 0x035c1c57 nEMPNOTIFY.MainEntryPoint+43 (3d62dc,141000e,0)

nEMPNOTIFY

On page 5 , From

http://www.sybase.com.pl/_gAllery/17/27/1727.pdf

This DLL, called nempnotify.dll, monitors new mail arriving at the Domino server,

and when new mail arrives, the DLL makes an HTTP request to the Pylon

Anywhere server. This web request contains the username of the user receiving

the new email. If this user has activated Push or Alert devices, the Pylon

Anywhere server will use a courier account or the user’s ID file to connect to the

Domino server and obtain the header information of this new email. Pylon

Anywhere then uses the user-defined filters to determine if the new email is one

that the user wants to be alerted on, or have Push initiated from.

5

The access method that the Pylon Anywhere server uses to read the users’

Domino mailboxes is configured on the Access tab of the Lotus Domino Profiles in

the Pylon Anywhere Admin Console.

hcl-bot · December 3, 2007, 8:30am

Subject: RE: Domino 7.0.3 crash

Hi!

Thanks you very much!

Now that you mention this, we had an Intellisync server installed not long ago, seems like this DLL file is part of it.

So we’ll have our supplier take a look at it.

/Carsten

hcl-bot · December 12, 2007, 10:00am

Subject: RE: Domino 7.0.3 crash

Hi,

I have the same problem with our Domino server and we also have Intellisync installed. Did you find any solution to the problem?

hcl-bot · December 13, 2007, 2:51am

Subject: RE: Domino 7.0.3 crash

Hi,

No, not yet.

We have shut down the Intellisync server, and Domino is running fine now!

We have our supplier looking at it, but no solution yet. I will post again when they have a solution.

/Carsten