Recently, I upgraded a <a href="http://www.emc.com/products/detail/hardware/clariion-cx4-model-120.htm" target="_blank">Clariion CX4-120</a> to Flare 30 (see my post <a href="http://blogs.egroup.jasonmangone.com/?p=2521" target="_blank">here</a>).  This caused the Replication Manager server to start failing on all the jobs that would run.  It even would fail when I tried to add the Application Set for <a href="http://www.microsoft.com/exchange/2010/en/us/overview.aspx" target="_blank">Exchange 2010</a> into the RM Console.

After much toil and banging my head against the wall.... (see<a href="http://blogs.eGroup-us.com/wp-content/uploads/2010/09/keyboardrage4ov.gif"> here</a>)....I got it figured out.

Here is the steps to getting Replication Manager to work once you have upgraded to Flare 30.....

<!--more-->1. Update the Replication Manager Software (sounds like a simple task, but there are a lot of moving parts to RM)  Here is a list.
<p style="padding-left: 30px">The RM server Software must be updated to level 5.3 or later</p>
<p style="padding-left: 30px">Each of the host agents also must be updated to version 5.3</p>
<p style="padding-left: 30px">Solutions Enabler needs to be version 7.1.2.7 or later</p>
<p style="padding-left: 30px">Navisphere Secure CLI has to be version 7.30 or later</p>
<p style="padding-left: 30px">Navisphere Admsnap must be version 2.30 or later</p>
<p style="padding-left: 30px">If using with Exchange 2010, the Management Tools need to be installed</p>
2. Once all the updates are installed, you have to basically rebuild Replication Manager from scratch.  For some reason RM doesn't show the updated levels for the hosts (even with refresh) until they have been removed from RM completely.  Which, of course, means that all the jobs, and application sets need to be removed before you can remove the host.  (hence the banging of the head against the wall)

3. Once the hosts have been added back in, you are good to go, unless you are using Exchange.

4. If you are using Exchange 2010, when you reinstall the RM software make sure to use a user who's credentials allow the user access to the following Exchange roles, or you will get an error stating that the host has thrown an exception.
<p style="padding-left: 30px">For a stand-alone configuration - Databases</p>
<p style="padding-left: 30px">For a DAG configuration - Databases, Database Copies, and Database Availability Groups (All of which are covered in the default Organization Manager Exchange Group)</p>
5. If, you still receive an error after all this is done, the last thing to check is IIS
<p style="padding-left: 30px">In IIS go to the Default Web Page&gt;Powershel&gt;Authentication</p>
<p style="padding-left: 30px">Enable Windows Authentication</p>
<p style="padding-left: 30px">Under Advanced Settings, Make sure Extended Protection is Off, and uncheck "Enable Kernel-mode Authentication"</p>
Finally, at long last, the Replication Manager is functioning successfully with Flare 30 (and Exchange 2010).

*Sigh of relief*