(nilm) Write error to client: TIMEOUT.

[JFiddie]

We have had to restart the license manager 3 times because it had quit responding to requests since migrating to this server on Aug. 1st.  

Each time the VLM server state is Running and everything is green but have found that the last entry in lmgrd.log is the error in the subject line.  

We are running VLM 3.1.0.250 on a VM of Windows Server 2008 R2.

We are trying to determine if the write to client errors are causing the server to lock up or if it is just a coincidence they are the last entry?

Are there any other ways to determine the cause of the lock up other than the lmgrd.log or the Event Viewer (which shows no related entries).  

[A-Guz-Man]

Hi JFiddie,

When you say you had to restart the license manager you mean the Volume License Manager right? (VLM) What was the last server where the VLM was hosted?

It seems weird that requests locked the VLM, have you tested connections betweent he clients and the server? (Ping each other , Open Telnet connection)

[JFiddie]

A-Guz-Man,

Correct, restarting the VLM resolved the issue.  

This server is for our Enterprise Agreement which replaced a number of VLAs hosted in a number of locations.  

The users called out in the error message receive their licenses, it is other users that call in after the VLM stops responding preventing them from getting a license.

[A-Guz-Man]

JFriddie,

Have you considered taking this request to the Support channel?This could speed up the narrowing of the issue and I'm sure that because your company has an Enterprise Agreement you could call for an Application Engineer.

I'm curious why this VLM stops, is this easily reproducible? At what conditions does this happens?