Policy Engine Hub Log Codes

Error Code Reference Guide › Policy Engine Hub Log › Policy Engine Hub Log Codes

More information:

Policy Engine Hub Log Codes

The following are error, warning and informational codes for the Policy Engine Hub log file. The log files are named WgnPHub_<datestamp>.log.

E1A11 (Error 6673)

Failed to disconnect a policy engine on machine <machine name>. Error was <Error data>.

Reason:

Could not cleanly disconnect from the policy engine. Very rare.

E1A1A (Error 6682)

"Event <subject> has been timed out while waiting for policy engine <PE name>"

Reason:

The event timestamp was found to be expired just before being assigned to a policy engine.

E1A1C (Error 6684)

Failed to analyze event from <PE state> state on policy engine <PE name>.

Reason:

The event was just about to be assigned to policy engine when the policy engine status changed (shutdown, suspended). The event will be reassigned to another policy engine. Very rare.

E1A22 (Error 6690)

Failed to respond to heartbeat on policy engine <PE name>. Error was <Error data>.

Reason:

When a heartbeat is received by the hub from a policy engine it responds with its own call back to the policy engine. If that call fails it probably implies a serious network problem. Very rare.

E1A24 (Error 6692)

Timed out waiting for management thread on <PE name> to die cleanly.

Reason:

The policy engine handling code has failed to shut down cleanly. Very rare.

E1A2C (Error 6700)

Failed to connect to the policy engine <pe name>. Error was <Error data>.

Reason:

The DCOM connection to the policy engine could not be created. Most likely error is ACCESS_DENIED which implies a problem with the SetCredentials user.

E1A2E (Error 6702)

The 'CA DataMinder Policy Engine Server' service has not been started on machine <machine name>. Please manually start it.

Reason:

The hub has queried the remote service manager and has found the WgnPESv service has not been started.

E1A2F (Error 6703)

The 'CA DataMinder Policy Engine Server' service is not registered on machine <machine name>. Please reinstall it.

Reason:

The hub has queried the remote service manager which cannot find the WgnPESv service.

E1A30 (Error 6704)

Cannot contact machine <machine name>. Please check for access.

Reason:

The hub cannot query the remote service manager. Possibly the service manager itself has not started yet.

E1A31 (Error 6705)

Access is denied contacting machine <machine name> for service status.

Reason:

The hub cannot query the remote service manager because of a security problem. Check rights of credentials user.

E1A32 (Error 6706)

Failed to impersonate user. Error was <Error data>.

Reason:

The hub failed to use the credentials user correctly. Check rights of credentials user. Very rare.

E1A33 (Error 6707)

Failed to obtain a monitor callback from PE on machine <machine name>. Error was <Error data>.

Reason:

Failed to initialize policy engine. Implies a serious error with the policy engine. Very rare.

E1A34 (Error 6708)

Failed to register monitor callback on <machine name>. Error was <Error data>.

Reason:

Failed to initialize policy engine. Implies a serious error with the policy engine. Very rare.

E1A39 (Error 6713)

Failed to unregister monitor callback on PE <pe name>. Error was <Error data>.

Reason:

Policy engine failed to disconnect cleanly. Implies a problem with the policy engine.

E1A3B (Error 6715)

Failed to register client on policy engine <pe name>. Error was <Error data>.

Reason:

Failed to initialize the policy engine.

E1A3C (Error 6716)

Failed to UnregisterClient on Machine <pe name>. Error was <Error data>.

Reason:

Failed to disconnect cleanly from the policy engine.

E1A3D (Error 6717)

SetConfig failed on <pe name>. Error was <Error data>.

Reason:

Failed to initialize the policy engine. The usual error is because of an incorrect default/fallback user.

E1A3F (Error 6719)

The method '<method name>' on policy engine <pe name> has taken too long to complete. The call may now be canceled.

Reason:

Most calls to the policy engine from the hub are timed. If this time exceeds "PECallTimeoutMilliseconds" (or the default if not defined), the call is failed and the policy engine is reconnected.

E1A46 (Error 6726)

SetEventDetails on pWgnHubWorkItem failed. Error was <Error data>.

Reason:

There was a problem creating the necessary event data to pass to a policy engine. This may be due to being passed bad data by the client, or possibly due to environmental problems such as low memory. Very rare.

E1A47 (Error 6727)

AddToBackofQueue failed to add pNewWorkItem to the back of queue. Error was <Error data>.

Reason:

E1A54 (Error 6740)

Event has failed to be added to queue. Error is: <error data>.

Reason:

Signifies a problem with the supplied event, or the hub environment being out of memory?

E1A5A (Error 6746)

Unknown type for event copying mode. New mode will be ignored.

Reason:

Unknown copying mode. Very rare.

E1A5E (Error 6750)

Event '<subject>' cannot be processed due to a communication fault - it will be returned to the source. Error is: <error data>.

Reason:

The event cannot be processed due to a problem with the data source. Most likely, the client has disconnected from the hub while there are outstanding events.

E1A5F (Error 6751)

Failed to add event '<subject>' to <pe name>. Error was <error data>.

Reason:

Failed to add event to policy engine.

E1A68 (Error 6760)

Failed to obtain the IWgnEMailEventStore from the email store. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A69 (Error 6761)

Failed to obtain the mail envelope from the email store. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A6A (Error 6762)

Failed to obtain the subject from the mail envelope. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A6B (Error 6763)

Event '<subject>' failed to be processed on policy engine <pe name> and will be retried. Retry count is <number>. Error was: <error data>.

Reason:

The policy engine has failed to process an event. It will be retried.

E1A6C (Error 6764)

Event '<subject> failed to be processed on policy engine <pe name>. Error was: <error data>.

Reason:

The policy engine has failed to process an event. It will not be retried, as retry count was set to 0.

E1A6D (Error 6765)

Event '<subject>' failed to be processed on policy engine <pe name> and has reached its maximum retry count. It will be returned. Error was: <error data>.

Reason:

The policy engine has failed to process an event. It will not be retried, as event has reached its maximum retry count.

E1A6E (Error 6766)

Failed to CoCreate a WgnComboStream. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A6F (Error 6767)

Failed to obtain the IWgnEMailEventStore interface from iEvent. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A70 (Error 6768)

Mark() on the EventStore failed. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A71 (Error 6769)

SaveStream() on the Event failed. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A72 (Error 6770)

Stat() on the Event failed. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A73 (Error 6771)

Failed to CoCreate a WgnEvent. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A74 (Error 6772)

Seek on pStream failed. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A75 (Error 6773)

LoadStream on pNewWgnEvent failed. Error was <error data>.

Reason:

Internal error converting email data. Very rare.

E1A76 (Error 6774)

Failed to initialize COM security. Error is <error data>.

Reason:

Failure to initialize the DCOM security. Possible problem with too early windows version, or issue with credentials user.

E1A77 (Error 6775)

You must supply valid logon credentials via the SetCredentials option before starting the Policy Engine Hub. Error is: <error data>.

Reason:

Generally this means the credentials user does not have the "Logon as batch" right.

E1A7A (Error 6778)

Failed to obtain password from LSA. Error is: <error data>.

Reason:

Failure to obtain password. Please retry setting the credentials user with installer or SetCredentials switch.

E1A7B (Error 6779)

Timed out removing event on queue <queue name>.

Reason:

Implies an event counting problem on an internal queue. Very rare.

E1A7C (Error 6780)

Event '<subject>' has been timed out.

Reason:

The event has been in the hub longer than "GlobalEventTimeoutSeconds".

E1A7E (Error 6782)

Critical Error: <freeform text>.

Reason:

Unpredicted critical error in hub. The hub should be restarted after one of these. Very rare.

E1A88 (Error 6792)

Failed to notify completion of <subject>. Error was <error data>.

Reason:

Hub has failed to notify client (exchange, notes, importer and so on) of the completed status of an event. This is usually because the client has been closed down.

E1A8A (Error 6794)

Failed to initialize queue <queue name>. Are the registry entries complete?

Reason:

Implies serious problems with the registry settings for a queue. Unlikely to happen.

E1A8E (Error 6798)

An error occurred trying to write to the Policy Engine Hub Log file.

Reason:

This can occur if the policy engine hub cannot write to its log file.

E1A8F (Error 6799)

The LowWaterMarkEventCount registry value cannot be higher than the HighWaterMarkEventCount value.

Reason:

The value of LowWaterMarkEventCount must not be higher than that of HighWaterMarkEventCount.

E1A90 (Error 6800)

The LowWaterMarkMB registry value cannot be higher than the HighWaterMarkMB value.

Reason:

The value of LowWaterMarkMB must not be higher than that of HighWaterMarkMB.

E1A91 (Error 6801)

Access to the policy engine on machine <machine name> has been denied. This may occur if the user account <account name> is not a member of the local administrators group on that machine.

Reason:

Access to the policy engine host machine has been denied. This may occur if the specified user account is not a member of the local administrators group on the policy engine host machine.

I1A05 (Informational 6661)

The <number of> surplus policy engine connections(s) on queue <queue name> will be disconnected.

Reason:

This is the same as I1A04 above except for multiple Policy Engines.

I1A06 (Informational 6662)

Connection to policy engine <PE Name> failed. Error is <error data>.

Reason:

The hub failed to establish a DCOM connection to the PE. This is usually due to DCOM security issues with the hub "SetCredentials" user or, if used, hub service named user. Please check installation guide.

I1A07 (Informational 6663)

There are no more standby policy engines to replace <PE Name> so it will be restarted. Shutdown reason <error data>.

Reason:

An active PE has failed to connect with code <error data> and there are no more standby's to connect. The failing PE will continue to attempt to connect.

I1A08 (Informational 6664)

Active policy engine connection <PE Name> has been made inactive and will be restarted. Shutdown reason <Error data>.

Reason:

PE has shut down because of the error shown, but will be restarted.

I1A09 (Informational 6665)

There are no more standby policy engines to replace <PE Name> so it will be restarted. Shutdown reason <Error data>.

Reason:

Restarting failed PE immediately as there are no more standby policy engines to start.

I1A0A (Informational 6666)

Policy engine <PE Name> has been suspended.

Reason:

The policy engine has stopped processing because its infrastructure has suspended. The infrastructure may have been manually suspended or it may have been suspended automatically because of a fault such as lack of disk space.

I1A0B (Informational 6667)

Policy engine <PE Name> has been resumed.

Reason:

The suspended policy engine has started processing again.

I1A0C (Informational 6668)

The <number> surplus policy engine connections(s) on queue <queue name> will be disconnected.

Reason:

One or more Active policy engines have resumed and the Standby policy engines that replaced them are no longer required.

I1A0E (Informational 6670)

Policy engine <PE Name> has stopped processing.

Reason:

The policy engine has stopped processing. This message is part of the normal PE disconnection procedure.

I1A0F (Informational 6671)

Policy engine <PE Name> has started processing.

Reason:

The policy engine is now ready to accept events.

I1A12 (Informational 6674)

Failed to created policy engine proxy for machine <machine name> on queue <queue name>.

Reason:

Error was <Error data>. Failed to initialize policy engine on named queue. Very rare.

I1A15 (Informational 6677)

Starting up standby policy engine connection <PE Name> to make up requirements.

Reason:

Replacing Active policy engine with standby policy engine.

I1A16 (Informational 6678)

Starting up standby policy engine connection <PE name> to make up for failing active policy engine.

Reason:

Attempting to replace a single active policy with a standby.

I1A18 (Informational 6680)

No more standby policy engines to connect to make up requirements.

Reason:

Cannot make up numbers of active policy engines with standbys because there are no more available.

I1A1B (Informational 6683)

Policy engine <PE Name> is currently unable to process event '<subject>'. The event will be reassigned.

Reason:

The event was just about to be assigned to policy engine when the policy engine status changed (shutdown, suspended). The event will be reassigned to another policy engine.

I1A1D (Informational 6685)

Config changed on policy engine <pe name>.

Reason:

The policy engine registry configuration has changed.

I1A1E (Informational 6686)

Security config changed on policy engine <pe name>.

Reason:

Policy engine code for named policy engine has acknowledged changes to the credentials user.

I1A1F (Informational 6687)

Reason:

Event timeout changed on policy engine <pe name>.

Policy engine code acknowledged change of global event timeout in registry.

I1A20 (Informational 6688)

Common config changed on policy engine <pe name>.

Reason:

Policy engine code acknowledged change of common configuration in registry (Default user, Fallback user and so on).

I1A23 (Informational 6691)

Policy engine <pe name> has signaled its intention to shut down.

Reason:

The named policy engine is shutting down. Either the service is being stopped, or the host machine is shutting down.

I1A25 (Informational 6693)

Policy engine connection to <pe name> will now attempt to shut down.

Reason:

The policy engine is being shut down, either because it has been removed from the registry or the hub is being shut down.

I1A26 (Informational 6694)

Heartbeat not received from policy engine <pe name>. It will be retired.

Reason:

The hub has not received a heartbeat from the policy engine for 4 x HeartbeatPeriodMilliseconds. This implies either the policy engine is extremely busy, deadlocked or there is a network problem.

I1A27 (Informational 6695)

Suspect heartbeat failure on policy engine <pe name>.

Reason:

After a heartbeat failure described above in I1A26 a double check is applied to make sure it wasn't a simple timer problem. If this is the case then the missed heartbeat is ignored.

I1A28 (Informational 6696)

Policy engine for <pe name> will now attempt to connect.

Reason:

The policy engine will now attempt to connect.

I1A29 (Informational 6697)

Attempting to reconnect to policy engine <pe name>.

Reason:

The policy engine will now attempt to reconnect.

I1A2A (Informational 6698)

Policy engine <pe name> has been successfully loaded with modified settings.

Reason:

Policy engine specific settings (heartbeat, reconnect time etc) have been applied to the policy engine.

I1A2D (Informational 6701)

Successfully connected to policy engine <pe name>.

Reason:

The policy engine has connected successfully.

I1A35 (Informational 6709)

Deallocating all events on <pe name>.

Reason:

About to deallocate all events from policy event and reassign them.

I1A36 (Informational 6710)

Timed out waiting for events to process on policy engine <pe name>. Outstanding events will be deallocated.

Reason:

When a policy engine is shut down cleanly all the events already allocated to a policy engine are given a period of time to complete naturally. After this time events are forcibly deallocated.

I1A37 (Informational 6711)

Successfully waited for all events to process on <pe name>.

Reason:

As in message I1A36 above but all events managed to complete before they got reallocated.

I1A38 (Informational 6712)

Disconnecting policy engine <pe name>.

Reason:

Policy engine is being disconnected.

I1A40 (Informational 6720)

Pre-processing thread pool changing from <thread count> to <thread count> threads.

Reason:

The "PreprocessingThreadCount" value (if defined,) has changed.

I1A41 (Informational 6721)

Completion thread pool changing from <thread count> to <thread count> threads.

Reason:

The "CompletionThreadCount" value (if defined,) has changed.

I1A43 (Informational 6723)

Total item memory has gone under low watermark.

Reason:

The combined memory load of all events in the queues has gone below (LowWaterMarkMB) while in throttling mode. Throttling mode will be canceled.

I1A45 (Informational 6725)

Event count has gone under low watermark.

Reason:

The combined count of all events in the queues has gone below (LowWaterMarkEventCount) while in throttling mode. Throttling mode will be canceled.

I1A4C (Informational 6732)

Failed to add event '<subject>' of size <event size> to a valid queue returning to input queue.

Reason:

Temporarily unable to assign event to a queue, the operation will be retried.

I1A51 (Informational 6737)

Successfully created queue <queue name>.

Reason:

A queue has been successfully created.

I1A52 (Informational 6738)

Removing queue <queue name>.

Reason:

A queue is about to be removed.

I1A53 (Informational 6739)

Queue <queue name> has been removed.

Reason:

A queue has been successfully removed.

I1A55 (Informational 6741)

Hub throttling mode has been set to 'Wait'.

Reason:

The throttling mode has been set to "wait" mode.

I1A56 (Informational 6742)

Hub throttling mode has been set to 'Fail'.

Reason:

The throttling mode has been set to "fail" mode.

I1A57 (Informational 6743)

Event copying mode has been set to 'Immediate'.

Reason:

Incoming events are copied in full in the hub.

I1A58 (Informational 6744)

Event copying mode has been set to 'On Demand'.

Reason:

Parts of the incoming event are copied when required.

I1A59 (Informational 6745)

Event copying mode has been set to 'Never'.

Reason:

The incoming event is never copied by the hub.

I1A5B (Informational 6747)

Accepted event '<subject>'.

Reason:

The event has successfully entered the hub.

I1A5C (Informational 6748)

About to analyze event '<subject>' on <pe name>.

Reason:

The event is about to be processed on policy engine.

I1A5D (Informational 6749)

Analyzing event '<subject>' on <pe name>

Reason:

The event is being processed on policy engine.

I1A60 (Informational 6752)

Completed processing of event '<subject>' on <pe name> status <processing code>.

Reason:

The hub has finished with event and is returning the event to the client. The processing code is the final state of the event and may be a failure code. This event has been processed by a policy engine.

I1A61 (Informational 6753)

Completed processing of event '<subject>' status <processing code>. The hub has finished with event and is returning the event to the client.

Reason:

The processing code is the final state of the event and may be a failure. This event has not been processed by a policy engine.

I1A78 (Informational 6776)

The Policy Engine Hub Service is being run as a named user but has the 'Credentials' user specified. The 'Credentials' user will be ignored.

Reason:

The hub has previously been run with the credentials user, but now is running as a named user. Ideally the -clearcredentials switch should be used to clear details of the credentials user.

I1A79 (Informational 6777)

Policy Engine Hub is running in security context of '<user name>'.

Reason:

Shows the user the hub process is running as. This is the main process user, not the credentials user.

I1A7D (Informational 6781)

Reason:

General freeform informational text.

I1A7F (Informational 6783)

CA DataMinder Policy Engine Hub is starting.

Reason:

The hub is starting and is initializing.

I1A80 (Informational 6784)

CA DataMinder Policy Engine Hub stopped successfully.

Reason:

The hub has stopped.

I1A81 (Informational 6785)

CA DataMinder Policy Engine Hub started successfully.

Reason:

The hub has started.

I1A82 (Informational 6786)

*******************************************************

Reason:

Used before starting (I1A7F) and after stopping (I1A80).

I1A85 (Informational 6789)

Closing Distributor Agent ...

Reason:

The Distributor agent (if installed) is closing. No more events will be processed from the distributor.

I1A86 (Informational 6790)

The Policy Engine Hub Service is being run under the LocalSystem account and has no 'Credentials' user specified. Remote policy engines may not be accessible.

Reason:

When the hub is run in this mode you may get ACCESS_DENIED errors from remote policy engines. You should only use this mode if you have a single policy engine on the hub machine.

I1A87 (Informational 6791)

The Policy Engine Hub Service has been configured with the 'Credentials' user '<name>'.

Reason:

The hub will use the named user for all remote communications.

I1A89 (Informational 6793)

<subject> successfully called back into source.

Reason:

Hub has notified client of completion of event. Hub has finished with event.

I1A8B (Informational 6795)

Policy engine <PE Name> connected successfully.

Reason:

The policy engine has connected. Note this does not mean that it has started processing yet.

I1A8C (Informational 6796)

Shutting down standby policy engine connection <PE Name> as it's surplus to requirements.

Reason:

A standby PE that was previously started to compensate for a failing active PE has been disconnected. Most likely this is due to an active PE restarting.

W1A19 (Warning 6681)

Event '<subject>' has been deallocated from queue <queue name>.

Reason:

The named queue is being shutdown and all events currently allocated to it are being reallocated to another queue.

W1A3A (Warning 6714)

Event <subject> has been deallocated from policy engine <pe name>.

Reason:

Event has been successfully deallocated from policy engine.

W1A42 (Warning 6722)

Total item memory has gone over high watermark.

Reason:

The combined memory load of all events in the queues has exceeded (HighWaterMarkMB) and the throttling mode will be used.

W1A44 (Warning 6724)

Total event count has gone over high watermark.

Reason:

The combined count of all events in the queues has exceeded (HighWaterMarkEventCount) and the throttling mode will be used.

W1A48 (Warning 6728)

Event has been added to the hub while in memory throttling mode event will be returned.

Reason:

The hub is in memory throttling mode and is set by the client to fail incoming events.

W1A49 (Warning 6729)

Event has been added to the hub while in memory throttling mode event processing will be delayed.

Reason:

The hub is in memory throttling mode and is set by the client to delay incoming events so the total memory load does not go over high watermark.

W1A4A (Warning 6730)

Event has been added to the hub while in event count throttling mode. Event will be returned.

Reason:

The hub is in event throttling mode and is set by the client to fail incoming events.

W1A4B (Warning 6731)

Event has been added to the hub while in event count throttling mode. Event processing will be delayed.

Reason:

The hub is in event throttling mode and is set by the client to delay incoming events so the total event count does not go over high watermarks.

W1A4D (Warning 6733)

No active queues are defined so no events can be processed.

Reason:

This should never happen as you always have a default queue.

W1A50 (Warning 6736)

Queue '<queue name>' has the same byte limit as queue '<queue name> and will not be assigned events. Please reconfigure you queues.

Reason:

If two queues are configured with the same byte limit only one of the queues will be assigned events. It is best to reconfigure one of the queues.

W1A62 (Warning 6754)

Event '<subject>' has previously been completed, possibly by a timeout.

Reason:

The event will not be completed as it has already been completed (possibly previously timed out.)

W1A63 (Warning 6755)

Event '<subject>' has not been processed but will be completed successfully. Reason is: <error data>.

Reason:

Policy engine has returned this event unprocessed. A typical reason is having no matching user and no default user set. It will be returned to the client as usual.

W1A83 (Warning 6787)

Queue <queue name> is entering failure mode.

Reason:

A queue has had no processing policy engines for longer than NoPEFailTimeoutSeconds. Future events for this queue will be immediately timed out.

W1A84 (Warning 6788)

Queue <queue name> is leaving failure mode.

Reason:

A queue previously in no PE failure mode has left that mode because a policy engine has started processing.