Dialer History Messages panel

Dialer History Messages

Details

Additional Information

A COM exception occurred

A COM exception has occurred. Error: {xxx}

A Notifier request failed

A Notifier request failed. Error: {xxx}

A system status message was removed from the status view

The following system status error was removed from the status view: {xxx}

A warning error was reported by a Policy

A warning was reported by Policy: {xxx}. Message: {xxx}

The policy generates this message to report the error. The EventLog action creates this message.

A Win32 exception occurred

A Win32 exception has occurred. Exception: {xxx}

ACD workgroup not active on server

The ACD workgroup {xxx} is not active on this CIC server. Please add or enable this ACD workgroup before trying to start the campaign.

Active Group Change

Active group changed from {xxx} to group {xxx}

Active station lookup failed

An error occurred while trying to lookup the active station for Agent: {xxx}. Error: {xxx}. The error may indicate a problem with Client Services, please check the event log on the CIC server for further errors.

Agent Active Group Change

Agent set active group from {xxx} to {xxx}

If you are using Advanced Campaign Management feature, you will see these messages appear whenever someone manually transitions a campaign sequence. The message will list the name of the user who initiated the transition, the date and time the transition occurred, as well as the campaign groups involved in the transition.

Agent {xxx} transitioned active group from {xxx} to {xxx}

Agent not active, action ignored

A requested action will be ignored because the associated agent is not active in the campaign.

This message occurs when the system attempts to set the agent to Awaiting Callback status or process a break request when the agent is not logged on or active.

Agent not found in cache

The listed agent could not be located in the dialer cache. This may be due to the agent recently logging off or being forced out of the campaign after a connection failure. Please ensure that the agent is logged into the campaign or that they are logging out correctly. If the errors persist please contact PureConnect Customer Care.

Agent not logged in, Action ignored

A requested action will be ignored because the associated agent is not logged into the campaign.

Dialer no longer displays this message.

Agent Ping Failed

The listed agent has been automatically logged out of the campaign. The automatic logout was due to the loss of connection between the agent's scripter application and the Dialer process. If the agent exited the application without logging out then these errors should be expected, otherwise there may be network or custom application problems. If the errors persist please contact PureConnect Customer Care.

Dialer no longer displays this message.

An agent has attempted to disposition an interaction that the agent does not own.

An agent dispositioned a call that the agent does not own. This may be because the agent is not answering or the agent has transferred the call to another agent logged into the campaign. The action that was attempted on Call ID {xxx} will be ignored.

An error occurred validating a table.

An error occurred validating a campaign table. Error: {xxx} Table: {xxx}

On certain events, Dialer attempts to test that the database tables in the Dialer database remain valid. If the validation fails, this message appears.

An error was reported by a Policy: {xxx}

An error was reported by Policy: {xxx} Message: {xxx}

The policy generates this message to report the error. The EventLog action creates this message.

An event log message was reported by a rule action.

An error was reported by a rule action. nRule: {xxx} nRule Action: {xxx} nError Message: {xxx}

An exception has occurred.

An exception has occurred. Error: {xxx}

An information message was reported by Policy {xxx}

An information message was reported by Policy: {xxx}. Message: {xxx}

The policy generates this message to report the error. The EventLog action creates this message.

An unknown exception has occurred.

An unknown exception has occurred while performing operation: {xxx}

Behavior item failed to complete without error

The behavior: {xxx} failed to run properly. The error that was encountered: {xxx}

This message occurs when the system encounters an error with a Policy behavior.

Blended pause lifted for campaign

The blended pause for the listed campaign has been lifted.

Dialer no longer displays this message.

Call ID not found within contact attributes.

Call Id attribute is not present in the attributes to be updated to the database. The Call Id is needed to find the contact data associated with this interaction.  Unable to process completion for campaign.

This message occurs when the system attempts to complete the interaction. If this message continues to appear, contact PureConnect Customer Care.

Campaign has started

The listed campaign has started.

Call List has recycled

Call List has recycled. Number of recycles remaining: {xxx}. Contact records for new recycle: {xxx}.

Campaign group has transitioned

If you are using Advanced Campaign Management feature, you will see these messages appear whenever a transition occurs in a campaign sequence. The message will list the campaign groups involved in the transition, the reason for the transition, the date and time the transition occurred, and the condition that caused the transition.

Campaign group transitioned from {xxx} to {xxx}. Reason: {xxx} Item: {xxx} Parent: {xxx} Condition: {xxx}

Campaign has been paused due to an error.

