Resolve common issues for SharePoint On-Prem
Overview of common issues when setting up connection with SharePoint On-Prem
Site settings
In the past we've seen cases where not all sites are correctly returned by the Search API because of the following reasons:
- The search crawler is not enabled
To enable this, you can go to the search application management UI and click ‘content sources’. Then proceed by clicking ‘start all crawls’ to ensure all sites are indexed.
- Sharepoint's root folder Structure
The structure of your Sharepoint is set up to have one ‘root’ site and the rest are all subsites: if the sites you want to sync are subsites of the ‘root’ or ‘home’ site, please verify that the service account has adequate permissions to list/search subsites of the root site
=> Access test in Sharepoint to test service user's access to sites:
To see if the search actually works as expected, you could do a search through the UI whilst logged in with the service account. This can be done by creating a site collection that is specifically aimed at enabling searching through your Sharepoint content, also known as a ‘Search Center’.
Service user assigned to folders and not sites
Lexis® Create DMS will read from the top down, so it needs to be ensure that Lexis® Create DMS has access from the top down. Access can be further restricted, but Lexis® Create DMS needs to start reading at the "site" level. Once Henchman starts reading at the Site level, we will see which drives within the site we can read, then folders etc.
❗It is therefore not possible to only give the service user access to a single folder as the integration will start reading from the "site level.
Service user has insufficient rights
In case users are managed with Azure, they can connect using our OAuth 2.0 app.
The integration will then automatically ask for the ‘Sites.Read.All’ permission. If the service user is added as a Guest account in Sharepoint, this might not be available and this needs to be manually changed for the service user.
This setting can be found in Azure by navigating to ‘Enterprise Applications’, then opening the ‘Henchman’ Application & finally selecting the ‘permissions’ tab in the left navigation bar.
See below marked in red what needs to be enabled:
-png.png?width=688&height=160&name=Screenshot%202023-05-16%20at%2017-09-40%20(1)-png.png)