Troubleshooting: SCOM reports yield weird data/what the heck does 9.221E+07 mean?

Eventually when running a report in SCOM you are going to end up with a report like the one below.


At first glance everything looks okay. But then you start looking at the data that was returned and it can sometimes be a little confusing.


Usually the questions I get from customers ranges from “I think this report is broken” to “what the heck does 9.221E+07 mean?”

Fear not, reporting is not broken and 9.221E+07 is not nearly as confusing as it may seem. Basically, what is going on is that the dataset you have returned is so large in regards to the number of digits that in order to display it in a meaningful way the system is presenting the data using some shorthand commonly known as scientific notation. All you need to understand is that +07 indicates the number of times the decimal point would need to be moved to the right to display the full number.

So 9.221E+07 = 92210000

And if we look at the top of the chart we will note that the particular performance counter that we are reporting on is being returned in Bytes so we are dealing with:

92210000 Bytes

For those of you who like me are not particularly mathematically inclined and prefer to leave conversions to someone else I recommend using the wonderful built-in functionality of PowerShell.

If you enter 9.221E+07 and hit enter it will automatically output the full value for you:


If the original unit–in this case Bytes–is not your unit of choice and you want to know what the value is in MB  just enter the value in scientific notation form and then divide by 1 MB:

9.221E+07  / 1MB


Same goes for GB

9.221E+07  / 1GB



Troubleshooting: SCOM Web Console 500 – Internal Server Error

This is a problem that I occasionally see crop up in customer environments, but until now I had never bothered to document the issue.


Customer is able to log into the web console successfully but when they click on certain views like the active alerts view they see the following error:


Anytime there is an issue with the web console my first suggestion is to attempt to recreate the problem as localhost on the machine that hosts the webconsole. If the server has the same problem locally you know where to start troubleshooting, if it is only happening on client machines it could be firewall or some problem at the client level.

When we tested from SCOM web console server we get the same error, but this time with a little bit more information:


This may not seem useful, but this is actually telling us exactly where the problem is. Note the Version= in regards to .Net Framework. This is telling what version of the Framework is expected for this particular app pool.

If we navigate to IIS we see the following:


OperationsManagerMonitoringView is set to v.40, but it should be set to v.2.0. We need to edit the Basic Setting and select the drop down with v2.0


After that we need to recycle the Application Pool via the Application Pool task


Then just logout of the webconsole and back in and all will be well.

System Center Technical Preview Released: What’s New in SCOM

For those of you with MSDN accounts System Center Technical Preview is now out.

Technical Preview

I haven’t had a huge amount of time to dig in to see what’s new, but here are a few things that have caught my eye so far with the Preview for SCOM:

Open PowerShell Task

Open PowerShell

What is interesting about this task is that it isn’t simply launching an administrative PowerShell prompt on your local system. It is contextual to whatever server you have selected in the windows computer view and thus takes care of the fun of invoking a remote session for you in a single click.


(I had originally thought this was exclusive to the MP’s in the Technical Preview, but @StanZhelyazkov kindly pointed that this was added in the latest version of the Windows OS MP’s that came out on 8/27/2014:

I was hoping for some new Dashboards, but it looks like for now we have all the same Dashboards from 2012 R2 plus those that were added in UR2. The only change I have noticed so far is that some of the names of the dashboards have been modified.

Contextual Healh renamed

There are some new Management Pack Wizards. The TFS wizard may have already existed I haven’t imported that MP before, but I believe the Unix/Linux Service Monitoring Wizard is new:

Management Pack Wizards

New Monitors: (Two new Unix/Linux Script Monitors)


New Task Option:(Run a UNIX/Linux Script)

New Task


The contents of this site are provided “AS IS” with no warranties, or rights conferred. Example code could harm your environment, and is not intended for production use. Content represents point in time snapshots of information and may no longer be accurate. (I work @ MSFT. Thoughts and opinions are my own.)