Campaign {xxx} has been paused because the contact columns could not be loaded. Ensure that the Campaign Server is running and then set the campaign's status to Manual On. If this error occurs frequently please contact PureConnect Customer Care.

Campaign has been reset.

Campaign has been reset. The reset action occurs when an Administrator manually selects 'Reset Campaign' from the administrative plug-in or automatically via a Rule Action associated with the running campaign.

Campaign ID not found within contact attributes

Contact data does not contain a Campaign Id attribute.

Dialer no longer displays this message.

Campaign is now in a forced power dialing mode

The campaign is now in forced power dialing mode. Current abandon rate of {xxx} has exceeded max rate of {xxx}

When a Predictive campaign that uses a strict abandon rate reaches that percentage of abandons, Dialer forces the campaign into Power mode. Power mode reduces the abandons until the rate drops below the strict abandon rate. This message appears when Dialer forces the campaign into power mode.

Campaign not found in cache

The listed campaign could not be located in the dialer cache. Please ensure that the campaign is turned on. If the errors persist please contact PureConnect Customer Care.

Campaign Pause

The campaign has been paused. Dialing will continue only when the pause has been lifted.

Campaign Pause lifted

The campaign pause has been lifted from Interaction Administrator and dialing for the campaign will now resume.

Campaign paused due to Blended activity

Predictions made for the listed campaign will now be paused. The number of inbound calls {xxx} is greater than the configured maximum {xxx} for workgroup: {xxx}.

Campaign Server access to the management object failed

The campaign server management interface pointer could not be obtained. Restarting the Interaction Center service may be required to correct this error. If this error persists please contact PureConnect Customer Care.

The Campaign Server subsystem cannot find the interface to store objects.

Campaign Server failed to access the configuration file

The Campaign Server was not able to read or write the xml configuration file 'dialer_config.xml'. Ensure that this file exists, is not read-only, and is parsable by Internet Explorer. Also ensure that there is adequate disk space to write to this file. If this error persists please contact PureConnect Customer Care.

Campaign Server has reached the maximum number of threads allowed

This typically means that all processing threads are hung. Contact PureConnect Customer Care immediately. A restart of the Interaction Center Service may be required.

PureConnect Customer Care recommends that you set trace logging for the Campaign Server to Verbose or All to help diagnose this issue. For more information, see Control Log Verbosity in the Log Viewer help.

Communication with the Campaign Server failed

A failure occurred while registering this Dialer site with the Campaign Server. This typically means that the Campaign Server is not started or active. Please ensure the CIC service has been started and is active on the Central Campaign Server Machine.

Contact does not have a valid Phone Number

The contact associated with Row ID {xxx} does not have a callable phone number.

Database connection error

A connection to the database could not be established. Please verify that the connection: {xxx} is valid before using with any campaign. Typically, this error means that an invalid UDL file has been used or the file that was in use has been deleted.

Date Format could not be parsed

The data passed in for a date value could not be parsed. Date value: {xxx}

Dialer no longer displays this message.

Dialer Tran Server has started

The Dialer Tran Server has started successfully

Dialer Tran Server not started

The Dialer Tran Server could not start due to an error connecting to Notifier.

Dialer Tran Server restarting

The Dialer Tran Server is restarting because too many processing threads are hung.

Contact PureConnect Customer Care immediately. Customer Care recommends that you set trace logging for the Campaign Server to Verbose or All to help diagnose this issue. For more information, see Control Log Verbosity in the Log Viewer help.

Dialing Compliance

Attempt blocked - Automated calls may not be attempted on Manual Calling Server

This message occurs when an agent attempts to place an automated call from a Dialer server with the Manual Calling feature license.

Dialing has been paused due to high CPU utilization

All campaigns have been paused due to a High-CPU utilization issue. Once the CPU utilization drops below the configured point, campaign dialing will continue.

This message occurs when Remoco notifies Dialer of high CPU usage. This issue can result from CPU utilization of Dialer or of all processes.

Dialing has continued due to drop in CPU utilization

All campaign dialing has continued due to the CPU utilization dropping below the configured maximum.

Enabling Period Stats Failed

An error was received while trying to enable period stats for the Workgroup:<{xxx}>. Please ensure this workgroup is active and defined as ACD-enabled.

Dialer no longer displays this message.

Error threshold exceeded

The configured error threshold for a campaign has been exceeded.

A campaign can have up five errors within a short period. If a campaign exceeds this limit, the system pauses the campaign and displays this message.

Event interface not found in GIT

An event interface object was not found in Global Interface Table. Typically this indicates problems with Interaction Administrator. Additional Information: {xxx}

