Troubleshooting and Limitations – Microsoft SharePoint Discovery

This section provides troubleshooting and limitations for Microsoft SharePoint discovery.

1. The credential on which the job connects to the SharePoint host must provide a trusted connection to the SharePoint configuration database. If the database host is the third host (discovered host) and the trusted connection is used for the SharePoint configuration database, such configurations will not be discovered. To avoid this problem SQL credentials must be used in the SharePoint configuration.

   The discovery mechanism works in the following cases:

   • The SharePoint configuration database is connected via named pipes (a farm on a single host)

   • An SQL connection is used for the configuration database

   • A trusted connection is used for the configuration database, and this database is hosted with some other SharePoint components

2. For each SharePoint service, all the configuration details are merged into one string in the service configuration attribute of the SharePoint Service CIT.

3. Problem: The error message No SharePoint library found is displayed.

   Solution A: It is recommended to check the Event Viewer on the SharePoint database machine, to see if there are unsuccessful connection attempts from the SharePoint instance which is being discovered. If there are unsuccessful connection attempts, add a new login to MS SQL Server manager (the one which could not access the database) and grant db_owner permissions for the SharePoint_Config database to this new login.

   Solution B: Select the Run remote commands impersonated check box in the NTCMD Protocol Parameters dialog box.