Date: 10-3-2015 15:27:18
System.ArgumentNullException: Value cannot be null.
- Exchange 2013 - Mailbox Database Copy Performance;
- Exchange 2013 - Organization Performance;
- Exchange 2013 - All Performance;
- Exchange 2013 - IIS Application Pool Performance;
- Exchange 2013 - Windows Service Performance;
- Exchange 2013 - Server Storage Performance;
- Exchange 2013 - Server Mail Process SMTP Performance;
- Exchange 2013 - Server Mail Process Performance;
- Exchange 2013 - Server CPU and Memory Performance.
This one took me a long time to crack. I contacted my fellow MVPs in order to see they experience the same issues. But all of them had no issues what so ever with these Reports. For them these Reports run just fine.
Since this customer had a brand new Exchange Server 2013 environment I first thought the cause could be found there. Perhaps certain Groups, required by these Reports were still empty, causing these Reports to fail.
But the more I thought about it, the less viable it seemed to be the case. Also the Exchange administrators showed me everything is in place and running smoothly. So back to SCOM it was.
And suddenly it hit me. Could it be that the regional settings on the SCOM Management Servers were at play here? When Reports aren’t programmed that good, they can’t handle it because the decimal symbol, digit grouping symbols and short/long date are different, causing the Reports to fail with all kinds of exotic errors…
Time to check it out in my own test environment since I could repro this issue there as well.
As you can see, here in the Netherlands (and many other European countries for that matter) use a comma as decimal symbol and a dot as a digital grouping symbol, exact the opposite as the US does…
This causes the decimal symbol to become a dot and the digit grouping symbol to become a comma.
Tadaa!!!! I tested all the Reports which failed on me before this modification and ALL those Reports run fine now! Awesome!!!
When you’ve got many of the Exchange Server 2013 Reports failing on you with the error Cannot initialize report. Value cannot be null. Parameter name: GroupList, please check the Regional Settings on ALL your SCOM Management Servers.
Modify them to English (United States) and changes are those Reports will run as intended.
It’s common practice to have your production servers set to English (United States) unless there are strict issues preventing that.