NOTICE: Our Community is moving. Get more information. Updated information on a New Login Process
When running the Query Log tool in SilkMeter some entries may look like this:
This will happen if in the log file there is an entry for a Stop LicId but a corresponding Start LicId was not found. Only the Start LicId action has the host and user information and on licence check-in, the host/user data is got by looking for the Start LicId with the matching licence id (the number between the Start/Stop LicId column and the PolId column). This will happen if the SilkMeter service is restarted and some licenses are already checked out. After the SilkMeter service restart, when a running copy of Silk Test sends the check-in request it is logged but the corresponding checkout request is missing because the SilkMeter service initialisation resets the SilkMeter server.
Asking your IT department to review the Windows Event Logs may throw some light on why the SilkMeter service is being restarted.