3.70 Crashes

RChurchill
RChurchill Member Posts: 55
Hi,

We have a customer with many clients (over 80). 4 of them have started crashing. It appears in some cases that Nav crashes can occur when they aren't using the applicaton, in fact not even using the PC!!

The clients are GB 3.70.A and the databases are 3.70.B (native) which was a recommendation from Lars at Microsoft to fix another problem. This set up has been in for well over a year now without any other problems.

3 of the pcs are new builds and the other one has been installed for ages. The error codes are exactly the same on the 3 new ones and the old one is slightly different.

3.70.2.19516, 415c9df5, fin.exe, 3.70.2.19516, 415c9df5, 0, 0004184e

3.70.2.19516, 415c9df5, fin.exe, 3.70.2.19516, 415c9df5, 0, 00100053

The second one appears on the older pc. What is the significance of the last set of characters?

Has anybody got any ideas what can cause these kind of crashes?

Many Thanks in advance

Rob

Comments

  • nunomaia
    nunomaia Member Posts: 1,153
    Have you tried to make a technical upgrade to NAV client and server? Normally that kind of issues if solved with service packs and client hotfixes ? :-k
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • kine
    kine Member Posts: 12,562
    What about screensaver? Try to disable it. May be that error is there... :-)
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • tmatejko
    tmatejko Member Posts: 2
    You can check energy settings as well. Maybe computer goes stand-by?
  • Alex_Chow
    Alex_Chow Member Posts: 5,063
    You also want to make sure that you have enough space on your C: drive to store the Navision temporary files.
  • thaug
    thaug Member Posts: 106
    Try to compile all of the objects when no one else is logged in.
    There is no data, only bool!
  • RChurchill
    RChurchill Member Posts: 55
    Hi Everybody,

    Thanks for all you replies. Microsoft have guided us to trying the latest version of 3.70B (it was a 3.70B client with a 3.70A database, my apologies I've realised I put it the wrong way round) whilst reminding us of course that Microsoft have stopped their support for 3.70 on 12th December.

    THe other thing we are to try is that the SERVER installed is a different build to the 3.70B client. Could that be an issue? Possibly. Failing that we will probably try to move them to 4.0 SP3 executables but that also means a lot of testing to ensure things still work as they should, integration etc.