v12.5.1.1 broke SNMP

[blackmoonwolf]

I upgraded to v12.5.1.1. Suddenly, nearly all of my assets are saying:

Scan Incomplete
Object OID could not be retrieved. for OID 1.3.6.1.2.1.1.2.0 

I've been banging my head against the wall for the last FOUR HOURS trying to figure out what to do about it but changing credentials has served no purpose. I can walk SNMP on my systems and get output but Lansweeper is crapping the bed on SNMP.

Oddly, my Juniper network gear is still getting successful scans.

WHAT did you do, Lansweeper folk? 

[blackmoonwolf]

And, now, that post that WOULD NOT show up yesterday...is suddenly HERE at the bottom. It was NOT there earlier today, either.

What is happening with your guys' forums right now? 🤨

[DonMario73]

Hi Frank, can you provide an estimate date to have this fix released?

Thks!

[blackmoonwolf]

Well... So much for that. This all descended into a corrupted installation as I tried to fix the problem. Let's see if a fresh install continues having the same issues - I guess.

[blackmoonwolf]

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.