Dialer no longer displays this message.

Forced Power mode restriction has been lifted

Normal dialing has been restored for the listed campaign. The forced power dialing restriction has been removed. Current Abandon rate {xxx} Max Abandon rate of {xxx}

Initialization of campaign '{xxx}' failed.

Campaign Server was unable to commit table properties to the configuration file. Initialization for campaign: {xxx} has been aborted. Error: {xxx}

If this message appears, contact PureConnect Customer Care.

Insert / Update contains no Data

Insert or update operation was aborted because there was no data to process.

This message occurs when an update to a call list fails. Contact PureConnect Customer Care.

Interaction not found in cache

The interaction could not be located in the dialer cache. This may be due to multiple completions being sent from a single scripter for a single call. The action that was attempted on Call ID {xxx} will be ignored.

Line group not active on the server

The line group {xxx} is not active on this CIC server. Please add or enable this line group before trying to start the campaign.

This message occurs when a campaign uses a line group but the line group is disabled or missing for the server. This issue can occur more prominently in environments with multiple Dialer servers and active line groups.

Malformed call list update

A call list update was badly formed: {xxx}

Marking call as Ambiguous

A call that was placed and routed to an agent was not completed. Marking the Interaction as Ambiguous.

Memory allocation failed

A memory allocation failed while trying to create a new object. Please check the memory use on this machine via the Task Manager or Performance Monitor.

New tables have been created for campaign

One or more of the following tables were created for the referenced campaign: {xxx}

This message occurs when Dialer creates database tables in the Dialer database for a campaign.

No Lines Available

There are no lines available for Line group: {xxx}. The current request will be ignored.

Dialer no longer displays this message.

Object identifier not found

Object Identifier was not found while attempting the requested operation. Object Identifier: {xxx}. The operation will be ignored.

Policy Set failed to load

A policy set could not be loaded by the campaign server. The evaluation of this policy will be ignored.

Property load failed

An error occurred while trying to load the property: ('{xxx}') from the Campaign Server. This may indicate that the Campaign Server is down, there is a versioning problem with the dialer binaries or the ODS is not running as the same user as the CCS.

SQL operation failed

An SQL Operation failed to complete. Please check the configuration of the campaign and associated connection.

Check the status of the Dialer database.

Statistics request failed for the following column or statistic: {xxx}

Campaign Server request for statistics data failed for the following column or statistic: {xxx}. Ensure that the DialerStatRepeater subsystem is running and not reporting any errors. Evaluation of this statistic will be ignored for 30 seconds. If this error persists please contact PureConnect Customer Care.

Verify connectivity between ODS and CCS.

Status for agent '{xxx}' changed to an ACD available status before a disposition was received for Callid '{xxx}'. Scripting applications should prohibit agents from becoming available prior to dispositioning outbound calls.

Agent {xxx} has changed to an ACD available status prior to call disposition.

Dialer no longer displays this message.

Table validation failed

The table {xxx} could not be initialized or validated. Ensure that the table structure has not been altered and that it is accessible to Interaction Dialer.

The campaign has recycled

The campaign was recycled by Rule {xxx} of RuleSet {xxx}

OR

The campaign was recycled by user {xxx} using application {xxx} on workstation {xxx}.

The campaign has reset.

The campaign was reset by Rule {xxx} of RuleSet {xxx}

OR

The referenced campaign was reset by user {xxx} on workstation {xxx} using {xxx}.

The campaign pace has been adjusted manually.

The campaign pace was adjusted manually. The new pace was set to {xxx}. Enable configuration change auditing and execute the Audit Report to view configuration changes applied to the system.

Dialer no longer displays this message.

The Query for contacts left in recycle failed

The query to return the number of contacts returned an empty record set.

This message indicates a database error.

The scheduled date is invalid

The scheduled date passed in from the script was invalid. The scheduled time value was equal to {xxx}. Setting the callback for 24 hours from now.

This message can indicate a bad date format from a custom script or application. Verify that the date format uses ISO 8601 format.

Unable to evaluate a rule set item.

An error occurred while attempting to evaluate rule item {xxx} for rule set {xxx}

Unable to retrieve the number of contacts left in the current recycle.

Unable to retrieve the number of contacts left in the current recycle.

Dialer no longer displays this message.

Warnings occurred while processing database update.

Warnings were generated while processing a database update. Error(s): {xxx}

Dialer no longer displays this message.

Workflow status is not 'On' or 'Manual On'. Workflow will not be started.

Campaign status is not 'On' or 'Manual On'. Campaign will not be started.

Dialer no longer displays this message.