Hello,
I am working with a customer to use the MAP toolkit to collection and SQL Server Instance and Database Details in their environment. At present we are testing the MAP toolkit against one server that has seven instances installed on it. One instance is 64bit and the others are 32bit. All instances get discovered; however, the database details are only collected for the 64bit instance. All of the other instances are marked as failed. We ran MAP again with the tracing turned on and the only errors for the six instances that failed appear to be WMI namespace errors showing up repeatedly (see below). This is just one example, but these invalid namespace errors are all over the log.
How can we resolve these errors?
Does MAP support collecting database details from 32bit instances?
<2015-02-17 13:59:05.77
WorkerThread1@WmiClassesCollectionStep,T1> ConnectToNamespaceAccessTest(Device(GUID={f787ea32-08d0-46ad-a910-3e270005b61c},DnsHostName='HOSTNAME')) - Trying to connect to the WMI namespace 'root\Microsoft\SqlServer\ComputerManagement12' while impersonating
the user 'USERACCOUNT'.
<2015-02-17 13:59:05.77
WorkerThread1@WmiClassesCollectionStep,T1> ConnectToNamespaceAccessTest(Device(GUID={f787ea32-08d0-46ad-a910-3e270005b61c},DnsHostName='HOSTNAME')) - Caught ManagementException connecting to the WMI namespace 'root\Microsoft\SqlServer\ComputerManagement12'.
Exception: System.Management.ManagementException: Invalid namespace
| at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
| at System.Management.ManagementScope.InitializeGuts(Object o)
| at System.Management.ManagementScope.Initialize()
| at Microsoft.AssessmentPlatform.InventoryEngine.DeviceInventory.WmiClassesCollectionStep.ConnectToNamespaceAccessTest(WmiCollectionState stateRec, WindowsIdentity identity, SavedImpersonationContext sic, String wmiNamespace)