Services stop / shut down offline with timeout error

netblazer

Hi guys we have a serious issue in production... thank God it's on our slow period :

The nav serviced, without any explanation, decide to stop. All services work when they are online. User account is a domain account.

The services are on auto-start. The only remote explanation I have is this error in the windows application log, does thta ring a bell to anyone :

Service:
User: BELISLE-LAN\navservice
Type: System.Data.SqlClient.SqlException
Class: 11
LineNumber: 0
Number: -2
Server: NAVTEST
State: 0
Source: .Net SqlClient Data Provider
ErrorCode: -2146232060
Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
StackTrace:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.Dynamics.Nav.Runtime.NavDatabaseChangeListener.TryExecuteReader()
at Microsoft.Dynamics.Nav.Runtime.NavDatabaseChangeListener.CollectTrackingObjects()
at Microsoft.Dynamics.Nav.Runtime.NavDatabaseChangeListener.TimerHandler(Object param)



I've tried shutting down the SQL Server for 1-2 minutes but that does NOT crash the services. However apparently putting a lot of stress on the server like a major file import while renaming a company crashes the service everytime (3 times in a matter of 15 minutes).

Again when the services are online we can process our orders without any problems..

wic

same problem here... appears on a test local machine (with everything on it). It's not a top speed box but it's a good box.
You work on the RTC and suddenly server doesn't respond-> the nav server is in stopped state.
Sometimes it happens at the startup of the RTC client.

Any idea

regards
Chris

netblazer

Here's the workaround I came to put in place since I've not heard back from the consulting company that implemented NAV.

When I have a timeout error while calling the web services, I call a SQL server procedure which starts a job (permission workaround), in that job I have 2 steps :
#1
sc \\serveurnav start MicrosoftDynamicsNavServer
#2
sc \\serveurnav start MicrosoftDynamicsNavWS

sc is a remote command prompt which executes on the server (serveurnav).

wic

:shock: ok, this is a plaster not a solution :-#

thanx for the quick answer.

I'll look further and give you feedback as soon as I've a SOLUTION !

netblazer

I totally agree, the solution is that MS Nav fixes the problem. I've tried that route 2-3 times without any success so I had to stop the bleeding in the mean time... So far that works pretty good. The only downside is a 25 seconds delay when that happens, but it's still a bit better than having the website completly unusable.

netblazer

wic wrote:

:shock: ok, this is a plaster not a solution :-#

thanx for the quick answer.

I'll look further and give you feedback as soon as I've a SOLUTION !

So, did your research turn up anything usefull?

wic

:-k not actually..

I've to remember the problem->did we found a solution?->what was the status of it?
some holidays did dramatically erase part of my knowledge...

Sorry->if something reappears I'll tell you asap.

regards
Chris

ryanatwork

Same issue here on 2009 SP1.

Anyone have ideas ?

wic

I'm looking forward to install the latest build.

This should happen next week so I'll give you feedback as soon as I could analyse that afterwards it works better.

(Oh! today my english is still aleep )

Regards

ara3n

hello wic

Any update? Thanks. Experiencing this also as well.

netblazer

Never got any news from our contact.

Aside from my hack to "keep it going", I never was able to solve it.


The only other thing I can point out is that our contact had a ton of issues trying to get it to work in the first place. It took over 1 month of trial and error before it finnally worked and even then I'm not 100% they knew 100% why it worked.

wic

hi guys,
sorry for the long delay...
It is fixed (or at least it didn't appear since) by installing the latest build (it was the most recent). Actually they have the 32029 build.
So for me it's solved... who know's maybe it could appear again.

Thanx for participating to the discussion, see you =D>

manju

Hi,

Getting above issue of timeout in NAV2016 CU11. Any insight would be appreciated.

Thanks