You are here: BlueCielo Meridian Enterprise Administrator's Guide > Windows event log IDs

Appendix H: Windows event log IDs

Various Meridian Enterprise components log events in the Windows event log. These can be of any of the three supported event types: Information, Warning, or Error. The ID of the event can be used to determine the cause of the event and whether action needs to be taken to prevent the event from occurring.

The following table lists the event log IDs for the Warning and Error events from Meridian Enterprise sources. The Information level events an be safely ignored.

Windows event log IDs
ID Level Description or example error message shown

  AutoManager EDM Server

6

This vault must be upgraded to the new version by your system administrator.

256 Rare event generated only if updating the data version number fails during a vault upgrade.
257

Could not read User Database settings. Error code is 0x80070003.

258

Could not start User Database using this connection string 'C:\BC-Meridian Vaults\ICUserDB.SDF'. Error code is 0x80004005

Hypertrieve and HyperCache

257

Load failed (124) C:\BC-Meridian Vaults\<VaultName>\<VaultName>.HDB

258

Low cache size on (0) C:\BC-Meridian Vaults\<VaultName>\<VaultName>.hdb. Cache size 100MB is less than 25% of database size (1142MB). Performance may be degraded.

  AutoManager OML

4

Behavior BlueCieloECM.UIBehNet.Register failed to register; Cannot find class dependency 'UIBeh.Register' for 'BlueCieloECM.UIBehNet.Register'.

5

No more licenses available

256 Generated when an invalid user account name is used or a disk full condition is suspected by our stream server.
258 Generated when an upgrade of security fails for very old vaults.

  IC Meridian Object Manager

256

Last error reported by the database engine, for example:

  • Exception in calling database engine.
  • Unexpected error in database engine.
  • The clock on the server has gained more than 7 days since the last time the EDM Server was active. Please contact your administrator to verify the time on the server.
  • Incorrect log version

  AutoManager License Server

256 Generic error message
257

Generic error message for all licenses in use, for example, All licenses in use (BC [M] Classic - User License 9.4 License)

258

The license server executable file is corrupted.

259

The License Server has expired.

260

New License Database created.

261

An other instance of the license server is already active.

262

The trial license (<LicenseName>) has expired.

263

License #<SerialNumber> was disabled by update or migration to #<SerialNumber>.

HTSQLIO and HTORAIO

1

Connection to SQL server failed after 3 retries. Connection failure.

2

Connection to SQL server required 2 retries.

  AMTaskServer

0

A <ErrorCode> error occurred on an attempt to connect as user <UserAccount>. Reason: <ErrorDescription>.

Execution of task <TaskName> failed. Reason: <ErrorDescription>.

0

An error <ErrorCode> occurred in <ErrorSource> while processing the task <TaskName>. Reason: <ErrorDescription>..

A <ErrorCode> error occurred while processing the task <TaskName>. Reason: <ErrorDescription>..

A <ErrorCode> error occurred in <ErrorSource> while submitting a task of <TaskName> type provided by user <UserAccount>, as <TaskFileName>.

A <ErrorCode> error occurred in <ErrorSource> while submitting a task of <TaskName> type provided by user <UserAccount>. Reason: <ErrorDescription>..