Error Code Reference Guide › Event Import Log › Event Import Log Codes

Event Import Log Codes

The following are error, warning and informational codes for the event import log:

E0DA (Error 218)

System Error. Threads in the importer are having to be re-initialized too frequently.

Reason:

Logged when too many problems have occurred with the infrastructure. The importer will stop after logging this message.

I0DA (Informational 218)

System Info. Thread <thread ID> re-initializing.

Reason:

Occurs after an error 0x0DA9 if the importer is able to re-initialize the infrastructure.

E0D15 (Error 3349)

<Error description>

Reason:

General code to report an Event Import error.

E0D70 (Error 3440)

Failed. Title: <Message Title>. Reason: API <Method Name> failed with <error code>. Ext Error Code: <error code>. Ext Error Description: <description>

Reason:

Reported when the infrastructure returns an error, preventing the importer from continuing.

E0D71 (Error 3441)

System Error. The broker thread caught an exception. The error was: <error code>. Description is: <description>

Reason:

Unlikely to occur in normal operation. Following this error the importer will shut down.

E0D72 (Error 3442)

System Error. The event thread caught an exception. The error was: <error code>. Description is: <description>

Reason:

Unlikely to occur in normal operation. Following this error the importer will shut down.

I0D73 (Informational 3443)

Captured. Title: <message title>

Reason:

Only logged if the importer's logging is set to 'verbose' and a message is successfully imported.

E0D75 (Error 3445)

Failed. Title: <message title>. Reason: <description>

Reason:

Unlikely to occur during normal operation. If it does the importer will shut down.

I0D76 (Informational 3446)

Excluded (Imp). Title: <message title>. Reason: <description>

Reason:

Logged only when logging is set to 'verbose'. It may be seen when an invalid message type is imported, such as the Outlook Welcome message.

E0D77 (Error 3447)

Failed. Title: <message title>. Reason: <description>, Extended Error: <error code>

Reason:

Seen when the importer fails to obtain the participants of a message. The reason for the failure is described by the extended error code and description.

E0D78 (Error 3448)

Failed. Title: <message title>. Reason: <description>, Extended Error: <error code>

Reason:

Seen when the importer fails to process a message. The reason for the failure is described by the extended error code and description.

I0D79 (Informational 3449)

Excluded (Imp). Title: <message title> Reason: Participants all failed the user filter.

Reason:

Occurs when the importer fails to import a message as it has no participants associated with it.

E0D7A (Error 3450)

System Error. A critical error occurred processing message <message title>. Error was <error code>.

Reason:

Unlikely to occur in general use. It is used as a 'catch all' error code when something extremely unexpected has gone wrong.

I0D7E (Informational 3454)

System Info. Message Processing thread <thread ID> has finished processing.

Reason:

Only logged when the importer's logging is set to 'verbose'. This informs the user that a message processing thread has finished processing messages. The thread will exit after this message.

I0D7F (Informational 3455)

System Info. Import Started.

Reason:

Always logged when a new import session is started.

I0D80 (Informational 3456)

System Info. Import Finished.

Reason:

Always logged when an import session finishes.

E0D81 (Error 3457)

System Error. Title: <message title>. Reason: chapter <chapter number> is reported as ignored.

Reason:

Unlikely to occur under normal operation. This error can occur if the conversation source files are corrupted for example.

E0D82 (Error 3458)

Failed. Title: <message title>. Reason: A chapter could not be obtained from the importer. Error: <error code>. Reason <description>.

Reason:

Can occur if for some reason the conversation file has become corrupted and the importer parameter Engine.StopOnError = yes. The importer will begin shutdown after this log entry.

E0D84 (Error 3460)

System Error. A critical error occurred in the importer. Extended error code: <error code>, Extended error description: <description>.

Reason:

Can occur if system resources are extremely low. Details of the error encountered found in the extended error code and description. The importer will begin shutdown after this log entry.

I0D85 (Informational 3461)

Excluded (Imp). Title: <message title>. Reason: After applying the retention period, the email expiry date is in the past.

Reason:

The message's timestamp plus the retention period is earlier than the time of import. The retention period is specified by the parameter 'Engine.EventRetentionPeriod' in the importer's ini file. Only logged when the importer's logging is set to 'verbose'.

