-
标题
Test Not Complete Disk Space. WMI connection failed on server <ServerName> , because The ne -
说明
You will see a error similar to this in the Details of the not completed Test.
WMI connection failed on server <ServerName> , because The network path was not found.Verify that WMI is enabled on the server and the user account used for test execution has sufficient rights on <ServerName>. Refer to the Troubleshooting section in the Exchange Deployment Guide for more information about using Windows API instead of WMI.Failed to retrieve disk space values using WMI. Disk space statistics are not available.WMI connection failed on server <ServerName> (Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))). Name space is \\ServerName\root\cimv2<file:///\\ServerName\root\cimv2>. -
原因
This can be caused by permissions or can also be caused by running the test using alternate credentials.
-
解决办法
Make sure that the remote registry Service is started on the target Exchange server and the service account is in the local administrators group. If that is not the issue run the test below.
To test how Spotlight checks the Disk Space in the Health tests follow the steps below.
1. Click Start | Run type in Wbemtest and click OK
2. Click Connect
3. For the NameSpace Section put in \\ServerName\root\cimv2 (the ServerName is the server the health test is failing on, then Click the Connect button.
4. Click Query and put in Select * from Win32_Volume and then click on Apply
5. Double click one of the Win32_Volume objects that show up in the Query Results
6. Scroll down in the Properties window and double click on the FreeSpace property and if you can view that it is not a permission issue.Note:
If your using alternate credentials for your test you can resolve this error using the Windows API for the test
1. Edit the test with the error and on the left hand side select the version/s of Exchange you are using.
2. You will see what looks like a link above the Help button Click "Data collection Options".
3. In the Data Collection Options box on the volumes tab click the drop down and select "Allow fall back to Windows API if WMI fails"