kriki: The NAV2009R2 webservice does not start in time

[Blog bot]

Yesterday, I had a customer blocked.

What happened?

We imported some objects and restarted the webservice so it would take the new objects. But the webservice didn’t start anymore. (BTW: they still use the classic environment but a lot of data comes by webservice.)

In the event-log, there was nothing from the webservice. Strange.

But I got some other messages stating that some entries in the registry were blocked by the webservice user and had been unblocked by the user login service (or something like that). What the ….????

What is going on?

Problem with the account used for the webservice? Tried another account. Same problem. So, not a problem with the user account.

Is it SQL Server somehow? Changed SQL Server setup and restarted SQL Server to see all logins (failed and succeeded). After a lot of retries to start the servicetier, I rarely got a login from it in SQL Server. So most of the time, the servicetier doesn’t even get to SQL Server.

Firewall, antivirus? Disabled. Still same problem. So this is not slowing down things.

With the strange messages in the event-log, I found that there was a 30-second time-out. But what kind of time-out?

After some duckbingling, I found that the service controller starts a service and that service should communicate to the service controller when it is completely started. If after 30 seconds the service controller doesn’t receive a message from the service, the service controller assumes that the service has failed and KILLS it!

Ahha! Now we have something!

Maybe if I can change that 30-second time-out to 2 minutes, the webservice has enough time to activate itself.

I found this post http://www.itgeekdiary.com/increase-the-service-timeout-period/ that helped me how to change the 30-second time-out. In short: I needed to add/change a key in the registry and then restart the server.

Done that. Restarted the server. And TADAAAAAA. The service is up and running and humming.

Doublechecking it inside NAV: I do some logging of webservice processes to see what they are doing and indeed, logs were coming in.

So, did I fix the problem?

No. I didn’t! But I did find a way around it.

The problem is not fixed, because that would mean having the webservice start under 30 seconds.

It is a some problem between the webservice and Windows. But I don’t have the knowledge to find out the problem.

 

But anyway, if my experience can help someone avoiding to be problem-solving from 17:00 to 22:30, then I would say, it has been a useful post.



Читать дальше