E0D86 (Error 3462)

Failed. Title: <message title>. Reason: Unable to obtain a remote location from the importer. Extended error code: <error code>, Extended error description: <description>.

Reason:

Can happen if a message is marked as being remote, and yet no remote location is available for it. This would generally indicate a problem with the remote data storage system or corruption of the message.

E0D87 (Error 3463)

Failed. Title: <message title>. Reason: Unable to obtain a remote location from the importer for message <message>.

Reason:

Unlikely to occur in general use. If it is seen the importer will begin shutting down after logging this message.

E0D88 (Error 3464)

Failed. Title: <message title>. Reason: Unable to obtain a remote location from the importer. The Event Importer returned <error code>.

Reason:

Indicates that there was a problem obtaining the message's remote location. The error that occurred while trying to do this is described by the <error code>.

E0D89 (Error 3465)

System Error. The StartImporting RPC thread caught an exception. Importer will now shut down. The error was: <error code>. Description is: <description>.

Reason:

An unexpected error occurred in the main importer thread. The error is described by the error code and description.

E0D8B (Error 3467)

Failed. Title: <message title>. Reason: Import Policy Hub or Engine reported <description>.

Reason:

Used to log all messages that failed to be successfully dealt with by the Import Policy hub. The specific error is detailed by the error code.

I0D8C (Informational 3468)

System Info. Import Summary: Processed <number>. Captured <number>. Excluded <number>. Failed. <number>.

Reason:

Occurs before shutdown to provide a summary of how many messages succeeded, failed or were ignored during an import session.

E0D8D (Error 3469)

System Error. A critical error occurred processing message <message title>. Error was <error code>.

Reason:

Should not be seen in general use. It indicates that an unexpected error occurred while trying to obtain details regarding the participants of a message.

E0D8E (Error 3470)

System Error. Failed to create a transaction. Error code <error code>. Ext Error Code: <error code>. Ext Error Description: <description>.

Reason:

May occur if system resources are extremely low or if there is a serious problem with the infrastructure service. The initial error code details the error code returned by the infrastructure service. The extended error code and description relate to the error that occurred in the infrastructure.

E0D8F (Error 3471)

System Error. Failed to commit a transaction. Error code <error code>. Ext Error Code: <error code>. Ext Error Description: <desc>.

Reason:

See above.

E0D90 (Error 3472)

System Error. Failed to roll back a transaction. Error code <error code>. Ext Error Code: <error code>. Ext Error Description: <description>.

Reason:

See above.

I0D92 (Informational 3474)

System Info. Message broker thread <thread ID> has finished processing.

Reason:

Only logged when the importer's logging is set to 'verbose'. This informs the user that the thread that obtains messages from their source has finished obtaining messages. The thread will exit after this message.

E0D93 (Error 3475)

Failed. Could not obtain a sequence ID for chapter <chapter>. Error was <error code>, from <API>. Ext Error Code: <error code>. Ext Error Description: <description>.

Reason:

Occurs when the importer fails to obtain a sequence ID from the infrastructure. Sequence IDs are used to link the chapters of a sequence. This may occur if there is a problem with the infrastructure.

I0D94 (Informational 3476)

System Info. System successfully connected to the policy engine hub.

Reason:

Occurs when the importer has successfully connected to the Import Policy hub. It will try to do this when Engine.UsePolicyEngineConnector = yes defined in the importer's initialization file.

I0D95 (Informational 3477)

System Info. Successfully re-connected to the policy engine hub.

Reason:

Occurs when the importer has successfully re-connected to the Import Policy hub. It will try to do this when Engine.UsePolicyEngineConnector = yes defined in the importer's initialization file and the connection with the hub is temporarily lost.

E0D96 (Error 3478)

System Error. Failed to connect to the policy engine hub. Error was <error code>.

Reason:

Occurs when the importer has failed to connected to the Import Policy hub. The importer will try to connect to the hub when Engine.UsePolicyEngineConnector = yes defined in the importer's initialization file. This connection may fail if there is a problem with the Import Policy hub. The error is described by the error code.

E0D97 (Error 3479)

System Error. Shutting down the importer, as the infrastructure is stopping.

Reason:

