
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2010 04:33 PM
Hi,
in the scanning status http://lansweeperserver:9524 I have "in queue", "in process", "thread running" = 0. These values go to 0 after some time, maybe after completing a first scan (for example, after manually restarting the service). Is this a normal behavior?
This seems to occur after the installation of the lansweeperservice.exe test for the crash of http://www.lansweeper.com/forum/yaf_postst3463_Lansweeper-service-crash-v-4.aspx topic and persists with 4.0.0.24 upgrade installed
Thanks for the great support
in the scanning status http://lansweeperserver:9524 I have "in queue", "in process", "thread running" = 0. These values go to 0 after some time, maybe after completing a first scan (for example, after manually restarting the service). Is this a normal behavior?
This seems to occur after the installation of the lansweeperservice.exe test for the crash of http://www.lansweeper.com/forum/yaf_postst3463_Lansweeper-service-crash-v-4.aspx topic and persists with 4.0.0.24 upgrade installed
Thanks for the great support
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2010 06:03 PM
No error in the errorlog.txt after the upgrade to 4.0.0.24, anyway no new scan scheduled.
I think that there were always a lot of machines in queue before upgrading, but if you say is a normal behavior I'm sure it's true 🙂
Thanks
I think that there were always a lot of machines in queue before upgrading, but if you say is a normal behavior I'm sure it's true 🙂
Thanks

Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2010 05:17 PM
I had something similar after upgrade, the problem was caused by Lansweeperservice.exe.config that was overwritten, so you'll need to correct the credentials again. In the log file of the service there were messages about problems accessing database.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2010 04:48 PM
If they go to 0 it means that no scans are queued at the moment, this is normal behaviour.
If the service crashed (hopefully not) you should see it in your errorlog.txt file.
If the service crashed (hopefully not) you should see it in your errorlog.txt file.
