04-25-2005 06:01 PM - edited 03-20-2019 05:46 AM
Unity 4.0(4)SR1 Voicemail only. We had an issue with Unity not responding. Could not view system admin page or status monitor. Unity was running via services and via system tray. Unity Registered successfully with CallManager. We were able to dial voicemail ports with no answer to Unity, constant ring. In the Event viewer application log I only noticed one error that was noticeable below. Eventually rebooted Unity and everything tested ok. Any ideas?
Event Type: Error
Event Source: CiscoUnity_AvRdbSvr
Event Category: Startup
Event ID: 21000
Date:4/25/2005
Time:17:13:30 PM
User: N/A
Computer: Test
Description:
Failed connecting to underlying database using: provider=SQLOLEDB;driver={SQL Server};Data Source=TAC-TOR1UNTY3;Initial Catalog=UnityDb;uid=Administrator;pwd=<?}: 80004005
For more information, click: http://www.CiscoUnitySupport.com/find.php
04-25-2005 07:42 PM
If you look on system logs, do you see any NETLOGON 5719 errors? If SQL server is not started due to account logon, then Unity won't be able to connect to "Initial Catalog=UnityDb".
11-15-2005 06:16 AM
What could cause a generally stable Unity Server to lose connection with SQL in this manner?
I just had the same thing happen to me & the same error and behavior. Reboot fixed the issue.
I'm more concerned with the WHY, then the what. Any ideas?
Thanks
Matt
03-23-2006 10:03 AM
I had this issue as well and had to reboot to clear.
Unity 4.0(4) SR1, VM Only.
Nothing going on the server at the time.
Happened at 4:15am out of the blue, nothing else in logs at that time and from 4:15am and on we had these errors.
Event Type: Error
Event Source: CiscoUnity_AvRdbSvr
Event Category: Startup
Event ID: 21000
Date: 3/21/2006
Time: 4:15:35 AM
User: N/A
Computer: UNITY
Description:
Failed connecting to underlying database using: provider=SQLOLEDB;driver={SQL Server};Data Source=UNITY;Initial Catalog=UnityDb;Integrated Security=SSPI: 80004005
For more information, click: http://www.CiscoUnitySupport.com/find.php
03-23-2006 10:11 PM
Anyone have ideas on how to fix this?
03-24-2006 09:29 AM
Hi -
I don't know your specific environments, so I would check with TAC to see if this applies to you - http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCee49288&cco_product=Cisco+Unity+Unified+Messaging&fset=&swver=&keyw=SQLOLEDB&target=&train=
Ginger
03-24-2006 12:25 PM
Thanks. I searched bug but not on those keywords.
Applied the workaround for Enterprise manager (using server name instead of local) but they weren't on Windows 2003 and did not have failover but will see if that helps. Will be a few months probably since this happened back in december once and second time a few days ago. Still checking out some other items I noticed in the event logs a few hours before these errors.
03-26-2006 02:32 PM
Well, that workaround did not work. Problem happened again today. I think it ierss being triggered by something happening with POP3/IMAP4SVC attempted connections - see my other forum post. Am seeing 2-3 unity servers at different customers exhibit similar behavior past few days.
05-01-2007 07:58 AM
We recently encountered the same error message on our primary Unity server. The Unity version is 4.0(4)SR1. I tried searching the bug toolkit without any success. In the process of opening a TAC Case but anyone have any updated cause and fix for this issue?
02-29-2008 11:58 AM
Did you ever get this resolved? I am running into the same problem.
Chris
06-16-2008 08:55 AM
Anyone find a fix for this yet? Having the same issue with 4.2.
Thanks in advance.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide