Engine Fails to Start

Metastorm

The information in this article applies to:

Product: Metastorm BPM (e-Work)
Version: 6.x 7.x

Issue

• When the Engine service is trying to start, the following messages may be generated, either as pop-ups or in the Windows application event log:

  1. The e-Work 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.
     OR
     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.

  2. Could not start the e-Work Engine service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.
     OR
     Could not start the Metastorm Process Engine service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.

  3. SQL Server does not exist or access denied.

  4. Unable to open table while doing initialisation. Table name: eActiveEngine.
     Additional info: Source=Microsoft OLE DB Provider for SQL Server -
     Error=Invalid object name 'eActiveEngine'..

  5. Unable to open table while doing initialisation. Table name: eServer.
     Additional info: Source=Microsoft OLE DB Provider for SQL Server -
     Error=Invalid column name 'eEventHandlerFunction'..

  6. e-work Engine experienced catastrophic failure.

  7. Cannot open database connection - \#0: Error: (0x80004005) \[Microsoft\]\[ODBC Driver Manager\] Data source name not found and no default driver specified.

  8. Cannot open database connection - \#0: Error: (0x80004005) Cannot generate SSPI context

  9. Cannot open database connection - Provider cannot be found. It may not be properly installed.

  10. Error 1075: The dependency service does not exist or has been marked for deletion.

  11. Unable to open table while doing initialisation. Table name: eActiveEngine. Additional info: Source=OraOLEDB - Error=ORA-00942: table or view does not exist.

Resolution

• Check the following and correct if necessary (review all of the items first to see if one is specific for your error):

  1. If \#1 above (pop-up) and \#6 above (Windows application event log) are seen, set the following registry value to zero (0) so that precompilation of JScript.NET scripts is turned off:
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\JScriptPrecompileLevel.
     This should not be necessary in Metastorm BPM version 7.0.1 and later.

  2. If the installation has been upgraded to a newer version or a hotfix has been installed, run the new stored procedures against the database. These can be found at :\\Program Files\\Metastorm e-Work\\Engine\\Database
     OR
     :\\Program Files\\Metastorm BPM\\Engine\\Database
     For SQL Server, run eWorkProcedures.sql.
     For Oracle, run eWorkTypes.sql, eWorkPackage.sql, and eWorkProcedures.sql in that order.
     See the Installation Guide for more details.
     NOTE: If 6.6.4.6 is installed and Oracle is used, run the 3 Oracle scripts even though the Release Notes state otherwise.

  3. Verify that the Engine's database user login as specified in the DSN and registry is the owner of the Metastorm BPM (e-Work) tables in the Metastorm BPM (e-Work) database.

  4. Verify the following database connection details in the registry:
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database
     AND
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors

  5. For version 7.6, verify the following database connection details in the registry:
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\Oracle DBC\\Connection
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\Oracle DBC\\DotNetConnection
     OR (depending on DB used)
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\SQL Server DBC\\Connection
     HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\SQL Server DBC\\DotNetConnection

  6. Verify that the Metastorm (e-Work) system DSN exists, has the correct connection data that matches what is in the registry, and tests without error. If the DSN already existed, delete it (even though Test Connection works), and recreate it.

  7. For \#9 above, verify that the SQL Server 2005 native client is not being used for the ODBC DSN as it is not supported. Use the SQL Server ODBC driver that is installed with MDAC 2.8 SP1 or SP2.

  8. Error \#10 above may occur if Metastorm BPM is uninstalled and reinstalled without rebooting the server in between. Uninstall Metastorm BPM , reboot, install Metastorm BPM as specified in the Installation Guide.

  9. For \#11 above, verify that the table exists and the Engine can access the table. Verify the DSN and the database registry entries (see above.) Verify that the Oracle database is using the supported character sets specified in the Supported Environments guide.

  10. If Oracle is used, verify that the correct OLEDB and ODBC drivers are being used.

  11. If Oracle is used, configure the tnsnames.ora file to read the Metastorm service first so that it is cached in ODBC, then add the other service names.

  12. Run the file Register.bat located here: :\\Program Files\\Metastorm BPM\\Engine .

  13. See /awd/forums/questions/3402346 for additional information that may apply.