Troubleshooting - Document Composition - Foundation 24.1 - Foundation 24.1 - Ready - OnBase - external - OnBase/Document-Composition/Foundation-24.1/Document-Composition/Installation/Troubleshooting - 2024-03-25

Document Composition
Platform
OnBase
Product
Document Composition
Release
Foundation 24.1
License
  1. I successfully installed Document Composition, but the Template Builder tab is not displayed when I launch Word.
    Enable and load the Document Composition add-in:
    1. In Word, click the Office button.
    2. Select Add-ins.
    3. Select Disabled Items from the Manage drop-down list.
    4. Click Go.
    5. If the Document Composition add-in is included in the Disabled Items dialog box, select it and click Enable.
    6. The Document Composition add-in is enabled.
    7. Select Add-ins.
    8. Select COM Add-ins from the Manage drop-down list.
    9. Click Go.
    10. Select the check box next to the Document Composition add-in in the COM Add-Ins dialog box, and click OK.
    11. The Document Composition add-in is loaded.
  2. The Diagnostics Console displays a message stating, “System.IO.IsolatedStorage.IsolatedStorageException: Unable to open the store.”
    This issue can occur when attempting to create a document using a large template (i.e., hundreds of pages), or if a template creates a large document. It is caused by an issue in the .NET Framework. To resolve this issue, enable Impersonation on the Application Server. If Enterprise Document Composition is being used, the Composition Service should be configured to run as a user instead of as SYSTEM.
  3. How do I modify the service location I specified during Template Builder installation?
    Edit Hyland.Office[year].DocumentComposition.Config.dll.config. In a typical MSI installation, this file is located in C:\Program Files\Hyland\Office Integration\Office [year] (32-bit operating systems) or C:\Program Files(x86)\Hyland\Office Integration\Office [year] (64-bit operating systems).
  4. When composing a document and storing it as a PDF or TIFF, some Word features (for example, art page borders) are not displayed on the composed document.
    Document Composition does not support the use of all Word features when composed documents are stored as PDF or TIFF. If Word features are not displayed on composed documents being stored as a PDF or TIFF, store the composed document as a Word document (.docx).
  5. How do I resolve the “There was an error in gathering Field Information selected Field” error, which occurs when upgrading a database that is licensed for Document Composition and WorkView?
    Upgrade the OnBase database, install and run WorkView Configuration, and install Document Composition.
  6. When configuring a new template with a Metadata Placeholder, the Document Type and Keyword Type drop-down lists on the Placeholder Input screen are both empty.
    This occurs because of the fact that WorkView attributes can be used as Placeholders. If the WorkView database tables are not present in the database, none of the Document Types or Keyword Types will display unless the WorkView tables have been created in the OnBase database. To resolve this issue, install and run WorkView Configuration to create the WorkView tables in the OnBase database. After creating the WorkView tables, close and re-open Microsoft Word, and then re-launch the Template Builder.
  7. When composing a PDF or TIFF document using a Document Composition template, tables within the document overlap surrounding tables, images, and/or text.

    This issue may be a result of one or more tables in the template using the Around text wrapping table property. To change this, open the template in the Template Builder and right-click the appropriate table. Select Table Properties and select the None property for Text Wrapping. Do this for each overlapping table.

    You can also try adjusting the spacing in between the tables to solve the issue if you do not want to change the table properties.

  8. When using the AscW VBScript function, negative values are returned when asking for the Unicode value of a non-Latin character. This negative number is then composed onto a document at runtime rather than the desired Unicode character.
    Microsoft has acknowledged this is a known issue. For more information on how to work around this issue, refer to Microsoft KB article 272138 (http://support.microsoft.com/kb/272138/en).
  9. When using C/WScript to run VBScripts, an error message is displayed.
    This issue occurs if the script file is UTF-8 encoded. UTF-8 encoded script files are not supported when using C/WScript to run VBScripts. When using C/Scripts to run VBScripts, UTF-16 encoded script files must be used.
  10. When opening a template, the following message is displayed: "This template contains a VBScript that may reference the DMCoreX API. If it does, the script will no longer function. Please contact your first line of support for more information."
    This occurs when the opened template contains a VB Script, and the system determines the VB Script may be using the DMCoreX API. The DMCoreX API has been deprecated. Therefore, VB Scripts using this API no longer run during document composition. This does not affect whether a document is successfully composed. For more information on VB Scripts using the DMCoreX API, contact your first line of support.
  11. When changing Windows display settings, Template Builder dialog boxes are only partially displayed.
    After changing Windows display settings, you must sign out of Windows and sign back in for the changes to take affect in the Template Builder.