cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
lunesolitaire
Engaged Sweeper III

Hi,

I found a problematic LsAgent client on a PC in the AD domain, because I haven't had any scan updates for 3 days, and when I checked its file C:\Program Files (x86)\LansweeperAgent\lsagentlog.txt , it said there was an error reading the ini file, and it "restored" something, but if I open the LsAgent.ini file, there are only the characters NUL..
do you know why?

The biggest problem for me is that I don't know if there are many PCs that have this same problem...our LsAgent is installed by SCCM which uses a specific credential (not the one for Lansweeper), and I already knew that if we use a different credential than the installer, we can't completely uninstall and it will leave a directory with 0 rights on it! means needs to be delete manually for a repair installation)

 

Thank you!no scan for 3 days-ini-nul.jpgno scan for 3 days-log.jpg

4 REPLIES 4
Mister_Nobody
Honored Sweeper II

You can try version 12.2.0.1

I will read the doc of 12.2.0.1 , Hopefully this version fixes this and will be able to wipe out the "out of control" folders left behind by the current version during the update process

StillGoing
Champion Sweeper

I'm running into the same issue with a previous version of lsagent (v11.1.10.0), but I'm discovering this on a multitude of devices (probably 300-ish). Either the lsagent.ini file is corrupt or, worse, it AND the lsagentconfiguration.xml file are corrupt. The first can be fixed by deleting it and restarting the service, but it appears the agent HAS to have some readable version of lsagentconfiguration.xml to do anything. My only solution thus far has been to copy a known good copy from another device.

I'm hunting for a solution I can push out to detect and address the issue. Going through them one at a time is not working for me, now that I've determined the scope of the issue. And I'm not encouraged to find that you are having the same problem with the latest version. Time for a support call, I suppose.

I agree with you, it is essential to know how many PCs have this issu, and I hope Lansweeper can give us a method/tool to detect and fix.... Since it is a common probleme for all...