Installation and Upgrade Issues

  1. Installation Error Caused by Special Characters in the Hostname
    An installation error can be caused by special characters in the hostname.
  2. Installation Fails to Complete Due to Pending Tasks on BPMNode
    Installation can fail to complete due to pending tasks on the BPMNode. In this situation, some messages are displayed and the installation does not complete.
  3. Installation Failure Due to Missing Database Objects
    The installation process fails if the database objects required by the BPM runtime are not available. This could manifest in a failure to start the Event Collector component.
  4. SQL Recovery Error after Installation
    After installation, the BPM node log files contain errors related to transaction recovery.
  5. Sanitizing After a Failed Installation
    An installation process can fail at various stages and the installer may not be able to clean up the environment before exiting. It is recommended that you clean up the environment manually before trying to re-install the product.
  6. Error When Configuring the ActiveMatrix Administrator Server
    While installing ActiveMatrix BPM, an exception is thrown when configuring the ActiveMatrix Administrator server.
  7. Refreshing a Node when Passing an Array to a Stored Procedure
    The Oracle database node restart is needed when you plan to use a stored procedure which passes an array. This can be done before or after the user application is deployed.
  8. Out of Sync SystemNode after Upgrade
    After upgrading from ActiveMatrix BPM 3.x or 4.x (with any ActiveMatrix 3.3.0 Hotfix installed on top of it), the SystemNode in the SystemEnvironment may be marked as Out of Sync. This is because the WSDL Validator is not correctly upgraded by the upgrade process.
  9. Additional EMS Requirements for Installation and Upgrade
    If your TIBCO ActiveMatrix BPM infrastructure connects to its TIBCO Enterprise Message Service servers with users that do not have administrator privileges, you must create some additional EMS topics and queues that are not described in TIBCO ActiveMatrix BPM Installation and Configuration.
  10. Failures in Linux Version 7 when TIBCO Business Studio uses the SWT Internal Browser
    There are failures in Linux Version 7 (OEL7, CentOS 7, RHEL 7) when TIBCO Business Studio uses the SWT internal browser (used for BPM Live Dev, Email Service Task, TIBCO Product Help view) and an error message is displayed.
  11. Initializers and Migration
    When you add a new ad-hoc activity, and then upgrade and migrate, you must define an initializer for the activity which executes after the migration. This could actually be the migration point itself.
  12. Adding a New BPM Node to an Existing System Fails Because a Resource Instance is Missing or Cannot be Installed