Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

0x8000007D6 results

I'm sporadically getting getting unexpected error occured. Unexpected result code was returned - 0x8000007D6 in a lot of my monitors. Does any one know the root cause of these and/or a method to correct?

I am often able to clear them by doing a test all on the nodes application monitor but that obviously isnt a long term solution.

Thanks

Find more posts tagged with

0x8000007d6

apm

Accepted answers

adeimel

several different answers. The easiest is the error means you are getting a negative value returned. If you do a remote perfmon from your APM box to the counter in question you should see the counter flatline at times. The cause of this can be congestion or any number of things, in my case switch over subscription was I believe the root cause. You may see more of this if your planning on adding a bunch of monitors, I was getting it somewhat randomly with no real pattern to which monitor it would hit.

Dev has added this result in 4.2 to a list of error conditions to ignore so upgrading should rid you of it causing a down status / alert. The root issue would of course still be there so you may still have inaccurate data if you ever need to mine into it.

If you are NOT on 4.2 and won't be for some time support can help you add this error code to your config to correct your issue.

All comments

lukas.belza

Hi adeimel,

Returned error code 0x800007D6 means "A counter with a negative denominator value was detected."

Could you check if it's only one type of performance counter causing this error or there are more perf. counters with this error?

Thank you,

Lukas Belza (SolarWinds development)

adeimel

i get both single instances of this within a greater group of perfmon counters in a template or an entire group of perfmon counters in a template.

I see this in IIS, Windows, and SQL counters across a bunch of different servers at i believe random times of the day. I'll attempt to see if there is a larger pattern I'm missing

adeimel

one interesting thing to note.

After 24 hours or so of operation i get numerous instances of conhost.exe and CounterFetcher.exe left running.

I'm guessing they are orphans are the number appears to grow over time.

adeimel

opened case # 253990

MarieB

adeimel--

Please post back with the resolution you get from Support.

Thx,