Troubleshoot Utility 1：UCP无法获取Managed Instance的Resouce Utility data --未解决
当Enroll一个Instance之后，1hour过后，发现该 Managed instance 的health status 仍然处于 No Data Available 状态，why？
1，手动 collect 和 upload 数据到UCP
链接到Managed Instance，点击Utility information，点击Collect and Upload Now，数据上传成功，但是，在UCP中，该Instance的health status 仍然处于 No Data Available 状态。
2，由于Utility Information 是使用Agent 来收集数据的，打开 sysutility_mi_collect_and_upload Job查看history
Step2 出错，错误消息是：Executed as user: NT Service\SQLSERVERAGENT. Internal error: A job step could not successfully pipe a script to PowerShell
3，Remove 这个Instance后，在Validate到配置WMI时，出现Warning
Waning 消息是：
WMI must be configured correctly. Validation completed with a warning. WMI on the target instance is not configured properly for it to report data back to the UCP. Verify that the following classes are available on the machine and are accessible to SQL Server Agent service account:
Win32_MountPoint
Win32_PerfRawData_PerfProc_Process
Win32_PerfRawData_PerfOS_Processor
Win32_Processor
Win32_Volume
Win32_LogicalDisk
For example, issue the PowerShell command 'Get-WmiObject Win32_PerfRawData_PerfProc_Process' on the target machine to verify that the Win32_PerfRawData_PerfProc_Process class is accessible. If the SQL Server Agent Service account recieves an Access Denied error, then the account may need to be added to the "Performance Monitor Users" group. For more information, see the Help topic for this operation.
这是错误的根源，参考资料：Access permission issue when uploading data to the utility warehouse ，我有没有解决这个问题。
参考MSDN ： Troubleshoot the SQL Server Utility
Failed WMI Validation
If WMI is not properly configured on an instance of SQL Server, the Create UCP and Enroll Managed Instance operations display a warning, but the operation is not blocked. Additionally, if you change the SQL Server Agent account configuration so that SQL Server Agent does not have permission to required WMI classes, data collection on the affected managed instance of SQL Server fails to upload to the UCP. This results in gray icons in the UCP.
Failed data collection results in gray status icons in the UCP list view for affected managed instances of SQL Server. The job history on the managed instance of SQL Server shows that sysutility_mi_collect_and_upload fails on step 2 (Stage Data Collected from PowerShell Script).
这段描述确实跟我遇到的情况相同，是Step2出错。
To resolve this issue, verify the following configuration settings:
-
On Windows Server 2003, the SQL Server Agent service must be part of the Windows Performance Monitoring group on the managed instance of SQL Server.
-
The WMI service must be enabled and configured on the managed instance of SQL Server.
-
The WMI repository might be corrupt on the managed instance of SQL Server.
-
The performance library might be missing or corrupt on the managed instance of SQL Server.
To verify that the specified instance of SQL Server is configured properly to report data to the UCP, verify that the following classes are available on the specified instance of SQL Server, and that they are accessible to SQL Server Agent service account:
-
Win32_MountPoint
-
Win32_PerfRawData_PerfProc_Process
-
Win32_PerfRawData_PerfOS_Processor
-
Win32_Processor
-
Win32_Volume
-
Win32_LogicalDisk
You can use the Get-WmiObject PowerShell cmdlet on each of the classes to verify that each class is accessible. Run the following cmdlets on the managed instance of SQL Server:
Get-WmiObject Win32_MountPoint -ErrorAction Stop | Out-Null Get-WmiObject Win32_PerfRawData_PerfProc_Process -ErrorAction Stop| Out-Null Get-WmiObject Win32_PerfRawData_PerfOS_Processor -ErrorAction Stop | Out-Null Get-WmiObject Win32_Processor -ErrorAction Stop | Out-Null Get-WmiObject Win32_Volume -ErrorAction Stop | Out-Null Get-WmiObject Win32_LogicalDisk -ErrorAction Stop | Out-Null
For more information about troubleshooting WMI, see Troubleshooting WMI. Note that queries in these SQL Server Utility operations are running locally, so the DCOM and remote troubleshooting content does not apply.
本人对WMI一窍不通，后续search...
推荐文档：
Troubleshoot the SQL Server Utility