LogicBase server extensions fail to start

Products

• Workflow Solution

Issue/Introduction

After a hard computer shutdown or failure of the Workflow server, LogicBase server extensions fail to start after the server is rebooted. Errors such as the following occur in the Windows Event Log:

Our Production workflow machine lost power.  After booting the Logicbase Extensions will start; below is the error we are getting.  Help

Event Type: Error
Event Source: LogicBase 2006 Server Extensions
Event Category: None
Event ID: 0
Description:
Service cannot be started. System.Exception: server extensions did not start ---> System.Exception: could not read in object  ---> LogicBase.Framework.ObjectDeserializationError: could not deserialize: LogicBase.Core.Messaging.AbstractExchangeConfiguration[] ---> System.Exception: exception deserializing array ---> LogicBase.Framework.ValueNotFoundException: value not found: searching type: LogicBase.Core.Messaging.SearchMode
   at LogicBase.Framework.ObjectReadStream.GetValue(String name, Type type)
   at LogicBase.Core.Messaging.AbstractCacheConfiguration.ReadFromStream(ObjectReadStream stream)
   at LogicBase.Core.Messaging.TimeBasedCacheConfiguration.ReadFromStream(ObjectReadStream stream)
   at LogicBase.Framework.ArrayTypeConverter.GetObject(ObjectStorageContainer storageContainer, ObjectStorageObjectData values, Type valueType, ObjectStorageErrorHandler errorHandler)
   --- End of inner exception stack trace ---
   at LogicBase.Framework.ArrayTypeConverter.GetObject(ObjectStorageContainer storageContainer, ObjectStorage

Cause

Corrupted configuration files due to improper Windows shutdown.

Resolution

Run the dbtool.exe utility to correct this issue. This file can be found in <Altiris_installation_drive>:\Program Files\Altiris\Workflow Designer\Ensemble folder. Verify that the settings that appear in it match what was originally configured during the Workflow installation. Save the settings, then retry starting the LogicBase server extensions.