I am running a x86 discovery script on the x64 agent (C:\Windows\syswow64\cscript.exe) - have to do it as I need to use third-party DLLs that are only available in x86. I managed to define my own discovery probe and it is starting the script fine, load third party dlls..., however when I try to load MOM.ScriptAPI it fails. Apparently it can not find 32-bit version of MOM.ScriptAPI on a x64 SCOM Agent. Is there a solution for that? Is there 32-bit version of MOM.ScriptAPI on x64 agent under a different name? If not what is the solution for running 32 bit discovery on 64-bit agents? Sounds like a huge limitation! Thx, David

What is the exact error you receive when arriving at MOM.ScriptAPI? Is that 0x8004005? R.E.M. - YEAH!

Here is the output - I don't think it is 0x8004005 - shows -7ff5fe53 - but then it's a javascript probably misinterpreted most significat bit as a sign... the message is "Automation server can't create object".. if I run the same script as x64 (C:\Windows\system32\cscript.exe) then it is a reverse: loads MOM.ScriptAPI fine, but fails to load xyz.Params whcih is in 32 bit DLL. ------------------------------------------------------------------------------------------------------------------ The process started at 2:47:32 PM failed to create System.Discovery.Data. Errors found in output: SourceId {4AC532AA-2A0A-1917-C1FD-20D1DDC80EC5} ManagedEntityId: {C816BB7D-E349-6090-A285-B0D8E3789578} Host: OZVMWIN701.XYZ.COM Port: 13000 UseSSL: true Loading xyz.Params object ... Loading xyz.Proxy object ... Connecting to OZVMWIN701.XYZ.COM:13000 ... Server Version: 524290 Loading MOM.ScriptAPI ... Error: -7ff5fe53 : Error : Automation server can't create object Command executed: "C:\Windows\syswow64\cscript.exe" /nologo "DiscoverServer.js" {4AC532AA-2A0A-1917-C1FD-20D1DDC80EC5} {C816BB7D-E349-6090-A285-B0D8E3789578} syswow64 OZVMWIN701.XYZ.COM 13000 true Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\925\ One or more workflows were affected by this. Workflow name: xyz.Discovery.Servers.x64 Instance name: OZVMWIN701.XYZ.COM Instance ID: {C816BB7D-E349-6090-A285-B0D8E3789578} Management group: xyz