Table Of Contents
Error Messages
About Error Messages
Startup Error Messages
Cisco Unity Fails To Start
Browser and Windows Error Messages
E-mail and Voice Error Messages
AMIS Error Messages
Notifier Errors
AMIS Conversation Errors
Exchange 5.5 Directory Monitor Event Log Errors
Active Directory Monitor Event Log Errors
Error Messages
About Error Messages
Error message problems fall into these categories:
Startup Error Messages
Use the information in this section to troubleshoot errors that occur when starting either the Cisco Unity software or server.
Cisco Unity Fails To Start
Error Message At least one service or driver failed during system
startup.
Explanation This message is displayed when one or more of the Cisco Unity
services or the services required by Cisco Unity do not start.
Action To troubleshoot this problem:
•Check the startup settings for the services as described in the procedure, To check the service startup settings.
•Check for errors listed in the Application and System Event logs as described in the procedure, To look for errors in the Application and System Event logs.
To check the service startup settings
Do the steps below for each of the following services:
•These Cisco Unity services: AvCsGateway, AvCsMgr, AvGaenSvr, and AvMalSvr
•Dialogic
•IIS Admin Service
•Each Microsoft Exchange service
•World Wide Web Publishing Service
Step 1 In the Control Panel Services dialog box, click the service, then click Startup.
Step 2 Verify that Manual is selected for AvCsMgr, AvUMRSyncSvr, and AvRepDirSvrSvc.
Step 3 Verify that Automatic is selected for the other services.
Step 4 Verify that the domain name, user name, and password in the account assigned to the service are correct and that the account has the following rights and permissions (note however that AvDirChangeWriter does not require these permissions):
Windows domain permissions
|
•Member of the Domain Admins group
•Member of the Local Administrators group
|
Windows user rights
|
•Log on locally
•Act as a part of the operating system
•Log on as a service
|
The account assigned to any of the Cisco Unity services must also have Services Account Administration permissions for the site and configuration containers.
To look for errors in the Application and System Event logs
Because startup events occur in rapid succession, when you look in the Application or System Event log for information about these events, you will be looking for the first event in a series of events that probably occurred just seconds apart. Locate the first error in the startup attempt. Subsequent errors may have been caused by the first error. If you can determine the cause and fix the first error, then shut down and restart the Cisco Unity server. All subsequent errors may be resolved by fixing the first.
Step 1 On the Windows Start menu, click Programs > Administrative Tools > Event Viewer.
Step 2 In the Application Event log, look at the Date and Time columns to find the first event in the current startup attempt.
Step 3 Once you find the first event in the startup attempt, look for the first error that occurred after it. If no errors appear in the startup attempt, skip to Step 5.
Step 4 Look at the value in the Source column for the first error and then for any subsequent errors in the startup attempt.
If the name in the source begins with the letters "Av," then double-click the error to display a dialog box containing additional information that may help you solve the problem.
If the source is Doh_Mc, then Exchange probably is not running. Start Exchange, then try again to start Cisco Unity.
If the Source column for an error contains any other value, or if you cannot determine the cause of the problem, contact the Cisco Technical Assistance Center (TAC).
Step 5 In the System Event log, look at the Date and Time columns to find the first event in the current startup attempt.
Step 6 Once you find the first event in this startup attempt, look for the first error that occurred after it.
If no errors appear in the System Event log, contact Cisco TAC.
Step 7 Look at the value in the Source column for the first error and for any subsequent errors in the startup attempt.
If the value is Dlgc_log or DlgcDcm, then the problem is with the installation or configuration of the Dialogic voice or fax cards. Double-click the event error to display additional information that may help you solve the problem. When a Dialogic service fails to start, you may need to check the IRQ settings, switches, jumpers, and rotary dials on each card, as appropriate. When the Cisco Unity server contains more than one Dialogic voice card, you may also need to check the cable that connects the cards. See the "Installing Voice Cards" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide for additional information. The Cisco Unity Installation Guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm.
If the Source column for an error has any other value, contact Cisco TAC.
To change LPT1 port settings
Step 1 On the Windows Start menu, click Programs > Administrative Tools > Computer Management.
Step 2 Double-click Device Manager.
Step 3 Expand Ports and double-click LPT1.
Step 4 Click Port Settings.
Step 5 Click Try Not To Use an Interrupt.
Step 6 Click OK.
Browser and Windows Error Messages
Cisco Unity administrators or subscribers may see the following error messages:
Error Message Access denied. Your class of service prohibits you
from accessing the System Administration Web pages.
Explanation When this message appears during a logon attempt to the
Cisco Unity Administrator, one of the following has occurred:
•The class of service for the logon account has been changed. See the system administrator for more information.
•The Cisco Unity class of service has been changed to subscriber for everyone who previously had administrator privileges. There is no longer a Cisco Unity account for the administrator class of service.
Action Do the procedure, To temporarily associate an Exchange account with
the Administrator class of service.
To temporarily associate an Exchange account with the Administrator class of service
Step 1 In the Exchange Administrator, go to the recipients for your site, and locate the Example Administrator recipient.
Step 2 Double-click the Example Administrator recipient.
Step 3 Associate the Example Administrator recipient with the Windows account that you are logged on with.
Step 4 Log off and then log back on again to Cisco Unity.
Step 5 Assign accounts as needed to the administrator class of service.
Step 6 Log off of Cisco Unity.
Step 7 In the Exchange Administrator, remove your account association with the Example Administrator account.
Under normal circumstances, the Example Administrator should not be associated with a Windows account.
Error Message Access denied. You cannot access the System
Administration Web pages. Cisco Unity is not running.
Explanation When this message appears, Cisco Unity is not running.
Cisco Unity must be running before anyone can log on to the Cisco Unity
Administrator.
Action Start Cisco Unity.
Error Message Access denied. You cannot access the System
Administration web pages. There are too many active sessions.
Explanation When this message appears, the maximum limit of five concurrent
system administration sessions has been reached.
Action Wait for an active session to be closed and then try again later.
Error Message Access denied. Your Windows Domain Account
[Domain\login] is not associated with a Cisco Unity subscriber.
Explanation When this message appears during a logon attempt to the
Cisco Unity Administrator, an invalid user name or password is being used.
Action Contact the system administrator to confirm the user name and
password.
Error Message The Windows NT account you are logged on with is not
associated with a Cisco Unity subscriber.
Explanation Subscribers will get this error message when attempting to access
the ActiveAssistant or the Visual Messaging Interface (VMI), or when
attempting a TRaP (telephone recording and playback) connection from
ViewMail for Outlook if they are not authenticated under a domain account
that is linked to their Exchange mailbox, either directly or indirectly through
the Active Directory SidHistory property.
Action Run the GrantUnityAccess utility to associate the domain account with
the subscriber account. GrantUnityAccess is a command line utility and can be
found on the Cisco Unity server in the folder in which Cisco Unity was
installed (the default location is C:\CommServer). Specify the following
arguments:
GrantUnityAccess -u <Domain>\<UserAlias> -s <UnitySubscriberAlias>
For information about the arguments, enter
Error Message Additional users cannot be assigned to the class of
service associated with the selected subscriber template. You
have reached the license limit for one or more of the features
enabled by the class of service.
Explanation Class of service can be used to restrict which licensed features are
available to subscribers. If all available licenses for a feature are in use by a
class of service, no new subscribers can be added to that class of service.
Action Go to the Licensed Features page for the class of service associated
with the subscriber template. Determine if any of the licensed features used by
that class of service are out of licenses, and if so, obtain sufficient additional
licenses to meet subscriber needs. As a temporary measure until additional
licenses are available, you can change the class of service associated with the
selected subscriber template.
Error Message Failed to perform fetch against AvXml.dll. Check
AvXml virtual directory settings in IIS for proper permissions
and execute access. See the Troubleshooting Guide for details.
Explanation This error may appear when accessing the Status Monitor page.
Action Do the procedure, To set up access to the Status Monitor after an
upgrade.
Error Message This page cannot be displayed. HTTP 403.1 Forbidden
execute access forbidden.
Explanation This error may appear when Status Monitor access is attempted
for the first time after an upgrade.
Action Do the procedure, To set up access to the Status Monitor after an
upgrade.
To set up access to the Status Monitor after an upgrade
Step 1 On the Windows Start menu, click Programs > Administrative Tools > Internet Services Manager.
Step 2 Click the Default Web Site folder, then locate the Status folder.
Step 3 Right-click the Status folder and go to Properties.
Step 4 Click the Virtual Directory tab.
Step 5 Set Execute Permissions to Scripts Only.
Step 6 Click OK.
E-mail and Voice Error Messages
By default, Cisco Unity sends e-mail to the System Event Messages public distribution list when certain critical errors occur. Cisco Unity administrators can use the Event Notification utility to send e-mail and/or voice mail to other subscribers or distribution lists when an error occurs. Cisco Unity administrators or subscribers may see the following error messages:
Error Message A conversation error has occurred.
Explanation A conversation error has occurred, sending a caller to the fail safe
conversation.
Action Refer to the Windows Application Event log for more information
about the error. If you are unable to determine the source of the problem from
the information in the Application Event log, contact Cisco TAC.
Error Message Account locked—logon attempt limit reached.
Explanation An account is locked because the limit of unsuccessful phone
logon attempts was reached.
Action Go to the Subscribers > Subscribers > Account page for the
subscriber, and uncheck the Cisco Unity Account Status box to unlock the
account. You can also refer to the Windows Application Event log for more
information about the error.
Error Message All Ports Busy notification.
Explanation The voice server detected that all ports that are set to answer calls
are busy. In this circumstance, incoming calls receive a busy signal and
subscribers are unable to access the Cisco Unity conversation.
Action Generate a port usage report for the ports set to answer calls.
If the value of Percentage Of Ports Used exceeds 70 percent usage during peak periods, go to the System > Ports page in the Cisco Unity Administrator and review the port configuration to determine if additional answer ports are required, or if other adjustments to the port settings are needed. For more information, see the "Voice Port Settings" section in the "System Settings" chapter of the Cisco Unity System Administration Guide. The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.
Error Message One or more Exchange servers in the site are
unavailable.
Explanation The Cisco Unity server detected that one or more Exchange
servers are unavailable.
Action Restart the Exchange server(s), and refer to the Windows Application
Event log for more information about the error.
Error Message Possible phone system integration failure.
Explanation The Cisco Unity server received an inbound call with no phone
system integration information.
Action Refer to the Windows Application Event log for more information. If
you are unable to determine the source of the problem from the information in
the Application Event log, contact Cisco TAC.
Error Message System event notification.
Explanation Notification of a system event was attempted, but the notification
text or voice message is missing or corrupt.
Action Refer to the Windows Application Event log for more information, and
review the notification message settings for the Event Notification utility. If
you are unable to determine the source of the problem from the information in
the Application Event log, contact Cisco TAC.
Error Message That e-mail cannot be played at this time.
Explanation All of the licensed text-to-speech resources are in use.
Action Subscribers can try again later, or you may need to add more licenses.
Error Message Voice server hard disk almost full.
Explanation The Cisco Unity server hard disk is almost full. System logging
and report data generation are terminated to conserve space.
Action Reclaim space on the hard disk to avoid potential loss of new messages
and to resume logging and report generation. The Example Administrator
account, which Cisco Unity creates during installation, serves as a default
message recipient for the Unaddressed Messages and System Event Messages
distribution lists. If you have not assigned another subscriber to these
distribution lists, be sure to monitor the Example Administrator account and
forward or delete the messages sent to this account as appropriate. For
subscribers on the Unaddressed Messages public distribution list, create a
separate Inbox folder for returned messages. Then create a rule that
automatically moves messages sent by the Cisco Unity Messaging System
account from the Inbox to the returned messages folder.
Caution Do not delete the Example Administrator unless you have assigned another subscriber to the Unaddressed Messages and System Event Messages distribution lists. Following Cisco Unity installation, the only member of these distribution lists by default is the Example Administrator. If these distribution lists contain no members, messages sent to them will be lost.
Error Message Voice server restart.
Explanation The Cisco Unity server stopped responding and was restarted.
Action Refer to the Windows Application Event log for more information
about the error. If you are unable to determine the source of the problem from
the information in the Application Event log, contact Cisco TAC.
AMIS Error Messages
Cisco Unity logs AMIS-related errors to the Windows Application Event log. The Cisco Unity components that log the AMIS-related errors are the Notifier, the Conversation, and a sub-component of the Conversation called Conv AMIS. The component name is listed as the Source in the event log properties for an event. The Notifier has the Source AvNotifier_MC, and the Conversation has the Source AvConvMsg_MC. When troubleshooting a problem with Cisco TAC, you may need to use the Cisco Unity Diagnostic tool to turn on micro traces for these components. Additionally, you may want to set up the Event Notification utility so that you are notified when a particular error event is logged. To do that, you need to know the Event ID and the Source component that are listed in the event log.
This section provides a description of each AMIS-related error message, the Source of the error, a brief suggestion for fixing the error, and where possible, the Event ID.
Depending on the error, you may need to refer to the following for additional troubleshooting information:
•The "Troubleshooting Problems with Outbound AMIS Messages" section.
•White Paper: AMIS Analog Networking Definitions, which is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/amis.htm.
This white paper contains detailed information about the touchtones that are transmitted during an AMIS call.
Notifier Errors
In the event log, Notifier error messages have AvNotifier_MC as the Source.
Error Message Event ID: 1062
Error: AMIS outbound mailbox contains messages more than 24 hours
old.
Explanation At least one AMIS outbound message has been in the UAmis
mailbox for more than 24 hours and therefore has not been delivered.
Action Review the AMIS schedule and port assignments to determine if
additional resources (time and/or ports) should be dedicated to AMIS message
traffic. If there are sufficient resources, use the Cisco Unity Diagnostic tool to
run micro traces on the following components: Notifier traces 13, 19, 24, 26,
and 28, and Exchange Monitor trace 13. To send messages that are in the
UAmis mailbox immediately, set up the AMIS schedule so that it is active. You
may also need to use Outlook to mark the message as read and then unread to
trigger a new message event that the Exchange Monitor detects.
Error Message Event ID: 1063
Error: AMIS message from <sender> to <intended recipient> cannot
be delivered.
Explanation An AMIS message was undeliverable due to rejection by the
destination node. Reasons for rejection include rejection of the Cisco Unity
node ID or rejection of an individual extension.
Action Refer to the Non-Delivery Receipt (NDR) sent to the sending
subscriber. Confirm that the remote mailbox number of the intended recipient
is correct. If the remote mailbox number is correct, confirm that the Node ID
on the Primary Locations page is accepted by the remote voice messaging
system. If the recipient is an AMIS subscriber, confirm that the extension
address listed in Exchange is correct. If the Node ID is correct, use the
Cisco Unity Diagnostic tool to run micro traces on Notifier traces 13, 19, 24,
26, and 28, and then send a test message to the same location and remote
mailbox number.
Error Message Event ID: 1064
Error: AMIS call to location <number> was not answered.
Explanation On an AMIS outbound call, Cisco Unity either received no answer
too many times, or reached a line that was busy too many times, as defined on
the AMIS Delivery Options page in the Cisco Unity Administrator.
Action Refer to the Non-Delivery Receipt (NDR) sent to the sending
subscriber. In the Cisco Unity Administrator, go to the Network > Delivery
Location > Profile page of the AMIS location, and confirm the delivery phone
number. Go to the AMIS Delivery Options page, and confirm that the number
of times that a call is retried is sufficient. If the delivery phone number and
AMIS Delivery Options are valid, use a phone to dial the delivery phone
number to see if the remote voice messaging system answers.
Error Message Event ID: 1065
Error: AMIS location with DTMF ID = <number> was disabled. Cannot
get AMIS reply from this location.
Explanation On an AMIS outbound call, either a human, a non-AMIS
compliant voice messaging system, or an answering machine answered the
call. Technically, the call was answered, but the recipient either hung up or did
not respond with the appropriate touchtone.
Action In the Cisco Unity Administrator, go to the Network > Delivery
Location > Profile page of the AMIS location, and confirm that the delivery
phone number is correct. If the number seems to be correct, then use a phone
to dial the delivery phone number to see if the remote voice messaging system
answers. When the problem is resolved, go to the Network > Delivery
Location > Profile page of the AMIS location, and uncheck the Disable
Outbound Message Delivery To This AMIS Location check box.
Error Message Event ID: 1066
Error: AMIS restriction table not found. Message delivered.
Explanation An AMIS outbound message was sent, despite the absence of an
AMIS-specific restriction table.
Action In the Cisco Unity Administrator, create a restriction table to manage
the phone numbers used for outbound AMIS calls. Specify the restriction table
on the Network > AMIS Options > Delivery Options page.
AMIS Conversation Errors
In the event log, Conversation error messages have AvConvMsg_MC as the Source. The sub-component Conv AMIS logs an error, and then the Conversation adds additional error text to the error event. When this occurs, the Event ID is overwritten with 10002; therefore, these errors do not currently have unique Event IDs.
Error Message Event ID: 10002
Error: AMIS message from <sender> to <intended recipient> cannot
be delivered.
Explanation An AMIS message was undeliverable due to rejection by the
destination node. Reasons for rejection include rejection of the Cisco Unity
node ID or rejection of an individual extension.
Action Refer to the Non-Delivery Receipt (NDR) sent to the sending
subscriber. Confirm that the remote mailbox number of the intended recipient
is correct. If the remote mailbox number is correct, confirm that the Node ID
on the Primary Locations page is accepted by the remote voice messaging
system. If the recipient is an AMIS subscriber, confirm that the extension
address listed in Exchange is correct. Another possible reason for the rejection
of an individual extension is that the voice mailbox for the recipient is full.
Error Message Event ID: 10002
Error: Location <number> not found. Inbound AMIS message
rejected.
Explanation A remote AMIS node tried to deliver messages to Cisco Unity, but
was rejected because the node ID did not correspond to an AMIS delivery
location in Cisco Unity.
Action In the Cisco Unity Administrator, go to the Network > Delivery
Locations page and confirm that there is an AMIS delivery location for the
remote voice messaging system. If there is a delivery location, then confirm
that the Node ID on the Network > Delivery Locations > Profile page is
exactly what the remote voice messaging system is sending.
Error Message Event ID: 10002
Error: Extension <number> not found. Inbound AMIS message
rejected.
Explanation A remote AMIS node tried to deliver a message, but it was
rejected because the intended message recipient mailbox does not correspond
to the primary call handler of a Cisco Unity subscriber.
Action The sender will receive an NDR and will need to confirm the
subscriber extension. Be sure to inform the users of the remote voice
messaging system that even though public distribution lists and Cisco Unity
call handlers and interview handlers have extensions, Cisco Unity accepts
AMIS messages only for subscribers.
Error Message Event ID: 10002
Error: Inbound AMIS message on Port <number> was terminated after
<number> seconds.
Explanation An inbound AMIS message transmission was terminated
unexpectedly.
Error Message Event ID: 10002
AMIS location <number> disabled.
Explanation On an AMIS outbound call, either a human, a non-AMIS
compliant voice messaging system, or an answering machine answered the
call.
Action In the Cisco Unity Administrator, go to the Network > Delivery
Location > Profile page of the AMIS location, and confirm the delivery phone
number. If the number is correct, then the problem is most likely with the
remote voice messaging system. When the problem is resolved, go to the
Network > Delivery Location > Profile page of the AMIS location, and
uncheck the Disable Outbound Message Delivery To This AMIS Location
check box.
Exchange 5.5 Directory Monitor Event Log Errors
The directory monitor writes several messages to the Windows Application Event Log. This section lists the error messages logged by the directory monitor and provides a brief suggestion for fixing each error.
In the event log, Exchange 5.5 directory monitor error messages have AvDirSynch_MC as the Source.
Error Message Event ID 1000
Error: Component diagnostic setting: X not found. Diagnostics
are disabled.
Explanation This error indicates that diagnostics are not available.
Recommended Action Confirm that the Log Manager service, AvLogMgrSvr, is
started.
Error Message Event ID 1009
Error: Cocreate of log manager failed.
Explanation The log manager service, AvLogMgrSvr.dll, failed to register.
Recommended Action In the directory in which Cisco Unity is installed (the
default is C:\CommServer), run Regsvr32.exe to register AvLogMgrSvr.dll.
Error Message Event ID 1010
Error: Cocreate of DCQ failed.
Explanation The service AvDcqWriterSvr.dll failed to register.
Recommended Action In the directory in which Cisco Unity is installed (the
default is C:\CommServer), run Regsvr32.exe to register AvDcqWriterSvr.dll.
Error Message Event ID 1011
Error: Cocreate of AvRdbSvr failed.
Explanation The service AvRdbSvr.dll failed to register.
Recommended Action In the directory in which Cisco Unity is installed (the
default is C:\CommServer), run Regsvr32.exe to register AvRdbSvr.dll.
Error Message Event ID 1024
Error: Failed loading configuration due to error retrieving
server name.
Explanation The directory monitor could not retrieve the name of the local
computer or of the cluster it belongs to.
Recommended Action Contact Cisco TAC.
Error Message Event ID 1028
Error: Failed loading configuration due to error retrieving
custom container name.
Explanation The directory monitor failed to get the custom container name
from the resource loader.
Recommended Action Contact Cisco TAC.
Error Message Event ID 1029
Error: Failed loading configuration due to error connecting to
LDAP while performing the first time directory initialization.
Explanation The directory monitor failed to connect to Exchange.
Recommended Action Do the following:
•Confirm that the LDAP port in the registry is set correctly.
•Confirm that the Exchange server in the registry is set correctly.
•Confirm that there is connectivity between Cisco Unity and the Exchange server.
•Confirm that Exchange services are running on the Cisco Unity server.
•Confirm that the directory monitor service account is configured correctly.
Error Message Event ID 1030
Error: Failed loading configuration due to error connecting to
LDAP while getting server DN.
Explanation The directory monitor failed to connect to Exchange.
Recommended Action Do the following:
•Confirm that the LDAP port in the registry is set correctly.
•Confirm that the Exchange server in the registry is set correctly.
•Confirm that there is connectivity between Cisco Unity and the Exchange server.
•Confirm that Exchange services are running on the Cisco Unity server.
•Confirm that the directory monitor service account is configured correctly.
Error Message Event ID 1031
Error: Failed loading configuration due to error while getting
server DN.
Explanation The directory monitor failed to connect to Exchange.
Recommended Action Do the following:
•Confirm that the LDAP port in the registry is set correctly.
•Confirm that the Exchange server in the registry is set correctly.
•Confirm that there is connectivity between Cisco Unity and the Exchange server.
•Confirm that Exchange services are running on the Cisco Unity server.
•Confirm that the directory monitor service account is configured correctly.
Active Directory Monitor Event Log Errors
The Active Directory monitor writes several messages to the Windows Application Event Log. This section lists the error messages logged by the directory monitor and provides a brief suggestion for fixing each error.
In the event log, Active Directory monitor error messages have AvDirSynch_MC as the Source.
Error Message Event ID 1000
Error: Component diagnostic setting: X not found. Diagnostics
are disabled.
Explanation This error indicates that diagnostics are not available.
Recommended Action Confirm that the Log Manager service, AvLogMgrSvr, is
started.
Error Message Event ID 1009
Error: Cocreate of log manager failed.
Explanation The log manager service, AvLogMgrSvr.dll, failed to register.
Recommended Action In the directory in which Cisco Unity is installed (the
default is C:\CommServer), run Regsvr32.exe to register AvLogMgrSvr.dll.
Error Message Event ID 1010
Error: Cocreate of DCQ failed.
Explanation The service AvDcqWriterSvr.dll failed to register.
Recommended Action In the directory in which Cisco Unity is installed (the
default is C:\CommServer), run Regsvr32.exe to register AvDcqWriterSvr.dll.
Error Message Event ID 1011
Error: Cocreate of AvRdbSvr failed.
Explanation The service AvRdbSvr.dll failed to register.
Recommended Action In the directory in which Cisco Unity is installed (the
default is C:\CommServer), run Regsvr32.exe to register AvRdbSvr.dll.
Error Message Event ID 1062
Error: Domain Controller <domain controller name> is down.
Stopping monitoring domain <domain name> until total
resynchronization is performed.
Explanation The monitor connects to a domain controller (DC) to collect
information about objects associated with the domain. The monitor keeps
using the same DC until it detects an error. Connecting to a new DC requires
a full synchronization in order to maintain consistency. Because a full
synchronization may have a heavy impact on the network, the monitor does
not execute it automatically. Therefore monitoring is suspended until a full
synchronization is requested.
Recommended Action Force a full synchronization. See the following
procedure, To force a full synchronization.
To force a full synchronization
Step 1 On the Cisco Unity server, browse to the location where Cisco Unity is installed (the default is C:\CommServer), and then browse to the TechTools folder.
Step 2 Run DohPropTest.exe.
Step 3 In the DohPropTest Logon dialog box, leave the Password box empty, and click OK.
Step 4 On the warning dialog box, click Ignore to start the read-only mode of DohPropTest.
Step 5 Click AD Monitor. The Directory Monitor window appears.
Step 6 Click TotalResync.
Step 7 Close the Directory Monitor window.
Step 8 Close DohPropTest.
Error Message Event ID 1064
Error: Domain Controller <domain controller name> has been
restored from backup. Stopping monitoring of domain <domain
name> until total resynchronization is performed.
Explanation .Connecting to a DC that has been restored from backup is similar
to connecting to a DC for failover.
Recommended Action Force a full synchronization. See the procedure, To force
a full synchronization for details.