03-04-2005 01:06 PM - edited 03-18-2019 04:18 PM
Running Unity 4.0(4)SR1. DC is a seperate box running Windows 2000. Exchange 5.5 was on a seperate box running Windows 2000. All servers are up-to-date with service packs and fixes. Customer installed Exchange 2003 on a seperate server running Windows 2000. Exchange 2003 is NOT installed.
Customer changed the Unity Partner server to the new Exchange 2003 server, but will continue to have subscribers on the Exchange 5.5 server, using the following procedures on the Unity server:
1. Stopped Unity
2. Removed the Message Store Configuration using Add/Remove Programs, and rebooted Unity server.
3. Uninstalled the Exchange 5.5 Administration Tools
4. Installed the Exchange 2003 System Tools
5. Created the UnityMsgStoreSvc and UnityDirSvc accounts. Gave them domain admin rights, Exchange 2003 Full Admin Rights, Exchange 5.5 Admin rights on both the site and configuration containers.
6. Ran the updated Permissions wizard.
7. Ran the Service Configuration wizard choosing Exchange 2003 as the Partner server.
8. Ran the Message Store Configuration wizard choosing Exchange 2003 as the Partner server.
9. Reran the Permission Wizard.
10. Rebooted the Unity Server.
Unity came up but now when a subscriber is either created or imported in Unity, and the mailbox is on the Exchange 5.5 server, the following error message, which does not occur if the mailbox is located on the Exchange 2003 server, appears in the Event log:
Source: CiscoUnity_Notifier
Event ID: 1034
Mailbox logon failed for user cn=TerryG,cn=Recipients,ou=CHICAGO,o=SBC. This can occur if the user's message store is unavailable. When the message store becomes available, resync the user from the SA by refreshing the MWI status on the user's Messages page.
I have recreated this in a lab following the same steps as the customer. Any help is appreciated.
03-04-2005 06:02 PM
Open Unity Diagnostic Tool
Turn on MWI Macro traces.
Add Micro traces ExchangeMonitor 10 12
Click Start New Logs
Leave a vm for the subscriber with a MWI problem
After the error appears on app logs, click on "Gather Logs" in UDT
click on "Select logs"
Get the last of AvCsMgr, AvMsgMonitorSvr, and AvNotifierMgr logs. Zip the logs and post them here.
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