Cisco Cisco Unified Contact Center Enterprise 9.0(2) Maintenance Manual
See Also
Refer to the Staging Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted, Release
8.x(y) for detailed information about installing SQL Server.
8.x(y) for detailed information about installing SQL Server.
For more information about database networking, refer to the Microsoft SQL Server System
Administrator’s Guide.
Administrator’s Guide.
Manual Intervention to Restart Cisco Unified Intelligent Contact Management Processes After an Exception
Sometimes, manual intervention is required to restart Unified ICM processes after an exception.
This error can be suppressed by setting a registry value.
This error can be suppressed by setting a registry value.
Windows allows you to change the handling of hard error popups that result from application
and system errors. Such errors include no disk in the drive and general protection (GP) faults.
and system errors. Such errors include no disk in the drive and general protection (GP) faults.
Normally, these events cause a hard error popup to be displayed, which requires user intervention
to dispatch. This behavior can be modified so that such errors are logged to the Windows event
log. When the error is logged to the event log, no user intervention is necessary, and the system
provides a default handler for the hard error. You can examine the event log to determine the
cause of the hard error.
to dispatch. This behavior can be modified so that such errors are logged to the Windows event
log. When the error is logged to the event log, no user intervention is necessary, and the system
provides a default handler for the hard error. You can examine the event log to determine the
cause of the hard error.
Note: The "hard errors" referred to in this section could be critical system errors, such as an
I/O error, no disk in drive, and so on. These system errors result in a dialog box that pops up
on the window's console and requires manual intervention by a user. Handling of these types
of system errors (dialog box popup or event log) is controlled by the registry setting listed below.
I/O error, no disk in drive, and so on. These system errors result in a dialog box that pops up
on the window's console and requires manual intervention by a user. Handling of these types
of system errors (dialog box popup or event log) is controlled by the registry setting listed below.
The following registry entry controls the hard error popup handling in Windows:
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
Windows\
ErrorMode
The following are valid values for ErrorMode:
•
Mode 0: This is the default operating mode that serializes the errors and waits for a response.
•
Mode 1: If the error does not come from the system, this is the normal operating mode. If
the error comes from the system, this logs the error to the event log and returns OK to the
hard error. No intervention is required and the popup is not seen.
the error comes from the system, this logs the error to the event log and returns OK to the
hard error. No intervention is required and the popup is not seen.
•
Mode 2: This always logs the error to the event log and returns OK to the hard error. Popups
are not seen.
are not seen.
If you want to suppress the Windows exception, set the registry key value to 2 for the
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode"
registry key.
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode"
registry key.
Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x
69
Chapter 5: General Administration
Optional Administration