Occurs when the infrastructure notifies the importer that it is stopping while the importer is running.

E0D98 (Error 3480)

System Info. The infrastructure is starting up.

Reason:

Occurs when the infrastructure notifies the importer that it is starting up.

E0D99 (Error 3481)

System Info. The infrastructure is shutting down.

Reason:

Occurs when the infrastructure notifies the importer that it is shutting down.

E0D9A (Error 3482)

System Info. The infrastructure failed to start.

Reason:

Occurs when the infrastructure notifies the importer that it has failed to start.

E0D9B (Error 3483)

System Info. The infrastructure has been suspended.

Reason:

Occurs when the infrastructure notifies the importer that it has been suspended.

E0D9C (Error 3484)

System Info. The infrastructure has been resumed.

Reason:

Occurs when the infrastructure notifies the importer that it has been resumed.

E0D9D (Error 3485)

System Info. The infrastructure has entered an undefined state.

Reason:

Occurs when the infrastructure notifies the importer that it has entered a state, but that state is not recognized by the importer.

W0D9F (Warning 3487)

System Info. A participant from the message <message title> was not imported: No email address.

Reason:

Occurs when a participant of the message did not have a participant address.

W0DA0 (Warning 3488)

System Error. Failed to initialize the importer. Error was <error code>. Error Description is <description>

Reason:

Occurs when a problem with configuration prevents the importer from starting correctly.

E0DA1 (Error 3489)

System Error. Failed to initialize the importer. The supplied import user <user name> does not have bulk import privileges.

Reason:

