Lansweeper service stops run

[cheche]

After a time running the service stops run with a shared memory violation. This is the only message in errorlog. The server is a virtual machine.

[klug2892]

That error that I included in the last post is from the application event log on the test server I mentioned previously. I let the system run over night to see if it would fail again and it didn't make it very long before the service stopped and it wasn't running when I checked it this morning. It had only scanned about 1200 systems before it failed.

[Hemoco]

Is this error fixed?

Faulting application Lansweeperservice.exe, version 4.0.0.24, time stamp 0x4bd85ed0, faulting module mscorwks.dll, version 2.0.50727.4200, time stamp 0x4a9ee32d, exception code 0xc0000005, fault offset 0x0000000000292007, process id 0x%9, application start time 0x%10.

the 0xc0000005 was fixed for the other user with these patches.
You also seem to have a 0xc0000374 error.

From what I can find there can be a lot of causes for this:
http://www.google.com/search?hl=en&rlz=1B3GGGL_en-GBBE342BE342&q=0xc0000374+ntdll.dll

[klug2892]

I've applied the patches you suggested with the exception of KB955454 because it doesn't apply to Server 2008 R2, it's for Server 2003 R2. However, even after those patches, the service still errors out and subsequently stops. This is all done on a brand new test server running Server 2008 R2 with nothing other that Windows Updates, SQL Server 2008 R2, and LanSweeper.

Faulting application name: Lansweeperservice.exe, version: 4.0.0.24, time stamp: 0x4bd85ed0
Faulting module name: ntdll.dll, version: 6.1.7600.20548, time stamp: 0x4ad6c384
Exception code: 0xc0000374

[Hemoco]

Could you try these patches on your windows 2008R2 please

Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A"
http://support.microsoft.com/kb/979444

A memory leak issue occurs in the Windows Management Instrumentation service on a computer that is running Windows Server 2008 R2 or Windows 7
http://support.microsoft.com/kb/977357/en-us

The "Win32_Service" WMI class leaks memory in Windows Server 2008 R2 and in Windows 7
http://support.microsoft.com/kb/981314/en-us

The Wmiprvse.exe process crashes when an application runs a query to enumerate process information on a Windows Server 2003 R2-based computer that has Subsystem for UNIX-based Applications installed
http://support.microsoft.com/kb/955454/en-us

After you enable large pages for a process in Windows 7 or in Windows Server 2008 R2, the process stops responding intermittently
http://support.microsoft.com/kb/975992

[klug2892]

Attached is all the Application Error events related to Lansweeper.exe.

[Hemoco]

So far the problem is only reported for Win2008R2 (but it doesn't happen on all servers)

Could you post the exact errormessages related to Lansweeper from the eventlog please.

[klug2892]

Apologies, I copied the wrong event. The FWASU.exe event is from an internally developed application. That shouldn't have been included. My mistake.

What about Server 2008 (with SP2), though? That's what I'm currently running and it still occurs.

[Hemoco]

We are currently investigating this problem with another customer.
It seems to only happen on Win2008R2

FWASU.exe error is not related to lansweeper

[klug2892]

I'm having an issue with the service failing as well. I originally thought it was something else I had installed on the box as it was restarting itself as well, so I just wanted to start clean as it was running the beta version previously. I reinstalled the OS (Windows Server 2008 R2) and SQL (SQL 2008 Enterprise x64). The same symptoms happened again, so I rebuild the box again on 5/5/2010 with Server 2008 SP2 x64 and it's still happening. I set the service to restart itself, but it will only do that so many times in a period of time. Here are some the error messages in the application event log. There are more if you need them, but these are the three that show the differing faulting modules.

5/8/2010 7:21:50 PM
Faulting application Lansweeperservice.exe, version 4.0.0.24, time stamp 0x4bd85ed0, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0x2a04, application start time 0x01caeefd809b6120.

5/8/2010 7:21:49 PM
Faulting application Lansweeperservice.exe, version 4.0.0.24, time stamp 0x4bd85ed0, faulting module mscorwks.dll, version 2.0.50727.4200, time stamp 0x4a9ee32d, exception code 0xc0000005, fault offset 0x0000000000292007, process id 0x%9, application start time 0x%10.

5/5/2010 3:44:28 PM
Faulting application FWASU.exe, version 2.0.3.0, time stamp 0x4b86ddf3, faulting module KERNEL32.dll, version 6.0.6002.18005, time stamp 0x49e041d1, exception code 0xe0434f4d, fault offset 0x00000000000176fd, process id 0x%9, application start time 0x%10.

Should I not be running x64? It's running on a standalone box, not in VM and I've never had IP Scanning turned on, just Active Scanning. It seemed to work well in beta just fine. Is there anything else I can provide to help figure this out?