Legacy SharePoint Connector

The Legacy SharePoint Connector has been renamed. In earlier versions, the app was called "SharePoint Connector for Confluence."

Limitations and Known Issues

Use this page to troubleshoot any problems you may have with the Legacy SharePoint Connector. For instructions on installation, configuration and usage, please consult the documentation for the Legacy SharePoint Connector.

Search Knowledge Base articles:


On this page:

Prerequisites

Full list of requirements: For more information on each of the above points, please refer to the complete list of requirements in the Legacy SharePoint Connector Installation Guide.

Diagnostic Tools

  • Tracing: To troubleshoot or debug the SharePoint feature you can enable tracing and then view the trace with a tool such as DebugView. See Tracing the SharePoint Feature.
  • Logging: In addition to enabling the tracing feature, critical errors and warning messages are always output to the SharePoint Log. You can view this information by Analyzing the SharePoint Logs.
  • Checking the Confluence configuration: When the Legacy SharePoint Connector configuration is set up properly it just works. However when it does not work it can be tricky to diagnose the problem, given the two different platforms trying to authenticate, authorise, and communicate across different servers. Here are some things to check on the Confluence side:  Troubleshooting the SharePoint Configuration in Confluence.

Limitations

  • Integrated Windows Authentication (IWA): IWA, including LM, NTLM, NTLMv2 and Kerberos, requires complex configuration and may cause problems. See the documentation on Planning your Authentication Configuration. This documentation and configuration process is under review. We are working on a simplified procedure as well as simplified documentation.
  • SharePoint Forms-based Authentication: The Legacy SharePoint Connector  is not able to connect to SharePoint sites that use the Forms authentication module.
  • Crowd: The Legacy SP connector does not support Atlassian Crowd for SSO, when using a Crowd internal directory.
    • Crowd internal directory requires Microsoft SSO: If your Confluence instance uses a Crowd internal directory for user management, you must use the Microsoft SSO service. This means that you must have SharePoint MOSS, because SharePoint WSS does not provide Microsoft SSO.
    • Crowd LDAP does not require Microsoft SSO: If your Confluence users come from Active Directory via Crowd, there is no need for Microsoft SSO because the Confluence user credentials and the SharePoint user credentials are the same.
  • Clicking a link in the Confluence Page web part opens the Confluence page in a new browser window: It would be nice if you could click a link and have the new page open within the web part itself. We are tracking this popular feature request as CSI-196.
  • Some Confluence macros do not work in the Confluence Page web part: Any Confluence macro that performs an Ajax web call will not work in the Confluence Page web part. These are macros that perform a second call do load the macro display data independently of the page. Examples as the Recently Updated macro and the JIRA Issues macro (CSI-423). The problem is caused by security restrictions, because the Ajax call comes from the SharePoint page rather than Confluence.
  • Including private pages from a public page will result in an error message: It is possible in a Confluence wiki page to include the content of another page using the {include} macro. If a page that is generally available (Page A) includes the content of a page that is not generally available (Page B), this works as expected within Confluence as well as within the 'Confluence Page' web part in SharePoint. When a user authorised to see Page B views Page A, they see the content of Page A and the content of Page B. If the user is not authorised to see Page B, they see the content of Page A and an error similar to this: "Unable to render {include} Couldn't find a page to include called: Page B".
  • When using sharePoint list macro in Confluence to render a custom SharePoint view of a SharePoint document library: if the custom view of document library in SharePoint does not include the column with name "Name (linked to document with edit menu)" the layout of list macro in Confluence is broken. It's required that all custom views of document library in SharePoint have to include the column "Name (linked to document with edit menu)" in its view.

Frequently Asked Questions

Requesting Support

If you have a problem, please take a look at the prerequisites, diagnostic tools, limitations and known issues described above.

If you do not find a solution to your problem, please help us to troubleshoot the issue by providing the following information before submitting a support request on the Service Center:

  1. Find the base URL of your Confluence server. To see your base URL, open Confluence in your web browser, log in as a Confluence administrator and visit http://<Your Confluence URL>/admin/viewgeneralconfig.action.
  2. Tell us which browser you are using when the problem occurs, and which version of the browser such as Firefox 3.6.2 or Internet Explorer 8.0.
  3. Tell us which operating system you are using when the problem occurs, such as Windows Vista, Windows XP, Linux, Mac OS X.
  4. Capture a Fiddler report for tracking read-only issues.
  5. Run Confluence's generic error page by visiting http://<Your Confluence URL>/500page.jsp and give us the result for review. Please copy the whole page including the list of enabled plugins.
  6. Include your Confluence logs and a copy of the information on your Confluence 'System Information' page. To get this information, go to 'Confluence Admin', 'System Information' and copy the text from the page. We need that information to see what Confluence version and which application server you are using.
  7. Let us know what you are using for Confluence user management: Confluence internal user management, LDAP (Active Directory), Crowd internal directories, Crowd LDAP, JIRA user management, or any other user management scenario.
  8. Tell us whether you have MOSS or WSS installed.
    To determine whether you have WSS 3.0 or MOSS 2007 installed, go to Windows Start -> Control Panel -> Add/Remove Programs.
    • If you see 'Microsoft Office SharePoint Server 2007' in the list, then MOSS 2007 has been installed.
    • If you see only 'Microsoft Windows SharePoint Services' in the list (and not 'Microsoft Office SharePoint Server 2007') then you only have WSS 3.0 installed.
  9. Ask your SharePoint administrator which SharePoint service packs you have installed.
  10. Find out which version of the Legacy SharePoint Connector you have installed in SharePoint. To find this out, go to the 'Confluence Administrative Settings' page in SharePoint.
    • Go to the top level site within the site collection.
    • Select 'Site Actions' (at the top-right) -> 'Site Settings' -> 'Modify All Site Settings'.
    • On the 'Site Settings' page, choose 'Confluence Settings'.
    • On the 'Confluence Administrative Settings' page, copy the value for the 'Legacy Connector Version' (in the section labelled 'Confluence Site').

Want to know more about the Legacy SharePoint Connector?

Find the documentation here: Legacy SharePoint Connector