08-31-2005 10:37 AM - edited 03-18-2019 05:00 PM
When I tried to add a subscriber I receiver the following error .Any ideas??? Thanks for your input!
08-31-2005 03:07 PM
Hi -
You did not mention what Unity version you are running, so these may not apply (I got these hits doing a search for 0x80005000 - They are for Unity 4.0(1) and 4.0(2)):
http://www.ciscotaccc.com/voice/showcase?case=K10249363
Regards, Ginger
08-31-2005 04:44 PM
Cisco Unity 4.0 Build 4.0(3) SR 1
I do not know of anything that has changed...I just added 6-7 subscribers yesterday?...This is what I found in the release notes link that you forward,In Unity 4.0, when the new subscriber creation window comes up, instead of showing the various fields to fill in, this error is displayed, "Error fetching MailStore list (for server SERVERNAME). hr=0x80005000. Check that the AVDSGlobalCatalog is registered and running. Please see your system administrator for more details." Workaround Open Regedt32, highlight the registry key above, click Security > Permissions, and restore Full Control to the account that the AvDSGlobalCatalog service is running under
09-01-2005 07:28 AM
Hi -
Sounds like you were working OK a day ago then? I know version 4.0(3) does not have the automatic DC/GC reconnect feature and needed to be reset via the registry if it lost contact with its DC/GC. Can you ping the Unity server's DC and GC OK?
Ginger
09-01-2005 05:10 PM
Ginger, Thanks for your input the following was the fix: CiscoUnity_DSAD
Skipping synchronization cycle due to error connecting to domain controller. Ensure that the server is accessible
That means that the domain controller that unity monitors which is currently offline or not available. Checking the Unityinfo it seems that the value is empty:
Domain Controllers=ftsad.com:
Please follow the steps defined here to correct that, please point this to the correct DC.
After that, it should work.
09-01-2005 05:53 PM
I think Ginger is on the right track. Do you see any warning or errors in the application event logs? The other thing that could have happened is that the default OU that Unity creates objects in has been deleted.
To check for the domain controllers that you are using, see:
Changing the Domain Controller That Cisco Unity Monitors (Cisco Unity 3.x Through 4.0(3))
Changing the Global Catalog Server That Cisco Unity Monitors for Directory Updates (Cisco Unity 3.x Through 4.0(3))
Since this was working before, something changed to cause it to fail. A workaround may be to create the users in AD, and then using the Import tool.
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