Unable to fetch the SharePoint Server version
When adding a SharePoint Server monitor in Applications Manager, the SharePoint Server version selected in Applications Manager is validated against the version found on the target server.
If you encounter the error "Unable to fetch the SharePoint Server version" while adding the SharePoint Server monitor, it may be due to one of the following reasons:
- The SharePoint Server application is not running on the target server.
- The target server is not reachable.
- WMI queries cannot be executed to retrieve the SharePoint Server version details.
Follow the steps below to manually verify the SharePoint Server version using the VBScript utilized by the monitor:
- Open Command Prompt in Administrator mode on the Applications Manager-installed machine.
- Navigate to the <Applications Manager Home>\working\conf\application\scripts directory.
- Execute the following command by replacing hostname, username, and password with the credentials of the target server used in the monitor:
cscript wmiget.vbs hostname username password "select Version from Win32_Product where Name like '%Microsoft Sharepoint Server%'" - Check the command output to obtain the SharePoint Server version number.
Use the following reference to identify the SharePoint Server version based on the version number retrieved from the command output:
- SharePoint Server 2016 and 2019: Version number starts with 16 (e.g., 16.x.xxxx.xxxx)
- SharePoint Server 2013: Version number starts with 15 (e.g., 15.x.xxxx.xxxx)
- SharePoint Server 2010: Version number starts with 14 (e.g., 14.x.xxxx.xxxx)
- SharePoint Server 2007: Version number starts with 12 (e.g., 12.x.xxxx.xxxx)
- If an error occurs while executing the above steps, try running the same WMI query directly using the wbemtest tool on the Applications Manager server by connecting to the remote server.
- Refer to the section "Checking connectivity with WMI Tester" for instructions on using the wbemtest tool. If an error occurs, troubleshoot using the same KB.
- If an error persists, troubleshoot using this KB for WMI connection related issues.
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 ...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 ...Monitor Addition: Unable to add MS Office SharePoint monitor
Check if all the prerequisites are done. The prerequisites can be found here: https://www.manageengine.com/products/applications_manager/help/prerequisites-for-applications-manager.html#SharePointServer WMI Mode If unable to add the SharePoint Server ...How can I execute a SharePoint.bat / SharePoint.sh file?
This file is used to check if the connectivity and the Discovery of the Sharepoint Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the Sharepoint 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 ...