Jeff--
Old post, however, I thought I'd throw in an added twist.
I have a customer with two separate Unity Servers. Both are Unity 4.0(4)ES20/Exchange. They are linked using Cisco Unity Digital Networking, so they are using the same Active Directory as the global directory. Each server is integrated to it's own local Exchange 2003 Information Store. Each server is at a site with a local DC/GC.
TAC SR is 600538043 if you care to take a closer look. I've got logfiles and traces and EVTs and whatnot attached to the case.
We have had at least one Unity server outage per day this week. The "outage" varies a bit, I'm seeing a mixture of two major different issues:
1. AvCsMgr barfing all over the place, then usually crashing with a DrWatson.
2. Unity Voice Ports quit responding. We are CCM-integrated at both sites (different CCM clusters) , and we will get what seems to be about 20-45 minutes of ring no answer (indicating CCM thinks the ports are still registered). In Event Viewer on Unity, eventually you will see the ports dropping off one by one. Eventually they are all off, and suddenly CCM realizes this and shows them all registering (all at once, which is very different than what Unity see)s.
The two symptoms above seems to flip-flop -- one time it's issue #1, the next it's issue #2. Both are usually solved by a quick stop/start of Unity using the system tray tool. Sometimes with AvCsMgr, I need to use the kill.exe tool to kill all Av* services, then restart Unity.
There are a number of issues we see that coincide with the above:
1. MALEx errors, but I believe these have been eliminated since TAC provided me ES20.
2. AvCsMgr barfing all over the place (all kinds of different errors)
3. Occasional MSSQLSERVER errors from MSDE 2000/SQL 2000 complaining of too many queries at once ("optimized for 8, 13 attempted") or some such lingo
4. Occasional AvRdbSvr errors (which drove me to this post to begin with).
5. If we wait long enough, TSP errors indicating Unity thinks a port has de-registered.
During the most recent incident (a few hours ago), AvCsMgr threw errors for maybe 30 minutes or so -- then eventually DrWatson'd. The reason I am posting to this thread, is that in the micro traces for AvCsMgr I see the exact same error the original poster mentions: Failure (by AvCsMgr) to connect to UnityDb.
Two separate Unity's, separate mailstores, separate DC/GC servers ... but similar issues. My gut tells me this is something global, maybe an AD group policy or some such nonsense. Would you agree with this line of reasoning? Have you seen anything similar with other customers, or anything else I can check or provide more information for?
Thanks, as always.
-jd
