Perhaps this contributed to this and/or caused this problem? I updated to v12.5.1.1 yesterday. I immediately started to get these errors afterward:
The lansweeperuser account that is used to connect to the lansweeperdb instance doesn't have the 'dbcreator' role. In the unlikely case that a rollback is needed during the auto-update process, the service won't be able to rollback the database automatically, unless you grant the 'dbcreator' role to lansweeperdbuser.
The lansweeperuser account that is used to connect to the lansweeperdb instance doesn't have the 'View server state' permission. We will most likely not be able to perform the calculation for the database space requirement accurately in the auto update checks, unless you grant the 'View server state' permission to lansweeperdbuser.
To fix that issue, I found this solution and implemented it in my SQL database:
/* Grant lansweeperuser dbcreator and view server state
to be able to sync your database */
USE master;
GO
EXEC sp_addsrvrolemember [lansweeperuser], [dbcreator];
GO
GRANT VIEW SERVER STATE TO [lansweeperuser];
GO
MS SQL Server Management Studio reported that the above was successful. Those two errors disappeared.
But, now, most assets are giving the OID error. (Though, otherwise, I have discovered that they are still logging "Successful" scans. I'm not sure what the value of that is, however.)
This update really threw a wrench in the works.