I upgraded our Deployment Share yesterday to MDT 2012 (version 6.0.2223.0) and was looking forward to checking out the Monitoring Features and DART integration.
Just came to enable the monitoring however and I get an error whenever I try to look at the monitoring node; "object reference not set to an instance of an object". Clicking more details gives me the error message below.
Checked the MDT Monitoring Service and whilst it's set to Auto it will not start whatever I do. Get the error about it not responding in a timely fashion.
Any ideas?
------------ ERROR from Monitoring Node --------------
Assembly: mscorlib Assembly Version: 2.0.0.0 File Version: 2.0.50727.4216 (VistaSP2GDR.050727-4200)
Assembly: Microsoft.ManagementConsole Assembly Version: 3.0.0.0 File Version: 6.0.6002.18005
Assembly: System Assembly Version: 2.0.0.0 File Version: 2.0.50727.4220 (VistaSP2GDR.050727-4200)
Assembly: MMCFxCommon Assembly Version: 3.0.0.0 File Version: 6.0.6002.18005
Assembly: System.Configuration Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: System.Xml Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: System.Windows.Forms Assembly Version: 2.0.0.0 File Version: 2.0.50727.4214 (VistaSP2GDR.050727-4200)
Assembly: System.Drawing Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: Microsoft.BDD.Workbench Assembly Version: 3.0.0.0 File Version: 6.0.2223.0
Assembly: Microsoft.BDD.PSSnapIn Assembly Version: 3.0.0.0 File Version: 6.0.2223.0
Assembly: System.Management.Automation Assembly Version: 1.0.0.0 File Version: 6.0.6002.18111
Assembly: Microsoft.BDD.Core Assembly Version: 3.0.0.0 File Version: 6.0.2223.0
Assembly: System.Management Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: System.DirectoryServices Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: System.Data Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: Microsoft.PowerShell.Commands.Diagnostics Assembly Version: 1.0.0.0 File Version: 6.1.7600.16385
Assembly: System.Core Assembly Version: 3.5.0.0 File Version: 3.5.30729.1 built by: SP
Assembly: System.Configuration.Install Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: Microsoft.WSMan.Management Assembly Version: 1.0.0.0 File Version: 6.0.6002.18111
Assembly: System.Transactions Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: Microsoft.PowerShell.Commands.Utility Assembly Version: 1.0.0.0 File Version: 6.0.6002.18111
Assembly: Microsoft.PowerShell.ConsoleHost Assembly Version: 1.0.0.0 File Version: 6.0.6002.18111
Assembly: Microsoft.PowerShell.Commands.Management Assembly Version: 1.0.0.0 File Version: 6.0.6002.18111
Assembly: System.ServiceProcess Assembly Version: 2.0.0.0 File Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
Assembly: Microsoft.PowerShell.Security Assembly Version: 1.0.0.0 File Version: 6.0.6002.18111
Assembly: System.Data.Services.Client Assembly Version: 3.5.0.0 File Version: 3.5.30729.196 built by: QFE
Assembly: MMCEx Assembly Version: 3.0.0.0 File Version: 6.0.6002.18005
System.InvalidOperationException: Object reference not set to an instance of an object.
at Microsoft.BDD.Workbench.Utility.RunPSCommand(String commandString, Dictionary`2 parameters)
at Microsoft.BDD.Workbench.MonitoringListView.Refresh()