Lansweeper service stops with System.OutOfMemoryException

[mdotadmin]

This is the error message in the Server Application Event Log:
An unhandled exception ('System.OutOfMemoryException') occurred in Lansweeperservice.exe [8012]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

The server is Server 2003 R2 with 4g RAM and 8g of Pagefile space. There are around 2000 clients being scanned.
The service stops after 24 to 48 hours of running and has to be restarted. I am using version 3.2.2.0 of Lansweeperservice.exe. On one occasion, when I looked at processes on the server, Lansweeperservice was using just over 1.6g of RAM.

Do I need to add RAM to the server, or is Lansweeperservice not releasing RAM?

There are many DCOM errors like: DCOM was unable to communicate with the computer "clientname.domain" using any of the configured protocols.
Not sure if this is related to the service stopping or not.

Any suggestions?

[mdotadmin]

Setting the Service properties to restart on errors, and resetting the restart counter each day seems to be a good workaround. We have a large number of computers that are only on the network for short periods of time. This causes DCOM errors when Lansweeper tries to scan them and they are not available. That may be one cause for the out of memory situation.

[Hemoco]

We are currently testing a debug build at the affected customers system.
So far version 3.5 seems to solve the problem.

[sticky]

Hi was there a resolution to this problem? I'm also experiencing this.

Assembly Version: 3.2.3214.23938

My server isn't quite as powerful as mdotadmin's:
W2k3 Svr R2
2.66 GHz P4
1Gb RAM

~5,000 active scanning hosts

Following is logged in the application log when the service terminates:
Event ID: 5000
Source: .NET Runtime 2.0 Error
Description: EventType clr20r3, P1 lansweeperservice.exe, P2 3.2.3214.23938, P3 48fb2591, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 1239, P8 3b, P9 system.outofmemoryexception, P10 NIL.

Multiple DCOM errors also logged in the System log (although I suspect these are part of normal operation as they are just complaints about not being able to talk to certain machines I wouldn't expect them to be able to talk to anyway).

When the lansweeper service is running, typically consumes 80 - 90% cpu (luckily this server doesn't do anything else!).

This isn't a huge deal for me as I have another program (eventsentry) monitoring the service and restarting it when it fails. Would be nice if it didn't crash though :-).

[mdotadmin]

I could not determine how to attach a file to a Forum reply. I sent an email with the errorlog attachment and screenshots of the event log entries.

[Hemoco]

This is the latest version.

This is not a known problem: with 20 threads the service should stay under 100 MB memory

Could you attach your errorlog.txt and eventviewer information please.

Do you have this problem with active scanning on or off?

[mdotadmin]

Assembly version is 3.2.3214.23938

[Hemoco]

Could you take a look at the assembly version of the lansweeper service please. (same screen where the version is located)