Hi,
Exchange 2010 MP fails to run Troubleshoot-DatabaseSpace.ps1. Results in a Warning with "Error formatting a string: Format string is not supported". The EventNumber is 402. The Microsoft article it points to is useless at http://technet.microsoft.com/en-us/library/749e0eac-ebb2-41e3-8fa2-4a03a1bd3571.aspx 

Run ".\Troubleshoot-DatabaseSpace.ps1 -Server MailboxServer.domain.com -MonitoringContext" and works fine.

Any help appreciated.

thanks

• Edited by MDS Support Friday, February 01, 2013 2:59 AM

Got exactly the same problem. Seems to have started since applying RU4 to our Exchange 2010 SP2 servers

As stated above, running the troubleshooter manually on the server is abolutely fine

However, after it has finished, nothing is logged to the event log.

If I execute in verbose mode, I can see that it is generating output. However, this isn't being written to the event log when you run it normally.

I don't know whether this is related to the underlying SCOM issue above

Incidentally, I upgraded my SCOM 2012 last week to SCOM 2012 SP1 in the hope that it may resolve the problem. No joy!

It's driving me nuts so I'd appreciate any assistance

Cheer

• Edited by ChelseaMike Friday, February 01, 2013 4:56 PM

Hi,

Before the newer MP release, we can disable  these 4 monitor via override and this should not run the Troubleshoot-DatabaseSpace.ps1 :

KHI: Failed to execute Troubleshoot-DatabaseSpace.ps1.

KHI: The database copy is low on database volume space and continues to grow. The volume is under 25% free

KHI: The database copy is low on database volume space and continues to grow. The volume has reached error levels under 16% free.

KHI: The database copy is low on database volume space and continues to grow. The volume has reached critical levels 8% free.

Hello Alex,



What do you mean "Before the newer MP release"?
I am getting this problem with Exchange 2010 SP2. The MP version is 14.3.38.4 which I understand is the latest. 
So if you are suggesting I'm working with an older Management Pack and I can simply disable these, that is not correct.

My Database Copy alerts are working fine. I've had them warn me about a DAG log space problem and the alert is correct.



regards

I'm also getting these alerts. Running Exchange 2010 Sp2 RU5 with the latest MP (14.3.38.4). Running the command on the servers don't seem to indicate a problem. I'd rather not override the alert if it is possible to fix the problem.

Any tips would be appreciated.

Thanks

Anyone, anyone at all?

I'm still getting the error as well, even after upgrading to Exchange 2010 SP3. I can only assume that MS aren't interested in fixing problems with the SCOM MPs.

Any solutions to this? Can it be escalated?

I'm on Exchange 2010 RU2 and experiencing the same issue with the Exchange MP version

 After troubleshooting this with MS engineers we found out the reason for this - it happens when you have Windows Management Framework 3.0 installed on the server and thus you're running Powershell v3.0. When you open Exchange Management shell it will run PS v2.0 and the command will execute just fine, but if you just click on the Powershell button next to start menu and add PSsnapins for Exchange 2010 it will run PS v3.0 and the command will fail to execute. You can verify the version of Powershell run by calling $Host.Version in your PS/EMS window. The reason for this is, that whenever the script is ran by SCOM it will call PS from "NT AUTHORITY\SYSTEM" context which will run the latest version of PS available while Exchange Management Shell is always calling version 2.0

• Edited by Dariusz Nowara Tuesday, July 15, 2014 2:16 PM

That's a great explanation and seem to be my problem.  What is the solution that Microsoft gave you? 

I have the same problem and im also very interested in a solution. Or at least a confirmation that you can override the "Format string is not supported" errors and still have the Exchange MP working correctly.