Exchange 2010, khi: failed to execute Troubleshoot-DatabaseSpace.ps1 Error formatting a string: Format string is not supported RRS feed

  • Question

  • 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.


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

All replies

  • 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


    • Edited by ChelseaMike Friday, February 1, 2013 4:56 PM
    Friday, February 1, 2013 3:37 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.

    Alex Zhao
    TechNet Community Support

    Monday, February 4, 2013 9:07 AM
  • Hello Alex,

    What do you mean "Before the newer MP release"?
    I am getting this problem with Exchange 2010 SP2. The MP version is 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.


    Thursday, February 7, 2013 6:03 AM
  • I'm also getting these alerts. Running Exchange 2010 Sp2 RU5 with the latest MP ( 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.



    Monday, February 11, 2013 1:12 PM
  • Anyone, anyone at all?
    Thursday, July 25, 2013 6:38 AM
  • 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.


    Thursday, July 25, 2013 6:56 AM
  • Any solutions to this? Can it be escalated?
    Thursday, July 25, 2013 7:16 AM
  • I'm on Exchange 2010 RU2 and experiencing the same issue with the Exchange MP version


    • Edited by Stephen T. Leuthold Monday, September 30, 2013 9:00 PM
    • Proposed as answer by Equinox32 Tuesday, October 1, 2013 3:09 AM
    • Unproposed as answer by Equinox32 Tuesday, October 1, 2013 3:09 AM
    Monday, September 30, 2013 8:59 PM
  •  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
    Tuesday, July 15, 2014 2:06 PM
  • That's a great explanation and seem to be my problem.  What is the solution that Microsoft gave you? 
    Friday, October 24, 2014 12:15 PM
  • I have the same problem and i´m 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.
    Tuesday, November 25, 2014 12:14 PM
  • They asked us to uninstall PS 3.0, we said no and pushed, but they are still processing our case on their side (quite a while already). The funny thing is, that their management pack is clearly different from the one on the web page. They have the following string added when calling powershell which fixes the problem in their code:

    -version 2.0

    But the one on MS web page doesn't have this

    Sunday, November 30, 2014 9:43 AM
  • Version of the Exchange 2010 MP released a few days ago helps when PS 3.0 and PS 2.0 are installed side by side. There is no need to uninstall PS 3.0.

    Read the MP guide for more information.

    Suraj Guptha

    Friday, December 12, 2014 5:59 AM
  • Yes, this has been released due to us pushing on embedding this fix in the Management Pack
    Thursday, April 2, 2015 10:22 AM
  • Our's is till not fixed for PS 4.0, till 3.0 it was fine.. so we implemented below workaround & are working with MS for permanent fix.


    Sukhija Vikas http://msexchange.me

    Saturday, January 23, 2016 4:21 PM
  • Sukhija,

    Did they ever get you a resolution running this script via SCOM with PS 4.0 installed?


    Wednesday, February 10, 2016 1:22 PM
  • Still working with Microsoft Support

    Sukhija Vikas http://msexchange.me

    Thursday, February 11, 2016 4:15 AM
  • Did you ever get a resolution from Microsoft Support?

    I recently deployed SCOM 2012 R2 and i'm seeing the same behavior.

    The storage system we use requires powershell 4.0 is installed on the exchange servers.

    Friday, September 2, 2016 2:58 PM
  • No solution..

    Sukhija Vikas http://msexchange.me

    Friday, September 2, 2016 3:34 PM
  • Any update on this one already?
    Monday, September 12, 2016 7:32 AM