Using the CSI Diagnostics Tool to Test Confluence and SharePoint Connectivity (v 1.9)

If you are having trouble connecting to SharePoint from Confluence or to Confluence from SharePoint, you may want to perform some diagnostics to see what the problem is. Attached is a tool called 'CSI Diagnostics' which you can use to test the web services used to connect from SharePoint to Confluence and vice-versa.The CSI Diagnostics Tool must be run on a Windows computer with the .NET Framework 2.0 installed.

  1. Download the attached zip file.
  2. Unzip it.
  3. Run CSIDiagnostics.exe.

Below are guidelines the options that the tool provides.

On this page:

Testing SharePoint's Ability to Connect to Confluence

For the most realistic diagnosis, run this tool on your SharePoint server when trying to diagnose Confluence connectivity.

Screenshot: Testing Confluence connectivity

Use the 'Confluence Connectivity' tab to test connectivity issues when SharePoint cannot connect to Confluence.

For example, use this tab when you encounter problems on the following SharePoint pages:

The 'Test Confluence Settings' button uses the helper API built into the SharePoint feature to test the settings to Confluence. To run this test you must be running this tool on the SharePoint server with the SharePoint Connector features installed.

Testing Confluence's Ability to Connect to SharePoint

For the most realistic diagnosis, run this tool on your Confluence server when trying to diagnose SharePoint connectivity. If your Confluence server is not running on a Windows operating system, then run this tool on any Windows computer in your network that is 'close' (with regards to network hardware) to your Confluence Server.

Screenshot: Testing SharePoint connectivity

Use the 'SharePoint Connectivity' tab to test connectivity issues when Confluence cannot connect to SharePoint.

For example, use this tab when you encounter problems on the following Confluence pages:

This tool is not the best at diagnosing problems with SharePoint connectivity because the tool uses .NET libraries (web service proxies) to communicate to SharePoint whereas the plugin uses Java libraries. For that reason, you may find that the tool can communicate with SharePoint but the plugin still has problems.