
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2019 04:12 PM
Hi, I'm having trouble understanding why some (but not all) of my installs are failing and returning "No such key AgentKey". I am using flags like so:
LsAgent-windows.exe --server xxx --port xxx --agentkey xxx --mode unattended
This works fine on some machines: they return no errors, the agent installs, and shortly thereafter they report back to the server. Others seem like the key is invalid. I'm using the exact same command and key, issued in the exact same way. What is going on here?
LsAgent-windows.exe --server xxx --port xxx --agentkey xxx --mode unattended
This works fine on some machines: they return no errors, the agent installs, and shortly thereafter they report back to the server. Others seem like the key is invalid. I'm using the exact same command and key, issued in the exact same way. What is going on here?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2020 08:46 PM
I assume you already have LsAgent installed on these problem client machines and are trying to update the installations. We've had a few customer reports of LsAgent configuration files (LsAgent.ini) somehow becoming corrupt and subsequently causing issues while updating LsAgent. Our suspicion at the moment is that affected customers' LsAgent.ini files are being modified by an anti-virus scanner or something similar, though we haven't confirmed this.
Fully removing LsAgent from the client machine and then reinstalling it should fix the issue. Also note that it should ordinarily not be necessary to manually update LsAgent installations on Windows computers. LsAgent auto-updates on Windows. (On Linux and Mac, you do need to manually update.)
Fully removing LsAgent from the client machine and then reinstalling it should fix the issue. Also note that it should ordinarily not be necessary to manually update LsAgent installations on Windows computers. LsAgent auto-updates on Windows. (On Linux and Mac, you do need to manually update.)
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2020 08:46 PM
I assume you already have LsAgent installed on these problem client machines and are trying to update the installations. We've had a few customer reports of LsAgent configuration files (LsAgent.ini) somehow becoming corrupt and subsequently causing issues while updating LsAgent. Our suspicion at the moment is that affected customers' LsAgent.ini files are being modified by an anti-virus scanner or something similar, though we haven't confirmed this.
Fully removing LsAgent from the client machine and then reinstalling it should fix the issue. Also note that it should ordinarily not be necessary to manually update LsAgent installations on Windows computers. LsAgent auto-updates on Windows. (On Linux and Mac, you do need to manually update.)
Fully removing LsAgent from the client machine and then reinstalling it should fix the issue. Also note that it should ordinarily not be necessary to manually update LsAgent installations on Windows computers. LsAgent auto-updates on Windows. (On Linux and Mac, you do need to manually update.)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-11-2019 02:18 PM
Are these devices able to communicate out to the cloud relay? I'm wondering if the installer performs a check against the cloud relay to verify your key is actually valid.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-07-2021 10:42 PM
RKCar wrote:
Are these devices able to communicate out to the cloud relay? I'm wondering if the installer performs a check against the cloud relay to verify your key is actually valid.
It can't - I know this has been resolved, but added notation - the LSAgent.ini file just has [default] in the file, not any other info like a regular LSAgent.ini file; so no, it does not communicate with the cloud because there is nothing in the ini file telling it to.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2019 09:35 PM
I'm getting the same thing on my computer, "no such key AgentKey"
