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? 

[Thibo · Accepted solution]

Hi, thank you for your patience.

We would like to inform you that Lansweeper v12.5.2.3 addresses the incorrectly shown scanning error regarding the missing SNMP OID. 

If not done already, you can update to the latest Lansweeper version by following the steps in this guide: https://www.lansweeper.com/knowledgebase/updating-your-installation/ 

The latest Lansweeper installer can be found here: https://www.lansweeper.com/update-lansweeper/ 

Our apologies for any inconvenience this may have caused.

[Mister_Nobody]

Have anybody tested 12.5.2.3 for this bug?

[blackmoonwolf]

I can confirm that the update fixed it.

Though I hesitate to trust the platform now because that was such an egregious problem that there is NO WAY that they wouldn't have caught it during any testing prior to the release of that version.

So they CLEARLY didn't do any testing before they released it. There is NO WAY they wouldn't have seen this.

In any case... It took me time to get it all set up again but I imported my database from SQL and had to tackle a few issues but got it all sorted.

[Thibo]

Hello there! Earlier today, I posted information in this discussion thread about Lansweeper version 12.5.2.3, which addresses the issue related to the SNMP error. I’ve updated my response to make it more visible to other community members. Thank you for your understanding!

[Mister_Nobody]

Thousands of devices (voip phones, cameras) have broken lastseen status with this OID error.

But most of them don't have SNMP.

[FrankSc]

Hi, 

This is indeed an incorrect message. It is displayed when no value was found for a specific OID, while the actual scan is ok. We are looking into this and hope to handle this soon in a next release.

[blackmoonwolf]

Hey... We REALLY need you to update us here.

We REALLY need you guys to figure out what wrong thing you did and ROLL IT BACK.

Getting more aggravated by the day here.

[Mister_Nobody]

Any news?

[blackmoonwolf]

Thanks for the reply. I had more data that I tried to post here over the weekend but, for whatever reason, the site wasn't taking my replies. It was, instead, deleting them.

When I return home this evening, I can try to post that info here again. Not sure if it will yield any valuable info or not. It was detailing the new SQL query that I had to run to grant permissions to the `lansweeperdb` user `lansweeperuser`. That was the only thing that I could think of that caused the issue as it was the only real change that I made.

More to come later. But, for now, I would advise that this had major brand impact for your company as I wasted most of my weekend on trying to fix it and, after using LS for like 5 years, I finally started to look for suitable alternatives. (Of which there don't really seem to be many... "Runzero" looked decent, though. Especially because it's server component can run on Linux... *HINT HINT*.)