Unlinking from Lansweeper Sites stuck after migrating Lansweeper

[apiknowbler]

Summary

Description

After migrating Lansweeper, the old server cannot unlink from Lansweeper Sites. This issue persists despite service restarts.

Cause

The Lansweeper installation has two scanning servers (Configuration > Your Lansweeper License), which may be an unintended configuration. The unlinking process fails because the system does not recognize the new server name due to the old server's lingering presence. Additionally, the LsAgent Relay service may interfere with the renaming script, causing server name conflicts in the database.

Solution

• Execute the SQL statement at the bottom of the following KB article to rename the old server to the new name: https://community.lansweeper.com/t5/lansweeper-maintenance/move-your-lansweeper-installation-to-a-di...
• Restart the following services:
  • Lansweeper Server
  • Web service (can be either IIS Express or World Wide Web Publishing Service)
• Confirm that only the new server name is listed on the Configuration > Link with Cloud Site page after the unlinking process is complete.

Additional information

• The SQL statement may return a foreign key error between tblLsAgentRelayConfig and tsysASServers.

Msg 547, Level 16, State 0, Line 1
        The DELETE statement conflicted with the REFERENCE constraint "FK_tblLsAgentRelayConfig_tsysASServers". The conflict occurred in database "lansweeperdb", table "dbo.tblLsAgentRelayConfig", column 'Servername'.

• You can resolve this by navigating to Scanning > Relay Configuration in the Lansweeper web console and temporarily setting the old scanning server as the Relay Synchronization server.
• Then, attempt to rerun the SQL statement.