
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2013 04:40 PM
Hi,
i have a computer where scanning does not work properly and it does not stop:
Aborted ams\amsdblab01\1 scanning takes longer than 2 hours, repair wmi on this machine! 19/04/2013 14:21:56
Aborted ams\amsdblab01\1 scanning takes longer than 2 hours, repair wmi on this machine! 19/04/2013 13:20:55
Aborted ams\amsdblab01\1 scanning takes longer than 2 hours, repair wmi on this machine! 19/04/2013 12:19:55
First, why is scanning not much earlier aborted? I think you can lower the threshold to 10 minutes or so.
Second, how can i stop it?
Using v5069
i have a computer where scanning does not work properly and it does not stop:
Aborted ams\amsdblab01\1 scanning takes longer than 2 hours, repair wmi on this machine! 19/04/2013 14:21:56
Aborted ams\amsdblab01\1 scanning takes longer than 2 hours, repair wmi on this machine! 19/04/2013 13:20:55
Aborted ams\amsdblab01\1 scanning takes longer than 2 hours, repair wmi on this machine! 19/04/2013 12:19:55
First, why is scanning not much earlier aborted? I think you can lower the threshold to 10 minutes or so.
Second, how can i stop it?
Using v5069
Labels:
- Labels:
-
Archive
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2013 11:52 AM
Coworker restarted the computer, that solved the problem.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2013 05:23 PM
WMI (Windows Management Instrumentation) is most likely corrupt on the client machine. Could you do the following so we can confirm this:
- Copy the LsPush.exe found in Program Files (x86)\Lansweeper\Client on your Lansweeper server to the problem machine.
- Run the executable on the client machine. The machine will be scanned locally and the scan results attached to email and copied to your temporary folder.
Afterwards, contact support@lansweeper.com and provide us with:
- Link to this forum thread.
- The LsPush file that was generated.
- The Errorlog.txt file present in Program Files (x86)\Lansweeper\Service on your Lansweeper server.
- Copy the LsPush.exe found in Program Files (x86)\Lansweeper\Client on your Lansweeper server to the problem machine.
- Run the executable on the client machine. The machine will be scanned locally and the scan results attached to email and copied to your temporary folder.
Afterwards, contact support@lansweeper.com and provide us with:
- Link to this forum thread.
- The LsPush file that was generated.
- The Errorlog.txt file present in Program Files (x86)\Lansweeper\Service on your Lansweeper server.
