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 all metrics in the SharePoint Server monitor, follow the steps based on the data collection mode:
- WMI mode: Use the Self Help tools or the troubleshooting bat file to verify if data is being collected properly. Refer to this KB for detailed instructions.
- PowerShell mode: Run the PowerShell scripts manually to check if they return data. Refer to this KB for more information.
Error: "Unable to collect data ------- Reason: Timeout exceeded during script execution"
This typically occurs in the SharePoint Server monitor configured in PowerShell mode, when the script to be executed or the individual command takes too long to be executed.
To troubleshoot this error, use the following Measure-Command to determine how much time the script or command is taking to run:
Syntax:
Measure-Command{ <script-or-command> }
Example - Full Script:
Measure-Command{ .\SPMaster.ps1 'hostname' 'username' 'password' 'WebApplication,TimerJobs,ContentDB,SharepointServices' 'CredSSP' }
Example - Individual Command:
Measure-Command{ Invoke-Command -Session $session -ScriptBlock{ Get-SPServiceInstance } }
Upon receiving the results:
- Note the total execution time.
- Go to the SharePoint Server monitor settings in Applications Manager.
- Adjust the Polling Interval and Timeout value to allow sufficient time.
Error: "Unable to collect data for SharePoint Service / Web Applications / Databases / Timer Jobs"
This error indicates that data collection failed for specific SharePoint metrics.
Refer to the steps mentioned in this KB to run the individual data collection script or execute specific PowerShell commands to verify data availability.
Error: "Unable to create remote PowerShell session":
This error usually occurs when a remote session to the SharePoint Server cannot be established.
- Ensure all the prerequisites are met.
- Refer to this KB for the verification steps and the scripts to run for collecting metrics affected by this issue.
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: "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 ...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 ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...