Answered by:
OpsMgr 2012 - SQL MP - Unable to converrt parameter to double value

Question
-
Hello,
after upgrading OpsMgr to 2012 I am receiving the following error on 6 SQL servers for all databases:
Module was unable to convert parameter to a double value
Original
parameter: '$Data/Property[@Name='FreeSpaceAutoGrowPercent']$'
Parameter
after $Data replacement: ''
Error: 0x80020005
Details: Type mismatch.The MP is version 6.3.173.0. All the servers are setup for English (United States) as system locale and it onl yhappens for this specific rule.
It happens on databases were autogrow is set so a percentage value is available.
I hope someone has a solution for this. I am familiar with the problem on the old DHCP MP but never encountered it on SQL before.
Thank you
S.
Monday, May 21, 2012 10:13 PM
Answers
-
Hi,
we updated all SCOM Management Groups we have at the end of last week to CU1 and after that these error messages did not reappear. I guess this is another issue solved by RU1.
Regards
Sascha
- Marked as answer by Graham Davies Tuesday, May 29, 2012 6:17 PM
Monday, May 28, 2012 9:14 AM
All replies
-
Hi,
Please check the issue referring to the following post which may be about a similar issue:
SQL Server 2005 6.3.173.0 returning 0 for DB File Group Free Space
http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/d28af6d7-f2ca-4595-b8d7-553e24aa67f1Thanks.
Nicholas Li
TechNet Community Support
- Edited by Nicholas Li Wednesday, May 23, 2012 9:41 AM
Wednesday, May 23, 2012 9:40 AM -
Hi,
thank you. I will give this a try. I missed that thread.
Regards
Wednesday, May 23, 2012 9:42 AM -
Hello,
no luck with that one. The drive letters where correct for those databases.
However it seems one of our Management Group does not produce the messages anymore after the update to RU1.
Regards
- Proposed as answer by Nicholas Li Monday, May 28, 2012 5:35 AM
Wednesday, May 23, 2012 1:20 PM -
Hi,May I know how the issue is going? Do you mean the issue didn’t occur on a sever applied SCOM 2012 UR1? If so, please also try it on other servers:
OpsMgr 2012: Cumulative Update Rollup 1 (UR1) ships–and my experience installing it
http://blogs.technet.com/b/kevinholman/archive/2012/05/08/opsmgr-2012-cumulative-update-release-1-ur1-ships-and-my-experience-installing-it.aspxThanks.
Nicholas Li
TechNet Community Support
- Edited by Nicholas Li Monday, May 28, 2012 6:57 AM
Monday, May 28, 2012 5:38 AM -
Hi,
we updated all SCOM Management Groups we have at the end of last week to CU1 and after that these error messages did not reappear. I guess this is another issue solved by RU1.
Regards
Sascha
- Marked as answer by Graham Davies Tuesday, May 29, 2012 6:17 PM
Monday, May 28, 2012 9:14 AM