02-07-2007 11:57 AM - edited 03-18-2019 06:55 PM
We have Unity 4.2 running Unified messaging and Failover.
We have recently had two occurences where the Primary server "failsover" to the secondary server.
Unity is still running on the Primary and the Secondary has a log something like "Port 1 recieved a call so will failover and take calls"
On the primary their is a log as below
Process AvNotifierMgr
Source AvDiagnostics_MC
No 1433
Compnent AICommon
Level 10
[Thread 7840] Error in Unknown::get_AmisOutbound - >get_AmisOutbound(ppMailUser) Failed - File: E:\Views\CU4.2.0.110\un_Doh1\Doh\Src\AvDohSystemConfiguration.cpp Line: 354 Error: Catastrophic failure Thread: 00001EA0H Instance: 010F9BF0H
Does anyone know what this actually means and what should we do to prevent it occuring again, if this log is relevant.
PS the primary Server also has this log every 15 minutes
Replication of license information failed because the License Logging Service on server \\ESADS01S could not be contacted.
Thanks in advance.
02-08-2007 11:28 AM
Bump
02-08-2007 11:41 AM
Primary server and the licensing logging is just a Microsoft windows license deal.. no need to worry
For your failover answer calls.. somehow, calls are getting through to your secondary server. If you can check the log files on your secondary Unity server and trace back which number is call it and how it got there, that would tell you why. Because what happens is that if a call comes into the secondary failover server, while Primary is "running", then SQL tells Primary to shutdown Unity services and fail to secondary server.
You can also just flip the switch on the failover from Automatic to Manual if it's a constant problem. Manual just means if the primary kicks, you will have to manually start the failover process on the secondary. (sometimes easier and smoother)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: