I am having an issue here with Unity 4.2.1. We upgraded 4.0(4)SR1 to 4.2.1, SQL2000 SP4 is installed. We now wanted to add failover. We do have the failover license.
First we ran the failoverconfig.exe on the primary, and it returned an error saying can't find the REPLDATA folder. We manually added the folder and it ran ok on the primary.
Now, we ran failoverconfig.exe on secondary(we did manually added the REPLDATA folder as well), the configuration failed at "Waiting for SQL distribution agent to complete". We went back to the primary and see the error is "invalid descriptor index" in UnityDBPublication.
Before the upgrade, Unity is running with MSDE2000 SP3a and we did upgrade to SQL 2000 SP4. If we try to upgrade the SQL again, it won't allow you because we are using SQL already.
Your Unity servers must match identically. Same Unity versions, same sql verions and patches, same OS version and patches. Once this is done, then you can run Failovercfg.exe. You also need to make sure you have DNS or WINS running properly. Failover is utulizing FQDN when calling out to the failover server (SQL). You can force this in the hosts or lmhost file. (servername = ip address)
You will probably have to uninstall failover on both servers and start over. It's the only way to get it right. You may even have to reinstall the failover server if its still bombing out.
Since you've upgraded to 4.2(1), I would make sure to run the DiRT to have a good backup (and stored on a completely seperate server). I would start from scratch. Like the previous reply said, everything has to be identical. I think your secondary server can't be identical since it was never 4.04 and with all that history of patching and SR's. Definitly read the Unity installation guide for 4.05 "with failover" (even though it's 4.2 that you are installing). I would read it twice through before even starting the install. I learned the hard way. lol
It's been a few months since I installed our 4.2(1), but I'm pretty sure I remember reading in that guide something about starting fresh if you are building "with failover".
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...