spacer
cornerspacercorner
Customer Zone Partner Zone
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Discuss: Customer Forums Learn: Knowledge Base Ideas: Your Suggestions Read: Blog Articles Support: Help Desk & Resources

No Event Log File Path Causes Engine Crash

0 Kudos
Started 05-21-2010 by
Modified 05-21-2010 by
Article Options

Product: Metastorm BPM
Version: 7.x

Issue

  • An event occurs that prompts the Engine to write to the log file. After this, the Engine stops responding and users get the following error message:

    Service is not available.
    Creating an instance of the COM component with CLSID {EBAC9532-3094-11D4-9B1F-00C04F2A1F69} from the IClassFactory failed due to the following error: 80004005.

Resolution

  • If the Engine has been configured to log events to a file, instead of to the Windows event log, and no file path is specified, this behavior will be seen. Check the following registry values on the Engine server:

    HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\EnableEventLogToFile
    HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\EventLogFilePath

    If EnableEventLogToFile is set to 1, make sure a valid path is specified for EventLogFilePath. If a blank path is specified, the Engine will start but will exhibit the behavior described above. If an invalid path is specified, the Engine will not start.
Contributors
line spacer line
spacerFollow Metastorm on:
spacer Twitter YouTube Blog iTunes LinkedIn Metastorm Community Central, MC2
spacer Copyright © 2011 OpenText Corporation. All Rights Reserved.spacer About Metastormspacer Privacyspacer Legalspacer Site Mapspacer RSSspacer Contact Us
Microsoft Gold Certified Partner
Powered by Windows Azure
line spacer line