NSD running, generates log/error

Hi,

We have a user that gets the NSD generated logs. Doesn’t matter if we uninstall, reboot, and reinstall the clients, they get the same error when they are in the client and opening a word doc (I’m leaning towards word being the problem?).

I think this is the ‘fatal stack’ error? I figured posting the whole thing would be a no no:

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

FATAL THREAD 1/6 [ WINWORD:0984: 976]

FP=0x0012f0fc, PC=0x65048d08, SP=0x0012f0ec, stksize=16

EAX=0x00000688, EBX=0x00000001, ECX=0x00000510, EDX=0x00220003

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

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

Exception code: c0000005 (ACCESS_VIOLATION)

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

[ 1] 0x65048d08 VBE6.rtcEnvironVar+32564 (16,6f350d0,1eb310,1)

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

PASS 2 : FATAL THREAD with STACK FRAMES 1/6 [ WINWORD:0984: 976]

FP=0012f0fc, PC=65048d08, SP=0012f0ec, stksize=16

Exception code: c0000005 (ACCESS_VIOLATION)

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

Subject: NSD running, generates log/error

posting whole nsd files isn’t neccessary, but including at least full call stack of fatal thread might help to get answers:)

VBE6.dll is a component of visual basic… have you tried to reinstall word? i assume that user doesn’t try to launch but edit word-document (notes wouldn’t crash then i guess) - does it happen on all word documents? can docs be opened using word native?

Markus Seitz

markus.seitz@icodex.com