Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr MP Update: SQL MP version 6.3.173.1 ships

OpsMgr MP Update: SQL MP version 6.3.173.1 ships

  • Comments 10
  • Likes

 

This MP is not showing up on the MP Catalog just yet, however the MP catalog does take you to the latest version of the MP.

Get it at:  http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=10631

 

This is a simple update, per the guide it only fixes a bug in the SQL DB file free space monitors.  Previously in 6.3.173.0, this monitor would create a lot of alert noise in specific databases even when free space was not really an issue.

Comments
  • Thank Kevin. One of my customer has this exact problem.

    Interestingly though when I imported it OpsMgr said that I already had these MP's however I was running 6.3.173.0

  • The documentation is also incorrect. The Free disk space change is noted in the "Revision History" but the section called "Changes in This Update" is stating the changes in the previous version.

    By the way, any news around the Exchange 2010 MP? The Exchange team is ignoring any questions and comments and we are still without a working Exchange 2010 MP. Because the old version that was working (although with a bit more load on the Ops enviroment) is not available anymore. Companies that didn't download that version of the MP can't monitor their brand new installation :(

    Link to Exch Team MP post: blogs.technet.com/.../mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

  • A six month wait for a one line code change, i dont get it.

  • The new Exchange 2010 SP2 (fixed) MP should be available next week (03.09. - 07.09). Rumours says, that this MP is not for use as an update - you have to delete your old one and import the fixed version ... :(

  • This still hasnt fixed our issue.. :Module was unable to convert parameter to a double " keeps showing up!

  • I am having the same issues as Divyadeep on this one.  Any suggestions on how to fix it?

  • I'm having the same "Module was unable to convert parameter to a double value" issue as well. Not sure what could be the issue. Any thoughts? Anyone?

  • It's been serveral months now, and no word what so ever about the "unable to convert to double" error that so many people are having.

    Please, give us some update!

  • We found that after updating the MP, the errors were intermittent and were related to WMI Leaks.

    blogs.technet.com/.../wmi-leaks-memory-on-server-2008-r2-monitored-agents.aspx

  • I'm getting allot of alerts due to a collection rule.. any idea why?

    Module was unable to convert parameter to a double value

    Original parameter: '$Data/Property[@Name='FreeSpaceAutoGrowMB']$'

    Parameter after $Data replacement: ''

    Error: 0x80020005

    Details: Type mismatch.

    One or more workflows were affected by this.

    Workflow name: Microsoft.SQLServer.2008.DBLogFile.FileAllocatedSpaceLeftMB.Collection

    Instance name: mastlog

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs