Service NAV 2009 R2 is suddenly stop

johanna

Dear all,

I am using NAV 2009 R2. Today, the NAV 2009 R2 service is suddenly stopped.
In event viewer, there is application error like below

Faulting application name: Microsoft.Dynamics.Nav.Server.exe, version: 6.0.33750.0, time stamp: 0x50381129
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x054fb480
Faulting process id: 0x83c
Faulting application start time: 0x01cea640937b2f45
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\60\Service\Microsoft.Dynamics.Nav.Server.exe
Faulting module path: unknown
Report Id: 45619aac-13a2-11e3-a730-5cf3fce30bf4

Why this is happen and how to solve it?
Please help..
Thank you..

kriki

Did you have it only once, sometimes, always?

You can also put the service to autorestart in case of a crash.

johanna

Dear Kriki,

Thank you for your response.
This issue is only happened once until now.

geordie

Does the NAV server event viewer show anything?

johanna

Dear Geordie,

Thank you for your response.
Yes, the event viewer is shown like below.

Faulting application name: Microsoft.Dynamics.Nav.Server.exe, version: 6.0.33750.0, time stamp: 0x50381129
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x054fb480
Faulting process id: 0x83c
Faulting application start time: 0x01cea640937b2f45
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\60\Service\Microsoft.Dynamics.Nav.Server.exe
Faulting module path: unknown
Report Id: 45619aac-13a2-11e3-a730-5cf3fce30bf4

knm

johana,

I'm experiencing the same issue. Were you able to resolve this issue? If so, would you please share how you have fixed it?


kriki,

You mentioned that you can put the server to autorestart in case of crash. Would you please share how the autorestart can be setup?

Thank you!

kriki

run services.msc.
Search your service and go to properties.
Then go to the recovery tab
Set "first failure","second failure","subsequent failures" all to "restart the service".
"restart service after". Put it to 0. (0 is to restart it immediately after a crash to be offline as least as possible.)

knm

kriki,

Thank you so much for your feedback.
Yes, I was looking at this option in Windows Service's "Recovery", but what I have realized is that when this Application Error occurs, the Windows Service will remain its status as “Started”, although when you try to run RTC, it will not connect. So I don’t think Windows Service “Recovery” would work, since the status is indicated as “Started”...
I'm hoping there's another way to automatically identify when RTC would not start due to the "Application Error" event.

kriki

That doesn't sound good.
Check if you don't see any other message in the eventlog that says that the service has started after the crash.

If there is, it means that the servicetier has some problems connecting to the SQL server or the clients to the servicetier at that moment.

When it seems to have crashed, you should check with taskmanager (or even better process explorer) if the .exe is still running. Best would be NOT to automatically restart the service to be able to see if it effectively crashed and stopt running.

BTW: what do you do when you notice that the RTC cannot reconnect? How do you make it reconnect?

knm

kriki,

Unfortunately I don't see any other message in the eventlog.
When we experience this issue, what we usually do is upon confirming there is an Application Error evenlog for NAV, we restart the NAV service. Sometimes the NAV service won't stop, so we have to force kill the service session and start...

kriki

Sorry for the long delay.

Some other things you can check (I am running out of ideas...):
-Have your server up-to-date with the service packs/hot fixes.
-Check if there is some NAV hotfix that fixes that particular problem.
-Create another servicetier and start using that one with a few users. This is to check if the problem is connected to the installed servicetier or not. If this works, stop using the old one.