"Object reference not set to an instance of an object." I've seen some instances where people had this message come up on the website in NPM, but what does it indicate when you see it in UnDP?
Are you seeing it in the app on the server? I'd imagine it's pulling up either an orphaned assignment, or orphaned poller. I'd look at but the custompollers and custompollerassignment tables to see if there are assignments in that table for a poller that doesn't exist. There is also a Universal Device Poller log on the server you can check that should be in the install path.
Thanks for the reply. I'm not sure, since when I rebooted the server to work on a different issue this problem appears to have fixed itself. But it was in the app on the server. It only came up when I assigned it to certain devices (including ones it had previously been assigned to without problems).
Not sure if this is related, but I'm having trouble getting a web display for the custom pollers upsBasicBatteryTimeOnBattery (1.3.6.1.4.1.318.1.1.1.2.1.2) and upsBasicOutputStatus (1.3.6.1.4.1.318.1.1.1.4.1.1). The only option for them is to show up as gauges and when you assign those, the resource on the webpage thinks either no pollers were assigned or no input's been received.
If you customize the page, add the resource Universal Device Poller Status. This will list out all pollers assigned to the node, the latest polled value, and the last time it was polled. Does this show any data?
