05-16-2006 07:13 AM - edited 03-18-2019 05:54 PM
Upgraded a 4.0.4 SR1 (with failover) fully functional unified messaging system to 4.1.1. After the upgrade, the Primary server is not reading the message stack correctly. It will take messages, light MWI, and you can access the messages via viewmail. Just cannot retrieve the messages from the TUI on the primary system. In failover mode, on the secondary server, everything works as advertised. We tried resetting the permissions via the wizard with no luck. All of the system check tools say everything is happy. The back end is off box Exchange 2003 SP1 as are the management tools on both Unity servers. Any ideas where to look to try and track this down? Thanks in advance for any help.
05-16-2006 07:20 AM
Did you check all the Exchange Sps on the Unity Server? You may need to reinstall the Exchange sp's on the failover and primary.
05-16-2006 07:34 AM
We did try and rebuild the primary server and got the same results. I have not tried to reinstall the Exchange SP1 on top of itself. I will give that a try. Since the failover server works, I am at a loss why the primary would be having issues. The gather system utility says it is on Exchange 2003 SP1, but I would agree that it sounds like it is stuck in limbo. I'll give that a try and post a follow up.
05-16-2006 07:39 AM
Check for SQL errors in the replication. Sounds like the replication has lost some information or correct rights/permissions.
05-16-2006 08:58 AM
OK, there are some errors on the replication. Is there a document on how to rebuild the replication as the failover wizard does not seem to be doing a good job. (I have tried it about 10 times and it completes successfully and still has errors). I also tried to reinstall the Exchange 2003 SP1. It also completed successfully with no change to the issue. Any ideas?
05-16-2006 09:38 AM
You can try to get TAC on the phone and they are pretty good at fixing the SQL Enterprise settings. It's pretty tricky. I would probably just try and remove failover completely from the boxes, and run the wizard again. It seems to be the only way to actually get it back working again I have found
05-16-2006 10:02 AM
Thanks. The work around for ES 11 fixed the message access issue. I am working with TAC to get that ES. Then I will see if I can straighten out the SQL stuff. I messed with it so much to try and get the message stack issue resolved, that I may have messed it up myself. Thanks again!
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