Axapta Client getting Crashed

Finance and Operations/AX Technical Forum
1

To start with, I must tell you I am a new comer in the world of Navision. Till now I am through with the 3 tier deployment of Axapta with 1 server and several clients. But I dont know why two of the client machines (one with Windows 2000 and another Windows 98 ) get crashed while the server is running ok along with another client machine (Windows 2000). It is also generating a AxaptaCrash.log file in the Temp directory. I am copying the content of the file with this message as I am not able to make anything out of it. AxaptaCrash.log Axapta Crash Dump File for Axapta build 1951.8 (Sep 17 2002 01:46:40) Dumped : Wed Aug 06 11:38:34 2003 Crash : Exception 0xc0000005 caught (unspecified) in thread 0xfff72d63 of process 0xfff62533. ------------------------------------------------------------- --# FV EIP----- RetAddr- FramePtr StackPtr Symbol 0 .V 65346970 653462f7 00d4da54 00d4d9d8 Mod: OLEAUT32[OLEAUT32.DLL], base: 65340000h 1 .V 653462f7 6602a1ce 00d4da70 00d4d9d8 Mod: OLEAUT32[OLEAUT32.DLL], base: 65340000h 2 .V 6602a1ce 66029fc7 00d4e3cc 00d4d9d8 Mod: MSVBVM60[MSVBVM60.DLL], base: 66000000h 3 .V 66029fc7 00814217 00d4e428 00d4d9d8 Mod: MSVBVM60[MSVBVM60.DLL], base: 66000000h 4 .V 00814217 00813cd8 00d4e90c 00d4d9d8 Mod: AX32[AX32.EXE], base: 00400000h 5 .V 00813cd8 00000000 030317bc 00d4d9d8 Mod: AX32[AX32.EXE], base: 00400000h Stackdump exit code 487 (Attempt to access invalid address) ------------------------ Please tell me why such problem is arising and how to solve this problem.

2

Are you doing anything specific when these machines crash?

3

Maybe you should try updating (or re-installing) these machines. Seems that you have some kind of library version conflict there!

4

I also get the same error message almost everyday. It usually happens when I am doing development. (I use AXAPTA on Windows 2000 Advanced Server, and Windows Server 2003)

5

Thanks for your response. I uninstall the complete set up (including server and client) and reinstall it again. Now I am not getting the problem except only one machine. I cannot understand why such a problem was coming in only one client machine.