Error: No Data collected in MS Office SharePoint monitor added in Powershell mode
Error: "Unable to create remote PowerShell session" or "No data returned from PowerShell script"
If you face any of the above errors or any other error related to PowerShell Session, follow the below steps to check if you are able to run individual scripts.
1. Verify Prerequisites
If
CredSSP authentication is enabled in the SharePoint monitor, make sure the
CredSSP prerequisites are also met on both the Applications Manager server and the SharePoint server.
2. Run PowerShell Scripts Manually
Open PowerShell in Administrator mode on the machine where Applications Manager is installed.
- Navigate to the <AppManager-Home>\working\conf\application\scripts\powershell directory.
- Execute the appropriate script by replacing hostname, username, and password with the credentials of the SharePoint server as used in Applications Manager. Use CredSSP option if chosen in the monitor.
- Tabular data (SharePoint Service, Web Applications, Databases, Timer Jobs, Share Point Server Services, Web Content Management-Publishing Cache, Office Search Schema Plugin, Office Search Archival Plugin, Office Server Search Indexer Catalogs)
.\SPMaster.ps1 'hostname' 'username' 'password' 'WebApplication,TimerJobs,ContentDB,SharepointServices' 'CredSSP'
- Scalar data (Other performance metrics)

For AppManager version 175900 and above:
.\SPAttributes.ps1 'hostname' 'username' 'password' '<Selected-Services>' '<Version-Number>'
For AppManager versions below 175900:
.\SPAttributes.ps1 'hostname' 'username' 'password' 'WebApplication,TimerJobs,ContentDB,SharepointServices' 'CredSSP'
- Refer to the table below to choose the appropriate Version-Number and their Selected-Services
SharePoint Server Version | Version-Number | Selected-Services |
2019 | 16 | AccessServices, InfoPathServices, VisioWebAccess Services, SearchServices |
2016 | 16 | AccessServices, InfoPathServices, VisioWebAccess Services, SearchServices |
2013 | 15 | AccessServices, InfoPathServices, VisioWebAccess Services, ExcelServices, OfficeSearchGatherer |
2010 | 14 | AccessServices, InfoPathServices, VisioWebAccess Services, ExcelServices, OfficeSearchGatherer |
2007 | 12 | ExcelServices, DocumentConversions, OfficeSearchGatherer
|
- Get the full output and copy it to a text file.
Error: "No data returned from the PowerShell command"
Run the SPMaster.ps1 script mentioned above in step 2 to check if it retrieves data.
If not, refer to this
KB article to execute direct PowerShell commands on the Applications Manager server and validate the output.
Error: "No data available in the WMI class, or the WMI class is unavailable"
- Run the SPAttributes.ps1 script mentioned above in step 2 to check if it retrieves data.
- You can also check the specific metrics using the Self Help Tools and see if the associated WMI class fails.
- You may copy the WMI class name from the Self Help Tools output and verify it using the WBEMTEST tool directly on the SharePoint Server to check if the class exists and data is available.

Still facing issues?
- Screenshots of the completed prerequisites
- Output of the script executions (saved as a text file)
- Self Help Tools output if available
- Screenshot from the WBEMTEST tool if available
- Latest Support Information File (SIF) from Applications Manager with Print all logs enabled and the reported monitor polled.
New to ADSelfService Plus?
Related Articles
MS Office SharePoint Monitor - FAQ
1. What are the ports used in SharePoint Server monitoring? WMI mode: Remote Procedure Call (RPC): Port 135 (default) Dynamic DCOM Ports: WMI uses DCOM for remote communication, which typically involves a random port number above 1024 for the server ...
Troubleshooting Data Collection Issues in SharePoint Service, Web Applications, Databases and Timer Jobs (MS Office SharePoint monitor - PowerShell Mode)
In MS Office SharePoint monitoring, data for SharePoint Services, Web Applications, Databases, and Timer Jobs is collected using PowerShell. If these metrics are missing, follow the steps below to identify and resolve the issue: 1. Verify the ...
Error: Timeout exceeded during script execution - MS Office SharePoint monitor
The "Timeout exceeded during script execution" error usually occurs in the SharePoint Server monitor added in PowerShell mode. Run the below Measure-Command to measure the time taken for the script to be executed or the individual commands to be ...
Data Collection: Troubleshoot data collection issues in MS Office SharePoint monitor
Note: Before troubleshooting, ensure that you have met all the required prerequisites for the SharePoint Server monitor. Troubleshooting no data collected for some or all metrics in the SharePoint Server monitor If no data is collected for some or ...
Error: "No data available in the WMI class, or the WMI class is unavailable" (in MS Office SharePoint Monitor)
This error indicates that the SharePoint monitor is unable to fetch data due to: Missing or inaccessible WMI classes on the target SharePoint server, or Issues with WMI connectivity or permissions. Troubleshooting Steps For Applications Manager ...