Engine Fails to Start After Upgrading to Metastorm BPM Version 7.6

Metastorm

The information in this article applies to:

Product: Metastorm BPM
Version: 7.6

Issue

• After running the Metastorm BPM version 7.6 install to upgrade an existing installation, the following errors are encountered when trying to start the Process Engine:

  1. Pop-up message: The Metastorm Process Engine service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

     Windows application event log: The Metastorm Process database has not been updated for this version of the Metastorm Process Engine. Re-run the Metastorm stored procedure script(s).

  2. Pop-up message: The Metastorm Process Engine service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

     Windows application event log: Unable to open table while doing initialisation. Table name: InstanceState. Additional info: Source=Microsoft OLE DB Provider for SQL Server - Error=Invalid object name 'InstanceState'..

Resolution

• \#1 above - install the updated database stored procedures for either Oracle or SQL Server. See the Installation Guide for details.

• \#2 above - for all SQL Server databases run the following SQL scripts in this order:
  SqlPersistenceService\_Schema.sql
  SqlPersistenceService\_Logic.sql

  By default these files can be found in C:\\WINDOWS\\Microsoft.NET\\Framework\\v3.0\\Windows Workflow Foundation\\SQL\\EN\\.

• For SQL Server 2005, run the new SQL script eWorkProcedures2005SpecificEnhancements.sql.