IBM Support

IBM Content Navigator: Troubleshooting tips for IBM Docs Integration plug-in

Product Documentation


Abstract

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

Content

Symptoms and Solutions

TasksSymptomsSolutions
Menu selectionIn 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 Docs action, verify that the user has permission to edit for 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 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 actionYour 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 actionYour 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 actionThe application server where IBM Docs is installed returns a server error.
  • Verify that IBM Docs is configured with the correct URL for IBM CMIS for FileNet Content Manager.
  • Verify that the server where IBM CMIS is installed and the IBM 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 sessionOther 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 documentConflict warnings are not displayed. You might overwrite changes made during a previous IBM Docs collaborative editing session, where the document was checked out using IBM Docs, and you are checking in the document 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 ConnectionsIn a 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-inIBM Content Navigator returns an error message stating 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 Symphony or Open Office that was released before the mime type was approved in the OASIS 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 Symphony or Open Office, and if the mapping isn't automatically updated, you can manually update the mapping. Then, open IBM Symphony or Open Office, 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-inIBM Content Navigator returns an error message stating 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 you don't have Microsoft Office installed on your workstation.
  • You are adding an open standard document template file, but you don't have IBM Symphony or OpenOffice installed on your workstation.
Install the appropriate software on your workstation.

[{"Product":{"code":"SSEUEX","label":"IBM Content Navigator"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"2.0.3","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg27045448