This document explains how to troubleshoot the error message:
failed to configure sql replication that appears
when you run the Cisco Unity Failover Configuration Wizard on a Cisco Unity
There are no specific requirements for this document.
The information in this document is based on the Cisco Unity 4.x.
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
When the Cisco Unity Failover Configuration Wizard is run on a Ciso
Unity server, this error message is received:
failed to configure sql replication
In the diag-failoverconfig.txt, you see
this error message:
Error [0x80040afc] : [Microsoft][ODBC SQL Server Driver][SQL Server]
Could not find stored procedure
When the query exec sp_dboption
'UnityDb','published',false is run in the SQL Query Analyzer,
this error is returned:
The Distributor has not been installed correctly.
Could not disable database for publishing.
On the Unity server, go to SQL Enterprise Manager,
right-click on the server, and select Properties. Under the
Replication tab, the option to Disable Publishing and
Distribution is greyed out. This implies that the SQL publishing is not started
or configured correctly, which in turn causes the SQL replication failure.
Use this solution to solve the problem:
Go to Start > Programs >
Microsoft SQL Server > Enterprise Manager.
Right-click on the Server, then select
Properties. Under the Replication tab, choose
Configure for Publishing and Distribution.
At this point, if you receive a message that states
SQL Server replication does not support
nicknames, then perform these steps:
Go back to the server name (probably called local), and
right-click Delete SQL Server Registration.
Right-click on the SQL-Group, then select
New SQL Server Registration and add the name of the Unity
If you do not receive an error message, go to step
Click Next. In the next window, choose the
Make <Servername> it's own distributor; SQL server will create a
distribution database and log radio button.
Click Next until you see the Customize
the Configuration window. Choose use the default
settings and click Next.
Click Finish. You receive a message that states
SQL Server Enterprise Manager successfully enabled
<servername> as the distributor for <servername>.
Click OK and then Close.
This issue can also occur when the SQL Server is renamed after it was
originally installed. Therefore, the SQL Server name (old server name) does not
match the new machine name (new server name) as mentioned in
Failover Error Messages. In order to resolve the issue, perform the
steps mentioned in the Problem Description and Workaround sections under
Error: Could not change the Publisher because the subscription has been
In order to verify, run the query exec sp_dboption
'UnityDb','published',false in the SQL Query Analyzer. There
should not be any error messages that appear. You can run the Cisco Unity
Failover Configuration Wizard successfully now.
Note: If the wizard fails again with the error
[SQL-DMO]Invalid to alter this property after the distributor
has been installed in the
diag-failoverconfig.txt, you need to disable any
Antivirus application running on the server and then run the wizard
Use this solution in order to solve the problem:
Change the logon for MSSQLSERVER and
SQLSERVERAGENT to local system.
Open SQL Server Enterprise Manager on the secondary server.
Expand the tree to the SQL server.
Right-click and choose Delete SQL Server
Registration as the local host.
Right-click SQL Server Group and choose New SQL Server
Registration. Create both the registration for primary and secondary
servers in both the servers.
Reboot both servers.
Change the logon for MSSQLSERVER and SQLSERVERAGENT back to an
account that had domain admins.
Reboot both servers.
When you attempt to configure Cisco Unity Failover, this message
appears on both the primary and secondary servers:
Failed to configure SQL Replication
On the secondary server, this error message appears:
-Pure Virtual FunctionalCall.
Complete these steps:
On the primary Cisco Unity server, choose Start
> Programs > Microsoft SQL Server >
Client Network Utility.
On the General tab, confirm that Enables protocols by
order includes TCP/IP and Named
On the Alias tab, click the Add button, enter the
machine name of the secondary Cisco Unity server in the Server
Alias field, and then click OK.
Repeat steps one through three on the secondary Cisco Unity
server, but in step three, enter the machine name of the primary Cisco Unity
server in the Server Alias field.
Re-run the failover configuration wizard and see if the issue is
resolved. If the Failed to configure SQL replication for Cisco
Unity Failover error message appears, complete these
On the Windows Start menu, click
Programs > Microsoft SQL Server >
In the Connect to SQL Server dialog box, enter
In the SQL Server field, enter the name of the
Cisco Unity server.
Under Connect Using, click Windows
In the SQL Query Analyzer window, enter select
@@servername, press Enter, and click the
Execute Query button. The lower pane of the window displays
the old server name, which you will enter in step four.
Enter exec sp_dropserver
the name you found in Step 3, and press Enter. Note that you
must use single quotation marks, as shown.
Enter exec sp_addserver
'<new_server_name>', 'local', and
press Enter. Note that you must use single quotation marks as
Click the Execute Query button.
In the system tray, right-click the MSSQLServer
icon, and click MSSQLServer - Stop.
When prompted to confirm whether the MSSQLServer
service can be stopped, click Yes.
When prompted to confirm whether all dependent services can be
stopped, click Yes.
In the AvCsTrayStatus dialog box, click OK.
When the MSSQLServer icon indicates that the SQL
Server has restarted, select select @@servername in the Query
window, and click the Execute Query button in order to verify
the new server name.
Close the SQL Query Analyzer window.
In the system tray, right-click the Cisco Unity icon, and click