Troubleshooting tips for IBM Docs Integration plug-in

When troubleshooting problems with IBM Docs Integration plug-in, use this information for diagnosis and repair.

Symptoms

Table 1. Common problems and solutions
Tasks Symptoms Solutions
Menu selection In IBM Content Navigator, the New Document or Edit in IBM Docs actions don't appear on your desktop.
  • Verify that the IBM Docs add-on is installed on your repository.
  • Verify that the menus and toolbars are configured to include the IBM Docs actions.
  • For the Edit in IBM Docs action, verify that the user has permission to edit the document.
  • For the New Document action, verify that the user has permission to file a document in the selected folder.
Create new document IBM Content Navigator returns an error for the following actions:
  • New Document
  • New Spreadsheet
  • New Presentation
  • Verify that the user has permission to file a document in the selected folder.
  • Verify that the user has permission to create an instance of the Document Class.
  • If you added document templates to the IBM Docs Integration plug-in, verify that the user has read access to the document templates.
Select an IBM Docs action Your browser returns an error, 404: Not found. For the IBM Docs Integration plug-in, verify the value that is specified for the IBM Docs URL. The host name or port might be incorrect.
Select an IBM Docs action Your WebSphere® Application Server returns an error, 404: No context root.
  • For the IBM Docs Integration plug-in, verify the value that is specified for the IBM Docs URL. The path might be incorrect. For example, the docs folder might be missing from the path.
  • Verify that the server where IBM Docs is installed and the IBM Docs application are up and running.
Select an IBM Docs action The application server where IBM Docs is installed returns an error, 404: Not found.
  • Verify that IBM Docs is configured with the correct URL for IBM CMIS for FileNet® Content Manager
  • Verify that the server where IBM ECM CMIS is installed and the IBM ECM CMIS application are up and running.
  • Verify that the user has permission to edit the current document reservation.
Edit a document in IBM Docs and invite other users to join your editing session Other users cannot join your editing session. For the fncs-sitePrefs.properties file, verify that the following property is set to true:

enableSharedDrafts=true.
Edit a document in IBM Docs and save the document Conflict warnings are not displayed. You might overwrite changes from a previous IBM Docs collaborative editing session, where the document was checked out using IBM Docs, and you are checking in the document by using IBM Content Navigator. For the cmis.properties file, verify that the following property is set to false:

filterHiddenProperties=false.
Edit a document in IBM Docs from IBM Connections In an IBM Connections community library with approval enabled, the IBM Docs approval actions don't appear in your IBM Docs editing session.
  • For the cmis.properties file, verify that the following property is set to true:

    enableTeamspaceAwareness=true.

  • Verify that the server where IBM FileNet Collaboration Services is installed and the IBM FileNet Collaboration Services application are up and running.
Select a document template file to add to the IBM Docs Integration plug-in IBM Content Navigator returns an error message that you must specify a valid template file, and the selected document MIME type begins with application/x-vnd.

However, valid MIME types begin with application/vnd.

 This error occurs when you have a version of IBM Lotus Symphony® or Apache OpenOffice that was released before the MIME type was approved in the OASIS Content Management Interoperability Services specification. The characters x-vnd indicate a proposed standard MIME type, and the characters vnd indicate an approved standard MIME type. Your operating system maps the file extension to a MIME type, depending on how your installed applications registered the supported file extensions.

Install a later version of IBM Lotus Symphony or Apache OpenOffice, and if the mapping isn't automatically updated, you can manually update the mapping. Then, open IBMLotus Symphony or Apache OpenOffice, and open and save the document template file so that the file extension maps to a valid MIME type. Now, you can add the document template file to the IBM Docs Integration plug-in.
Select a document template file to add to the IBM Docs Integration plug-in IBM Content Navigator returns an error message that you must specify a valid template file, but no value is displayed for the selected document MIME type. This error occurs in one of the following situations:
  • You are adding a Microsoft Office document template file, but Microsoft Office isn't installed on your workstation.
  • You are adding an open standard document template file, but IBM Lotus Symphony or Apache OpenOffice aren't installed on your workstation.
Install the appropriate software on your workstation.