When attempting to configure a device in Scout, the system may display the message "This object has been locked by another Scout Manager. Reload configuration?"

This happens when a lock state remains in the SQL database, usually caused by an interrupted session or corrupted entry. Because the lock persists in the dbo.device table, Scout blocks any further configuration attempts.

A stale or corrupted lock entry in the SQL database causes Scout to think another manager is still editing the device. This prevents configuration changes until the entry is removed.

• Connect to the SQL database used by Scout
• Open the dbo.device table
• Locate the affected device by name or MAC address
• Delete the entire row for that device
• Refresh the device list in Scout Console
• Re-onboard the device so Scout can recreate the entry withouth the lock

The error appears when Scout believes a device is locked by another manager due to a stale or conflicting database entry.
This prevents configuration changes until the lock is cleared.

Be cautious when modifying SQL tables, as incorrect changes can affect other devices or Scout operations.
Always ensure a database backup exists before deleting entries.
After deletion, the device must be re-onboarded to restore configuration access.