cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mfuhrman
Engaged Sweeper
All of the assets that I have in Lansweeper are assigned to a user. I use the relationship of "Used By" and then the AD username. I turned on the option to remove user from Lansweeper database if deleted in AD. I didn't realize it would cause an issue with assets that were assigned to those deleted users.

If I try to edit an asset that was assigned to a deleted user I get a webserver error. I've been trying to figure out where the relationship is stored for the asset in the database but haven't had any luck so far. If I could just somehow clear that relationship for those assets I believe it will work like it should.

I have since unchecked the delete users option to prevent this from happening in the future. I sent an email to support but haven't heard anything back, so I don't even know if they got it.

Anyone have any ideas on how to fix this?
1 ACCEPTED SOLUTION
Bruce_B
Lansweeper Alumni
Version 7.2.107.4 fixes the webserver error, a further fix for the cleanup option will be added in a future release.

  • https://www.lansweeper.com/changelog/
  • https://www.lansweeper.com/knowledgebase/updating-your-installation/


Relations are stored in tblAssetUserRelations. Since you indicate you created a support ticket, you'll likely be able to receive a script to clean-up these orphaned entries.

View solution in original post

2 REPLIES 2
Bruce_B
Lansweeper Alumni
Version 7.2.107.4 fixes the webserver error, a further fix for the cleanup option will be added in a future release.

  • https://www.lansweeper.com/changelog/
  • https://www.lansweeper.com/knowledgebase/updating-your-installation/


Relations are stored in tblAssetUserRelations. Since you indicate you created a support ticket, you'll likely be able to receive a script to clean-up these orphaned entries.
Hi Bruce. Thanks for the info. Updating to the newest version did fix my problem. I'm used to seeing a popup screen when there is an update and haven't seen one in a while, so I assumed I was on the latest version.

Interesting side note. I've never heard back from support.