A Collector Server instance does not start

Edit online

At start, a Collector Server instance checks whether all settings are correct and whether it established a connection to the system where the repository is installed. In addition, all paths and files that are specified in the instance configuration must be accessible.

To determine why a Collector Server instance does not start, proceed as follows:
  • Check whether the Collector Server administrator can access all relevant paths and files and has the necessary permissions for these paths. Check whether the PATH environment variable contains the installation path to the repositories that are used. In addition, check whether the fully qualified paths are specified, where necessary.
  • Make sure that the Collector Server port is not used by another program. If it is used by another program, change its value in the instance configuration.
    Where to find the information:
    • Configuration Feature Basic Configuration > Communication > Ports > Collector Server port
    • Server configuration profile ARCHPRO_PORT keyword
  • Enable tracing in the instance configuration. In Configuration Feature, take these steps:
    1. Open the instance configuration that you want to change.
    2. Go to Basic Configuration > Logging and Tracing.
    3. In the Messages section, select the Console output check box.
    4. In the Tracing section, select Dynamic from the Tracing list.
    In a server configuration profile, you find the following specifications:
    Section in server configuration profile Keyword UI field that supplies the value
    Global section REPORT The selection of the Console output check box results in the value YES.
    TRACE The selection of the Dynamic results in the value DYNAMIC_ON.
  • IBM Content ManagerContent Manager OnDemandFileNet P8 Make sure that your repository contains only documents that have all the attributes, database fields, or properties that Content Collector for SAP needs:
    • IBM Content Manager If some or all of the documents lack certain required attributes, such as DocId or DocProtection, change the instance configuration. In Configuration Feature, take these steps in Extended settings view:
      1. Open the instance configuration that you want to change.
      2. Go to Logical Archives > Logical Archive IBM Content Manager id > General.
      3. Select the following check box: Logical archive is read-only. Use SAP Document Finder to view the documents.
      In a server configuration profile, you find the following specification:
      Section in server configuration profile Keyword UI field that supplies the value
      Global section ARCHIVETYPE The selection of the check box results in the value GENERIC_MULTIPART.

      The Collector Server instance then starts without checking whether all required attributes exist.

    • Content Manager OnDemand If some or all of the documents lack certain required database fields, such as DocId or DocProtection, change the instance configuration. In Configuration Feature, take these steps in Extended settings view:
      1. Open the instance configuration that you want to change.
      2. Go to Logical Archives > Content Manager OnDemand id > General.
      3. Select the following check box: Logical archive is read-only. Use SAP Document Finder to view the documents.
      In a server configuration profile, you find the following specification:
      Section in server configuration profile Keyword UI field that supplies the value
      Global section ARCHIVETYPE The selection of the check box results in the value GENERIC.

      The Collector Server instance then starts without checking whether all required database fields exist.

    • FileNet P8 Check whether the document classes that you specified in the instance configuration have the necessary system properties. If system properties are missing, add them. If you cannot add the system properties, delete the affected document classes from the instance configuration.
  • Look for error messages in the Collector Server start trace file and in the Collector Server trace file (default name: archint.trace).
  • Determine which child process has problems with the connection. The archpro program normally displays an error message.

    The same error message is also in the trace file. If you cannot find out which component failed, check each component separately. Enable only one agent at a time.