Evaluate and resolve SharePoint add-in test results
- Former user (Deleted)
- Lorenzo Manfredini
- Almuth Boehme [Communardo]
Successful run of the installation test
After a successful run of the installation test, it should look like this:
Checking connection to Confluence
If there is an error like "404 not found" and Confluence version is below 5.10 then an upgrade to Confluence 5.10+ could help.
Another reason can be Confluence is not accessed via its base URL. This could happen if the base URL at the time the SharePoint Add-in was downloaded from the confluence was different from the current base URL.
Checking login to Confluence
Action needed
Click on the login button and do a login into Confluence
Error
This means getting the login state for Confluence failed, could be a network issue with the current page being served from the cache instead of from the upstream Confluence server.
Checking registration of custom action
An error means there was either no registration of the SharePoint add-in or the communication with the app web failed.
Regarding registration of the application see also the last section of SharePoint: Deploy Add-in package to the App Catalog requiring to register the app with the correct Client ID, Confluence host, and provider URL.
Reasons for failing communication with the app web can be:
Missing DNS entry for app web host name pointing to the SharePoint farm - see DNS part of Preparing the SharePoint Add-in Infrastructure
Certificate not accepted by browser, e.g. missing in the certificate of the SharePoint farm - see HTTPS part of Preparing the SharePoint Add-in Infrastructure
Checking assets library and loader file
The same reasons as above can apply.
Related Articles