Anyone any ideas on this one.
I have a cisco unity voicemail only solution with failover with the secondary hosting AD and Exchange 2003.
The same error has occurred twice after a total rebuild.
Both servers build ok with identical features and drive locations.
UTIM runs succesfully on both servers.
Failover wizard runs succesfully on the Primary
Failover wizard fails on the secondary
Failed to verify SQL Configuration Table
Method Iavrdbconnection::Execute(KYNUDCSVM002,CSP_ConfigurationCleanupLastModifiedTime) returned [0x80040e37]
CCO is not much help, there are a few things in the general area which are all known bugs with SQL workarounds but not my specific one.
Google comes up with a few 0x80040e37 errors which are related to AD and Exchange which point to the following registry keys missing, but I don't want to go mucking about with that without cisco intervention.
I have attached the Failover config log file from both servers
Sound like this bug CSCsi64012
ES95 fixes it or copy the failoverconfigwizard.exe from Unity 5.0 disk. Are you running Unity 4.2?
Thanks for your response, I am actually running Unity 5.0, so have the latest wizard. I did look at that bug, and it is similar but not the same.
And you're running the same build or later of 5.x as indicated in the bug notes? Run the Gather Unity System Info (GUSI) to verify. It sounds bug related to occur twice after a rebuild.
We recently upgraded to Unity 5 and had same problem with the failover wizard not completing on the backup server. We opened a TAC case and the engineer was able to fix with these steps.
1. The engineer added entries for the primary and failover servers to the hosts and LmHosts files on both servers.
2. He then created a unique account for the MSSQLSERVER service and the SQLSERVERAGENT to log on as. He stated that this was just his personal preference. Doing this will stop and start Unity services. (Needs to be member of domain users and also a member of local admins group)
3. He then went into SQL enterprise manager and deleted all SQL server registrations, and then created new SQL server registrations and picked the primary server and then added another for the backup server. He did this on both servers.
4. He then reran the wizard on both servers successfully.
Hope this helps
This was the error I was getting.
I would open a Tac case. Sorry that couldn't be more help.
It's actually a 4.x problem also. I ran into this the other week. You have to change around the named pipes in the SQL manager, then it starts to work go through the Failover WIzard.
Check this link out.
I'm getting the same exact error, the only difference is the Server names.
I'm running Unity 5.0.1 ES30.
The FCW runs fine on the Primary Server, but on the Secondary Server it fails, and now i can't start Unity Services on the Secondary Server.
I have run into the exact same problem on a Unity 4.0(3) to Unity 5.0(1) upgrade I am working on. Doing everything in the lab first and this is happening with every attempt.
I have followed the above procedures to try to fix the problem, and have even made the point to do them before ever attempting to run the failover wizard and am still running into it.
Has anyone with this problem had luck getting past it?
I exactly the same problem with Unity 5.0.1:-
Failed to verify SQL Confuration table.
MethodIAvRdbConnection::Execute(LONLDCCCMU02, csp_ConfiurationCleanupLastModifedTime) returned [0x80040e37]:
I logged a support call and they said it was related to Bug ID 'CSCef60341'. Here is how I worked around this issue.
On the primary server open a 'cmd' prompt and execute the following command:
osql -E -d UnityDb -Q "update Configuration set LastModifiedTime=NULL"
Then, Re-run the FailoverConfig wizard on the primary server.
Then, Re-run the FailoverConfig wizard on the Secondary server.
This sequence of events gave me a successful failover configuration on Unity 5.0.1 after 3 days of getting the same error.
super solution, i came across the same problem and issued the command above and the wizard completed on secondary server with no problems.
Not sure if the cmd paste worked for me, but I used it anyways. Another 5.x failover not working.
Ran the fix, but then replication was not working. Turns out the Unity DBs in SQL have to be in the exact same location also or it will not work. bah!
I received this exact error attempting to complete an upgrade from 4.2(1) to 5.0(1) this evening. The steps in your post resolved the issue. THANK YOU!!
you saved ours lives,
we spent some days without knowing the reason of this error.
we execute the commands and the failover
is working now!!!!!
THANKS A LOT !!!!!
I ran into the same problem on Unity v7.0(2), which would sort of mean this problem is still around even in Unity v7.x
Anyway used the same fix process as above and failover config completed on both servers.
Thanks again Martin for starting this post..........