Error when opening plugin and/or WUA Versions tab

[chris]

This just started happening this morning, I haven't had this error the past 5 days or so. When opening the plugin and/or accessing the WUA Versions tab, I receive this error:

We hit a WUA error Conversion from type 'DBNull' to type 'Integer' is not valid.

Any ideas?

[chris]

This just started happening this morning, I haven't had this error the past 5 days or so. When opening the plugin and/or accessing the WUA Versions tab, I receive this error:

We hit a WUA error Conversion from type 'DBNull' to type 'Integer' is not valid.

Any ideas?

Well, with time the error has gone away. *shrug*

[Cubert]

Sounds like from the error we got some bad data during a scan that didn't compute when you open the plugin.

As scans replace the data on every sweep I believe it would indeed self heal after the system cleared what ever error it was generating.

[tsuky1]

I also started getting the same error since Wednesday. Unfortunately mine did not clear out and i am still unable to use the plugin as intended.
I was scanning every 4 hours to see if it would clear out and have turned it down to 12 hours for now. I have it enabled on 23% of my clients so i don't think i am overwhelming the system.

[Cubert]

Ok shoot me a screen shot of the error and where it pops up. What do you do to make error happen? and I will take a look and get a fix out. ASAP

[tsuky1]

I just tried it again today and the error is gone. My labtech does lock up for couple of seconds with "not responding" while the plugin loads, but no error. Tried couple of times and its good now. I dropped the scan down to 12 hours from original 4. I only have it on 22% of the clients enabled, so hopefully it will work once i get the rest on-boarded

[chris]

I find that this happens when you delete agents - for example if I'm cleaning up agents that have been offline for a while, etc. The error happens until Patch Remedy does its next scan. Just a thought?

[Cubert]

That is correct, Patch remedy uses its scanner to keep its tables clean. Removing old data when it is not available anymore. But you have to allow scanner to find it which may take a scan or 2 to do.

If scanner is set to 12 hours cycle then it maybe 24 hours or more before you see it clear up.

[tsuky1]

With the latest version 1.0.2.75 I no longer get the error, but now my WUA tab will not populate and on the overview screen the gauge for WUA is at 0.
Started this week and has not cleared itself out. The rest of the tabs look ok and have data in them, but not sure how accurate.

[tsuky1]

Just checked again and now i am running version 1.0.2.78, but still have the same issue with WUA tab.

screen shot

4-19-2016 1-56-27 PM.jpg (201.55 KiB) Viewed 18776 times