Can occur when Engine.BulkImporUserName and Engine.BulkImporUserPasswd (defined in the importer's initialization file or set using wgnimpsv –SetCredentials) are set for a user that does not have the correct privileges to allow event import to be done.

W0DA2 (Warning 3490)

System Warning. Failed to move file <file name> to failed directory. Error <error code>

Reason:

Can occur when the importer fails to move a file because it does not have access to it, or it has been deleted or a similar problem.

W0DA3 (Warning 3491)

System Warning. Failed to delete file <file name>. Error <error code>

Reason:

Can occur when the importer fails to delete a file because it does not have access to it, or it has been deleted or a similar problem.

W0DA4 (Warning 3492)

A generic log code through which importer .dll errors are made.

Reason:

Configuration and runtime errors that occur in the .dll that manages import of a specific type will be logged using this code.

W0DA5 (Warning 3493)

The remote data location tag <tag text> was not found in file <file name>. Resetting remote data type and location to NULL.

Reason:

Logged when an EML file is imported but the MIME headers are not available for the importer to determine the remote data location.

E0DA6 (Error 3494)

System Error. Could not initialize the importer. API <API name> failed with <error code>. Ext Error Code: <error code>. Ext Error Description: <description>.

Reason:

Generally caused by configuration or installation issues that prevent the importer from starting.

E0DA7 (Error 3495)

System Error. Could not initialize the importer. API <API name> failed with <error code>.

Reason:

Generally caused by configuration or installation issues that prevent the importer from starting.

E0DA9 (Error 3497)

System Info. An infrastructure API returned <error code> from <API name> while processing <message title>.

Reason:

Occurs when there is a problem communicating with the infrastructure service via COM. Usually the importer will be able to recover from this and re-initialize the infrastructure service.

I0DB0 (Informational 3504)

System Info. Processed <number>. Captured <number>, Excluded <number>, Failed <number>.

Reason:

Logged periodically for informational purposes.

I0DB1 (Informational 3505)

System Info. There are <number> messages outstanding in the import policy hub. Hub throttling is now on.

Reason:

Logged when the importer is throttling due to the number of messages being processed by the import policy or policy engine.

I0DB2 (Informational 3506)

System Info. There are <number> messages outstanding in the import policy hub. Hub throttling is now off.

Reason:

Logged when the importer is resumes importing after throttling due to the number of messages being processed by the import policy or policy engine.

I0DB3 (Informational 3507)

System Info. There are <number> messages ready for processing. Throttling is now on.

Reason:

Logged when the importer begins throttling due to the number of messages in the broker thread awaiting processing hitting the high water mark.

I0DB4 (Informational 3508)

System Info. There are <number> messages ready for processing. Throttling is now off.

Reason:

Logged when the importer resumes importing after throttling due to the number of messages in the broker thread awaiting processing hitting the high water mark.

E0DB5 (Error 3509)

System Error. Failed to get the IWgnImportEngine interface from the CWgnImportEngine object. Error was <error code>. Message was <message title>.

Reason:

Unlikely to occur under normal circumstances, but may occur if system resources are extremely low.

E0DB6 (Error 3510)

System Error. A critical exception occurred in the importer. The importer will now shut down.

Reason:

Unlikely to occur under normal circumstances, but may occur if system resources are extremely low.

E0DB8 (Error 3512)

System Error. The main thread caught an exception. The error was: <error code>. Description is: <description>.

Reason:

Unlikely to occur under normal circumstances, but may occur if system resources are extremely low.

E0DB9 (Error 3513)

System Error. Failed to register as a client of the policy engine. Error was <error code>.

Reason:

Unlikely to occur under normal circumstances, but may occur if there is a problem with the policy engine and the importer is in direct import policy mode.

E0DBB (Error 3515)

System Error. Failed to set the configuration of the policy engine. Error was <error code>.

Reason:

Unlikely to occur under normal circumstances, but may occur if there is a problem with the policy engine and the importer is in direct import policy mode.

E0DBC (Error 3516)

System Error. Failed to co-create the policy engine. Error was <error code>.

Reason:

Can happen when there is a problem co-creating the policy engine service. For example, the policy engine is not registered.

E0DBD (Error 3517)

System Error. Failed to register a callback interface with the policy engine. Error was <error code>.

Reason:

Unlikely to occur under normal circumstances, but may occur if there is a problem with the policy engine and the importer is in direct import policy mode.

E0DBE (Error 3518)

System Error. Failed to query the policy engine object for its callback interface. Error was <error code>.

Reason:

Unlikely to occur under normal circumstances, but may occur if system resources are extremely low.

E0DBF (Error 3519)

System Error. Failed to create the Import Policy Engine's suspension event. Error was <error code>.

Reason:

Unlikely to occur under normal circumstances, but may occur if system resources are extremely low.

I0DC0 (Informational 3520)

System Info. The policy engine has reported that its local infrastructure is suspended.

Reason:

Occurs when the policy engine informs the event importer that the local infrastructure has been suspended.

I0DC1 (Informational 3521)

System Info. The policy engine has reported that its local infrastructure has been resumed.

Reason:

Occurs when the policy engine informs the event importer that the local infrastructure has been resumed.

I0DC2 (Informational 3522)

System Info. A call to the policy engine has failed and the policy engine will now be re-created and initialized. Error was <error code>.

Reason:

Unlikely to occur under usual circumstances. It may be seen if the policy engine service crashes or is terminated in an unusual manner.

E0DC3 (Error 3523)

Failed. Title: <message title>. Failed to pass a message to the policy engine. Error was <error code>.

Reason:

Logged when the importer fails to pass a message to the policy engine for processing.

E0DC4 (Error 3524)

The remote data location item <location> was not found.

Reason:

Logged when the Event Importer is importing Lotus Notes events and a remote data location is expected but not found in the message.

I0DC6 (Informational 3526)

System Info. Title: <message title>. Info: A message will be passed to the policy engine again. It was not processed as the infrastructure has been suspended.

Reason:

Logged when the policy engine fails to process an event because the infrastructure was suspended.

I0DC7 (Informational 3527)

Excluded (PE). Title: <message title>. Reason: <description>.

Reason:

Logged when the policy engine processes a message, but it is not captured.

E0DC8 (Error 3528)

The required remote data location tag <tag string> was not found in file <file name>. Failing the message.

Reason:

Logged when the Event Importer is importing EML events and a remote data location is expected but not found in the message.

I0DCA (Informational 3530)

Abandoned. Title: <message title>. Reason: 'Dumping outstanding events'.

Reason:

Seen when the importer is stopped via service stop or the PC is shutting down.

I0DD2 (Informational 3538)

Attachment References not supported in BB XML Logs. Event description: <description>, Reference:<reference text>.

Reason:

Logged from ImpBB.dll when it is processing a Bloomberg Email XML log that includes an attachment by reference.