Appserver: service did not respond to the start or control..

buchhot

We have 3 NAV application servers running on an Windows Server 2008 SP1 64 bit.
We started the server in the evening (like we often do after the patch tuesday).
Now the app-servers do not start again.
I get the following error message:
"Error 1053: The service did not respond to the start or control request in a timely fashion"

When I try to start the appserver via the command line (logged on to the server with the same account that is used for the service) the appserver starts normal.

Has anybody an idea how to solve this or to get any hint or better error message.
I got no idea how to fix this.

Many thanks in advance

Thomas Buchholz

buchhot

I forgot to mention what NAV we are using.
We are using NAV 5.0 (no SP) austrian version.

garak

The NAS Server (the machine) can connect to the database server :?:
The NAS Service runs not under Local System, it use a windows user ?
If you restart the serve over the mmc snapin for the services you see an error in the EventLog?
The NAs is correct configured? Check this with the mmc snapin for the NAS.

buchhot

Hi garak!
Yes, the machine can connect to the database as this is the database server itself.
The service uses a windows account which is an admin in NAV.
I checked the settings in the snapin, everything is OK. the service was running fine the last months and we did not change anything.
If I start the service via the snapin I get the same error message (timeout while waiting for the service to start -> free translated because our system is german).
As I said I can start the NAS when trying to start it via the command line.

kr
Thomas

Monsta

Hello, buchhot.
Have you solved the problem?
We have similar situation: Windows Server 2008 SP1 64 bit, MS Dynamics NAV 5 SP1, SQL Server 2005.
Application server suddenly refused to start. The error message in event log contains the following message:

A timeout was reached (30000 milliseconds) while waiting for the Microsoft Dynamics NAV Application Server <NAS_SERVICE_NAME> service to connect.

We had installed application server on backup server with connection to database on the main server. It had been working for a period of time (about a month) and then at some point refused to start also there.
Now I am able to install an application server on other PCs (for example, a workstation with Win XP) and it successfully starts with connection to the database.
How to fix the issue? How to make NAS to start on then server?

buchhot

Dear Monsta!

Sorry, no solution yet.
Until today I always have a remote session kept open and have my three NAS started via the command line.
Not very handy but at least it works.
Sorry for not being able to help you any further.

Kind regards.
Thomas Buchholz

Monsta

I've found on the internet the following (here):

Looks like windows tries to verify the signature and this take too much time.

Could it be possible? I checked the file's nassql.exe certificate and discovered that the lowest level certificate in certification path was expired (see image attached).

Although certificate one level higher was not expired.

Any ideas? Is it possible to prolong the expired certificate?

ta5

Any messages in the event log? The normal message for nas usually is

"Der Navision Application Server <service name> startete mit der folgenden Konfiguration:..." (German Text).

Thomas

Monsta

ta5 wrote:

Any messages in the event log?

Hello, Thomas,
Yes, event log's message I have published here a few posts earlier. The message was:

A timeout was reached (30000 milliseconds) while waiting for the Microsoft Dynamics NAV Application Server <NAS_SERVICE_NAME> service to connect.

An attempt to start NAS service using net start command ends with error:

2186 The service is not responding to the control function.

jversusj

Did anyone ever chance upon a resolution to this? I am getting the same error today. Trying to setup up a test NAS to see if SCRIBE will work for us.

Timeout (XXX milliseconds) waiting for the Microsoft Dynamics NAV Application Server <NAS SQL Service Name> service to connect.

einsTeIn.NET

We encountered the same issue and MS said it could be related to this http://support.microsoft.com/kb/2677070/EN-US.

einsTeIn.NET

We still have some doubts regarding the relation between that Windows update and the mentioned system behaviour.

1. It's an optional update and we don't install optional updates until it's really necessary. If I check the list of installed updates this KB is not in, but if I check online the list of available updates it's also not in the list. :?:
2. This update is released on June 12, 2012. If it is installed and we just can't see it why didn't it occur before?

In general this happens when Windows tries to do something during startup of the service and that takes longer than the timeout of the service start. Whatever Windows wants to do...