Intermittent Connection Failure

Wren

Hello, I have only just installed SQL monitor in our place so I am still learning it. I have just set up a number of machines each with a number of instances on it, but one particular is giving me some problems.

The connection is intermittent with the following error...
Bad Data InvalidDataException column procc.cpu has negative value, but negative values are not allowed.

I am not sure where this data is, has anybody else has this message before? I am monitoring one other instance on the same machine and this is ticking over with no errors. I am monitoring SQL 2005 R2 RTM.

Thank you in advance for any help.
Regards,
W.

Brian Donahue

Hello,

No doubt your performance counters on one of the SQL Servers have bad data in them, as you can't have "negative" CPU usage. I have no idea what could have caused this - maybe it's some virtual machine issue?

You can try going to the SQL Server computer and rebuilding the default Windows counters using LODCTR.exe /R.

Wren

Hello Brian,

I tried the lodctr.exe /r which said it ran successfully, but it is still disconnecting, I now have an error that says alot of the perfmon data is missing objects, namely all the SQL ones. How can I get these back?

Regards,
W.

Brian Donahue

To rebuild SQL performance counters, use lodctr.exe with the performance counter ini files shipped in SQL Server. Here are some instructions for doing that: http://blogs.msdn.com/b/john_daskalakis ... 93110.aspx

Wren

Hello Brian,

Just to help others I thought I'd finish off the thread, this did solve my issue, but I did not have to go the extra step to replace the SQL counters, the server had to be restarted (for other reasons) and the SQL counters got re-registered automatically as a result of the restart. SQL Monitor is now connected and monitoring the instance nicely.

Thank you for your help.

Regards,
W.

Brian Donahue

Wonderful! I'm happy to have helped.

Brahim22

This error message definitely sounds frustrating, especially since you're new to SQL Monitor and it's only happening on one specific instance. Here's what's going on:

• The Error: SQL Monitor is encountering an invalid data point. The "procc.cpu" column, which likely represents processor usage, has a negative value, and SQL Monitor doesn't expect negative CPU usage.

• Possible Causes: There are a couple of things that could cause this:

  • Bug in Monitoring Script: It's possible there's a bug in the way SQL Monitor is collecting data for this specific instance.
  • SQL Server Issue: On the less likely side, there might be a weird issue with how SQL Server itself is reporting CPU usage for this particular instance.

• What to Do: Here are some steps to troubleshoot:

  1. Check the Script: Look into the specific monitoring script or configuration for this instance in SQL Monitor. See if there's anything related to CPU data collection that might be causing the issue.

  2. Compare with Working Instance: Since another instance on the same machine works fine, compare the monitoring setups for both instances. This might help identify any configuration differences that could be causing the problem.

  3. Search Online Resources: Search for the specific error message ("Bad Data InvalidDataException column procc.cpu has negative value") related to SQL Monitor and SQL Server 2005. You might find similar cases and solutions from other users.

  4. Contact SQL Monitor Support: If nothing else works, consider contacting SQL Monitor's support team directly. They might have specific insights into troubleshooting this error within their software.

Hopefully, by following these steps, you can identify the culprit behind the negative CPU value and get your SQL Monitor running smoothly for all your instances! visit https://nsapp.download/