Information not updating

[ccdesktop]

For the last week or so it doesn't look like Lansweeper is updating.

The total number of machines isn't increasing (and I know there are new machines being installed)

And all the scans for hardware / software / users etc are not updating.

It shows the last seen time correctly - but software scans, for example are set to "0" to update each time the user logs on - but this date is not updating.

Also - using the Premium tools I do a trigger scan and then all the dates against the scan items disappear and go red!

Nothing obvious in the log file either.

Any ideas...?

[ja3hawk]

Hmm. I think I tried using Vista as a server but ran into problems... Is this supported?

[gsvarney]

I am continuing to have problems with many of my machines. There are still a number of them that are not displaying most of the information. In some cases I'll force the firewall off (if RPC was the problem) and then run lsclient from it. When I do this it scans, but doesn't fill in much info. What I'll see under "High Priority" is everything is OK EXCEPT "Never scanned software" and "Never scanned OS" are red. Everything under scan is also red. The WMI settings that I've checked seem to be universally at the defaults which are fine.

My server is Vista 32bit, most of the failing clients are XP Pro 32bit. I have removed all of the failed computers and rescanned and some still won't. I just now deleted on such computer from the database, ran the command to disable firewall (though this was already done) then ran lsclient on it. Same thing.

[ja3hawk]

I would like to confirm this problem as well. We had just 1 or 2 machines not showing up but when I restarted the service It did a scan and pulled in the machines. I'm thinking about just creating a batch script to restart the service a couple times a day but this is more of a work around than a real fix...

Also I'm having an issue where after I restarted the service the computer name column sorts randomly. Anybody else having this issue?

[ccdesktop]

I'm getting this problem regularly now.

I find I have to restart the service several times a day as although the number of machines being "processed" is increasing nothing is actually being scanned.

Restarting the service is not the ideal solution as I need it to be scanning in the background constantly - and at the moment a lot of updates of info are being missed as it is not actually scanning!

[Wayne]

The queue as well as "in process" and "threads running" were all empty during the problem. The count of scanned computers would increase, however.

Since restarting the service it has been scanning computers normally. Right now I have 187 in queue, 25 in process, 20 threads running and 1970 scanned computers. I've increased the number of threads to 40 in the config file but have not restarted the service yet.

[Hemoco]

When the service stops scanning but is still running. Could you check http://127.0.0.1:9542 to see if your queue is full.

[Wayne]

I also have problems where the Lansweeper service is still running but not properly scanning computers. I have verified this by running the lsclient.exe on an unscanned machine and watching the "Last seen" field. The # of processed clients on the service status page increments as well. The data for the client remains unscanned (red squares all around). Once I restart the service, computers will start scanning properly again. If I rescan the same machine it will now populate the database with the client data, so it wasn't a problem with access to the client via WMI or remote registry.

The virtual server LS runs under spikes the CPU in the morning for a few hours when clients start logging on, so it is quite easy to see when the service has died by looking at CPU graphs in VirtualCenter.

The only recent errors in the Errlog.txt were:

-------------------------------------------------------------------------
System.Runtime.InteropServices.COMException (0x80072116): Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateCall(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack, Boolean IgnoreReturn)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)
at Lansweeper32.sweeperthread.LSADusersearch(clsComputer mycomputer, clsThreadinfo Threadinfo, SqlConnection& sqlcon)
COMPUTERNAME\USERNAME
9/28/2008 6:32:03 AM : COMPUTERNAME
System.Runtime.InteropServices.COMException (0x80072116): Name translation: Could not find the name or insufficient right to see name. (Exception from HRESULT: 0x80072116)
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateCall(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack, Boolean IgnoreReturn)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)
at Lansweeper32.sweeperthread.LSADusersearch(clsComputer mycomputer, clsThreadinfo Threadinfo, SqlConnection& sqlcon)
-------------------------------------------------------------------------

(I changed the computername and username to a generic) In this case, the user logs onto a local account instead of a domain account, so it appears that LS is failing on some lookup. lsclient is being run by the computer startup script, I believe, due to some issues that need to be resolved.

3.2 seemed to fix most of the errors logged by the service, which is great. Unfortunately, the service doesn't seem to run for long.

I am now waiting for the service to stop scanning again to try to narrow down if it fails after the above condition.

[Hemoco]

When your threads are too high the service can "clog", try lowering the threads to solve the problem.

[ccdesktop]

It was on 100 when this issue first appeared.

How come there are 174 stuck "In process" - and other than stop / starting the service - how can I bump these out?

[Hemoco]

100 should work, but I wouldn't recommend going above 128