- Check to make sure that the client is installed.
- Check that the service is running.
- Navigate to services.msc
- Look for the LabStats Client service.
- If the service is not started, then start the service.
- If the service is running, restart the service
- See if the station is checking in.
- If starting/restarting the service fixes this, the issue may be due to a change made by Microsoft to the default time allowed for a .net application to startup. In some environments, LabStats cannot start within the new 30-second time frame.
- To fix this you can set the startup type of the LabStats Client service to Automatic (Delayed Start).
- Or, we can send you a file to update your registry entries to change the time limit back to 1 minute (this will affect the time allowed for all .net applications to startup)
- Double check that the station is not checking in under a different computer.
- This can be accomplished by searching by mac address in the Station Manager.
- Check to make sure that the station’s mac address is not on the Ignored Mac Address list.
- If the station is still not checking in, contact LabStats Support.
Updated on September 26, 2018
Was this article helpful?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!Contact Support