We have a NetApp cDOT I/O sensor that was working fine, then over the weekend started giving the error:

"Value was either too large or too small for an Int32"

Has anyone seen this? Not sure what to do. Opened a support ticket, but no response yet.

Article Comments

Hello Mark,
we appreciate your contact.

It appears that you haven't received our previous reply to case PAExxxxx7 which was sent on 11/01/2016 08:12 UTC+1.

There's a known issue in the current(15.4.21.548x) version of PRTG which affects the NetApp cDOT I/O (SOAP) Sensor, it will be fixed on the next releases of PRTG but there is an hotfix available, which we can provide to customers who contact us via a Support Ticket.

Best Regards,


Jan, 2016 - Permalink

Hi there,

We are running 16.1.21.1422+ and using a NetApp cDOT Aggregate (SOAP) BETA, which seems to have the same issue (Value was either too large or too small for an Int32). I know that it is in BETA, but do you know how long it will be before the type will be bumped up to a int64?

Kind Regards, Niel


Feb, 2016 - Permalink

Hello, thank you for your feedback.

As per our release notes we've just released PRTG Version 16.1.22, this version includes several fixes to the NetApp cDOT SOAP-based sensors, we strongly recommend that you update and re-create the cDOT sensors after the upgrade for best results.

Please don't hesitate to contact us if you encounter any further issues with the cDot sensors in version 16.1.22 or later.


Feb, 2016 - Permalink