cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
siverson
Engaged Sweeper
I upgraded to 6.0.2.2 on 5/28. Ever since I have not been able to get scanning to work. And, YES the scanserver service is running and yes I have rebooted and yes to all authentications to SQL are active and working. What happened. Yes, our HelpDesk trial expired that scanning stopped before then.
1 ACCEPTED SOLUTION
siverson
Engaged Sweeper
RESOLUTION provided by Lansweeper that worked:

The upgrade to 6.0.2.2 corrupted the lansweeperservice.exe.config password. They claim it didn't but I claim it did because I've seen this happen with the web.config password where it gets changed from my assigned sql user password to their assigned default password, "myPassword".

Two files to watch out for after a future upgrade.

program files (x86)\Lansweeper\website\web.confg
program files (x86)\Lansweeper\service\lansweeperservice.exe.config

Both contain unames and pwords for sql communication.

View solution in original post

1 REPLY 1
siverson
Engaged Sweeper
RESOLUTION provided by Lansweeper that worked:

The upgrade to 6.0.2.2 corrupted the lansweeperservice.exe.config password. They claim it didn't but I claim it did because I've seen this happen with the web.config password where it gets changed from my assigned sql user password to their assigned default password, "myPassword".

Two files to watch out for after a future upgrade.

program files (x86)\Lansweeper\website\web.confg
program files (x86)\Lansweeper\service\lansweeperservice.exe.config

Both contain unames and pwords for sql communication.