locked
Module was unable to convert parameter to a double value RRS feed

  • Question

  • Hi, I'm getting the following error on one of our DHCP servers.
    
    Event Type:	Warning
    Event Source:	Health Service Modules
    Event Category:	None
    Event ID:	11052
    Date:		2009-06-15
    Time:		14:37:13
    User:		N/A
    Computer:	DHCP01
    Description:
    
    
    Module was unable to convert parameter to a double value 
    Original parameter: '$Data/Property[@Name='10.32.190.0/InUse']$' 
    Parameter after $Data replacement: '' 
    Error: 0x80020005 
    Details: Type mismatch.
     
    
    One or more workflows were affected by this.  
    
    Workflow name: 
    Microsoft.Windows.DHCPServer.Library.Scope.CollectScopeAddressesInUse 
    Instance name: SE-a-iLo (ASEFILS02) 
    Instance ID: {BE9E1BD1-A32E-71D8-D5DF-8A7E778457B0} 
    Management group: Global-OpsMgr
    
    For more information, see Help and Support Center at 
    http://go.microsoft.com/fwlink/events.asp.
    
    Anyone any the wiser how to resolve this?
    Monday, June 15, 2009 1:47 PM

Answers

  • Hi Patrick,

    The reason you're getting it from the EVA Perf MP is probably because of your regional setting on the machine running evaperf. The decimal symbol should be . and not comma (,)

    Maybe the DHCP MP has the same problem.


    Thanks for reporting it.
    • Marked as answer by StuartR Thursday, August 27, 2009 7:08 PM
    Tuesday, July 7, 2009 8:04 PM

All replies

  • Can you provide a little bit more details about the environmen including the DHCP Server OS type, language and how frequent you are getting this error? Have you made some overrides to any of workflows? Also can you confirm if you have imported the latest version of DHCP MP available here

    http://www.microsoft.com/downloads/details.aspx?FamilyId=2694E87C-76E0-417B-AD0F-5897E46FFF88&displaylang=en&displaylang=en

    Wednesday, June 17, 2009 7:59 PM
  • I have the same problem in my environnement:

    Module was unable to convert parameter to a double value
    Original parameter: '$Data/Property[@Name='10.165.145.0/Free']$'
    Parameter after $Data replacement: ''
    Error: 0x80020005
    Details: Type mismatch.

    DHCP2003ComponentDiscovery.vbs : Error adding superscope data. code = 424

    This is a DHCP running on Windows 2003.

    Thursday, June 25, 2009 2:43 PM
  • Did you delete any of scope/superscope a little before you got this error event? This might happen if you have deleted some scope/superscope and discovery has not worked yet.

    Friday, June 26, 2009 5:53 PM
  • I have found in the documentation that the MP does not support more than 500 scopes. This renders the MP useless for us since we have close to 1000 scopes.
    Tuesday, June 30, 2009 5:04 PM
  • Hi Alan, hi2all!

    That does not match to my environment...

    And: I have this alert from DHCP and your EVA Perf.MP too! ;-)

    eg from EVA Perf.MP:
    Module was unable to convert parameter to a double value Original parameter: '$Data/Property[@Name='Value']$' Parameter after $Data replacement: 'Total Read Hit MB/s' Error: 0x80020005 Details: Type mismatch. One or more workflows were affected by this. Workflow name: EVA.Disk.Group.Read.Miss.Reqs Instance name: Evaperf Instance ID: {5E8A1460-77CE-B2FE-210A-D5F8B344AB98} Management group: ...

    Any idea?

    Thanks in advance,
    Patrick

    Tuesday, July 7, 2009 6:18 AM
  • Hi Patrick,

    The reason you're getting it from the EVA Perf MP is probably because of your regional setting on the machine running evaperf. The decimal symbol should be . and not comma (,)

    Maybe the DHCP MP has the same problem.


    Thanks for reporting it.
    • Marked as answer by StuartR Thursday, August 27, 2009 7:08 PM
    Tuesday, July 7, 2009 8:04 PM
  • Alan,

    from my point of view it seems that all reg.settings are the same.
    I have about 11 SMAs running evaperf and just 3 of them are reporting this error. And data would be collected anyway.

    Edit: do you have an idea how to analyze/troubleshoot this error?

    Patrick
    • Edited by Patrick Seidl Thursday, July 9, 2009 6:07 AM further question
    Thursday, July 9, 2009 6:06 AM
  • Again, can you provide some more information which might help in knowing the exact problem.

    How frequenct you are getting this warning?
    Have you deleted any scope/superscope on any DHCP server which is generating this warning?
    Is the DHCP Service stopped on DHCP Server at the time when you get this warning?

    We have some known issue when it generates the warning if it has some discovered scope object in the database and and it cannot find that object in the DHCP Server which is possible in following 2 cases:
    1. DHCP Service is stopped on DHCP Server
    2. Scope object has been deleted from Server and not undiscovered by SCOM yet.

    But I do not expect this warning event to occur any more when Service is started (if stopped earlier) or scope has been undiscovered from SCOM (If deleted from DHCP Server case).
    Thursday, July 9, 2009 5:57 PM
  • Hi Patrick,

    Please contact me at alain.z.cote at gmail.com and I will help find the problem.
    Thursday, July 9, 2009 9:06 PM
  • I'm sorry but this solution does not fit to my problem as you can see in my next posting!
    But maybe for some other guys of you...

    Regards,
    Patrick
    Friday, August 28, 2009 6:34 AM
  • Hi all,
    have the same problem running DHCP on a MS Cluster. The message is from the cluster node that not running the dhcp-service!!
    What to do?
    Tuesday, October 6, 2009 3:02 PM
  • Current DHCP MP does not support clusters and it has beend documented in the DHCP MP guide.
    Tuesday, October 6, 2009 9:44 PM