Trying to upgrade Exch 2007 CCR to SP1 - Transient Communication E   

Error:
Move-ClusteredMailboxServer : Moving clustered mailbox server '[identity]' 
to '[passivenode]' failed because of a transient communication error with the 
Windows Cluster service.
At line:1 char:27
+ Move-ClusteredMailboxServer <<<<

Actions:
We had Forefront installed on both mailbox servers, but this has been 
removed.  The mailbox server would failover before, but is now giving us the 
above error.  I found http://support.microsoft.com/kb/945554/en-us but the 
registry setting is correct on the passive node, and the cluster starts to 
failover, but then fails back with the above error.  I then have to start the 
Exchange database instances as the remain offline.

Any help greatly appreciated, as I will be unable to install SP1 until 
Exchange will move.

Pete.

date: Wed, 30 Jan 2008 08:56:01 -0800   author:   PeteL

Re: Trying to upgrade Exch 2007 CCR to SP1 - Transient Communication E   

Are you able to start the CMS on the active node?  If so, what does 
Get-StorageGroupCopyStatus show for continuous replication?

If replication is healthy, you can try stopping the CMS and then using 
Cluster Administrator to move the CMS group to the other node.

Hope this helps.
-- 
Regards,

Scott Schnoll
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.


"PeteL"  wrote in message 
news:B280216C-76FE-46B7-8FBC-46A11AB761C3@microsoft.com...
> Error:
> Move-ClusteredMailboxServer : Moving clustered mailbox server '[identity]'
> to '[passivenode]' failed because of a transient communication error with 
> the
> Windows Cluster service.
> At line:1 char:27
> + Move-ClusteredMailboxServer <<<<
>
> Actions:
> We had Forefront installed on both mailbox servers, but this has been
> removed.  The mailbox server would failover before, but is now giving us 
> the
> above error.  I found http://support.microsoft.com/kb/945554/en-us but the
> registry setting is correct on the passive node, and the cluster starts to
> failover, but then fails back with the above error.  I then have to start 
> the
> Exchange database instances as the remain offline.
>
> Any help greatly appreciated, as I will be unable to install SP1 until
> Exchange will move.
>
> Pete.

date: Wed, 30 Jan 2008 11:16:13 -0800   author:   Scott Schnoll [MSFT]

Re: Trying to upgrade Exch 2007 CCR to SP1 - Transient Communicati   

Scott

Thanks for the response.

The CMS will start on the active node, Get-StorageGroupCopyStatus shows 
values of 0, and mail is getting to the server.  Due to time issues I'm going 
to raise a call with Microsoft.

Thanks again.

Pete.

"Scott Schnoll [MSFT]" wrote:

> Are you able to start the CMS on the active node?  If so, what does 
> Get-StorageGroupCopyStatus show for continuous replication?
> 
> If replication is healthy, you can try stopping the CMS and then using 
> Cluster Administrator to move the CMS group to the other node.
> 
> Hope this helps.
> -- 
> Regards,
> 
> Scott Schnoll
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> 
> 
> "PeteL"  wrote in message 
> news:B280216C-76FE-46B7-8FBC-46A11AB761C3@microsoft.com...
> > Error:
> > Move-ClusteredMailboxServer : Moving clustered mailbox server '[identity]'
> > to '[passivenode]' failed because of a transient communication error with 
> > the
> > Windows Cluster service.
> > At line:1 char:27
> > + Move-ClusteredMailboxServer <<<<
> >
> > Actions:
> > We had Forefront installed on both mailbox servers, but this has been
> > removed.  The mailbox server would failover before, but is now giving us 
> > the
> > above error.  I found http://support.microsoft.com/kb/945554/en-us but the
> > registry setting is correct on the passive node, and the cluster starts to
> > failover, but then fails back with the above error.  I then have to start 
> > the
> > Exchange database instances as the remain offline.
> >
> > Any help greatly appreciated, as I will be unable to install SP1 until
> > Exchange will move.
> >
> > Pete. 
> 
>

date: Thu, 31 Jan 2008 01:42:01 -0800   author:   PeteL

Re: Trying to upgrade Exch 2007 CCR to SP1 - Transient Communicati   

Installed Forefront SP1 onto clustered mailbox servers, problem went away.

Pete.

"Scott Schnoll [MSFT]" wrote:

> Are you able to start the CMS on the active node?  If so, what does 
> Get-StorageGroupCopyStatus show for continuous replication?
> 
> If replication is healthy, you can try stopping the CMS and then using 
> Cluster Administrator to move the CMS group to the other node.
> 
> Hope this helps.
> -- 
> Regards,
> 
> Scott Schnoll
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> 
> 
> "PeteL"  wrote in message 
> news:B280216C-76FE-46B7-8FBC-46A11AB761C3@microsoft.com...
> > Error:
> > Move-ClusteredMailboxServer : Moving clustered mailbox server '[identity]'
> > to '[passivenode]' failed because of a transient communication error with 
> > the
> > Windows Cluster service.
> > At line:1 char:27
> > + Move-ClusteredMailboxServer <<<<
> >
> > Actions:
> > We had Forefront installed on both mailbox servers, but this has been
> > removed.  The mailbox server would failover before, but is now giving us 
> > the
> > above error.  I found http://support.microsoft.com/kb/945554/en-us but the
> > registry setting is correct on the passive node, and the cluster starts to
> > failover, but then fails back with the above error.  I then have to start 
> > the
> > Exchange database instances as the remain offline.
> >
> > Any help greatly appreciated, as I will be unable to install SP1 until
> > Exchange will move.
> >
> > Pete. 
> 
>

date: Tue, 5 Feb 2008 04:12:00 -0800   author:   PeteL

Re: Trying to upgrade Exch 2007 CCR to SP1 - Transient Communicati   

Nice!  So the issue was that you were using the RTM version of Forefront and 
not SP1?


"PeteL"  wrote in message 
news:90CB69D0-418E-4C1C-8A07-96162E2F9D12@microsoft.com...
> Installed Forefront SP1 onto clustered mailbox servers, problem went away.
>
> Pete.
>
> "Scott Schnoll [MSFT]" wrote:
>
>> Are you able to start the CMS on the active node?  If so, what does
>> Get-StorageGroupCopyStatus show for continuous replication?
>>
>> If replication is healthy, you can try stopping the CMS and then using
>> Cluster Administrator to move the CMS group to the other node.
>>
>> Hope this helps.
>> -- 
>> Regards,
>>
>> Scott Schnoll
>> Microsoft Corporation
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is 
>> for
>> newsgroup purposes only.
>>
>>
>> "PeteL"  wrote in message
>> news:B280216C-76FE-46B7-8FBC-46A11AB761C3@microsoft.com...
>> > Error:
>> > Move-ClusteredMailboxServer : Moving clustered mailbox server 
>> > '[identity]'
>> > to '[passivenode]' failed because of a transient communication error 
>> > with
>> > the
>> > Windows Cluster service.
>> > At line:1 char:27
>> > + Move-ClusteredMailboxServer <<<<
>> >
>> > Actions:
>> > We had Forefront installed on both mailbox servers, but this has been
>> > removed.  The mailbox server would failover before, but is now giving 
>> > us
>> > the
>> > above error.  I found http://support.microsoft.com/kb/945554/en-us but 
>> > the
>> > registry setting is correct on the passive node, and the cluster starts 
>> > to
>> > failover, but then fails back with the above error.  I then have to 
>> > start
>> > the
>> > Exchange database instances as the remain offline.
>> >
>> > Any help greatly appreciated, as I will be unable to install SP1 until
>> > Exchange will move.
>> >
>> > Pete.
>>
>>

date: Tue, 5 Feb 2008 08:58:29 -0800   author:   Scott Schnoll [MSFT]

Re: Trying to upgrade Exch 2007 CCR to SP1 - Transient Communicati   

No.  We had done an uninstall of Forefront RTM, but something must have still 
been kicking around to cause a problem.

Pete.

"Scott Schnoll [MSFT]" wrote:

> Nice!  So the issue was that you were using the RTM version of Forefront and 
> not SP1?
> 
> 
> "PeteL"  wrote in message 
> news:90CB69D0-418E-4C1C-8A07-96162E2F9D12@microsoft.com...
> > Installed Forefront SP1 onto clustered mailbox servers, problem went away.
> >
> > Pete.
> >
> > "Scott Schnoll [MSFT]" wrote:
> >
> >> Are you able to start the CMS on the active node?  If so, what does
> >> Get-StorageGroupCopyStatus show for continuous replication?
> >>
> >> If replication is healthy, you can try stopping the CMS and then using
> >> Cluster Administrator to move the CMS group to the other node.
> >>
> >> Hope this helps.
> >> -- 
> >> Regards,
> >>
> >> Scott Schnoll
> >> Microsoft Corporation
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights. Please do not send email directly to this alias. This alias is 
> >> for
> >> newsgroup purposes only.
> >>
> >>
> >> "PeteL"  wrote in message
> >> news:B280216C-76FE-46B7-8FBC-46A11AB761C3@microsoft.com...
> >> > Error:
> >> > Move-ClusteredMailboxServer : Moving clustered mailbox server 
> >> > '[identity]'
> >> > to '[passivenode]' failed because of a transient communication error 
> >> > with
> >> > the
> >> > Windows Cluster service.
> >> > At line:1 char:27
> >> > + Move-ClusteredMailboxServer <<<<
> >> >
> >> > Actions:
> >> > We had Forefront installed on both mailbox servers, but this has been
> >> > removed.  The mailbox server would failover before, but is now giving 
> >> > us
> >> > the
> >> > above error.  I found http://support.microsoft.com/kb/945554/en-us but 
> >> > the
> >> > registry setting is correct on the passive node, and the cluster starts 
> >> > to
> >> > failover, but then fails back with the above error.  I then have to 
> >> > start
> >> > the
> >> > Exchange database instances as the remain offline.
> >> >
> >> > Any help greatly appreciated, as I will be unable to install SP1 until
> >> > Exchange will move.
> >> >
> >> > Pete.
> >>
> >> 
> 
>

date: Tue, 5 Feb 2008 09:06:07 -0800   author:   PeteL

Re: Trying to upgrade Exch 2007 CCR to SP1 - Transient Communicati   

Gotcha.  Thanks for the update!

"PeteL"  wrote in message 
news:BDB8BBEE-44A7-4974-901F-2CA19704E9AF@microsoft.com...
> No.  We had done an uninstall of Forefront RTM, but something must have 
> still
> been kicking around to cause a problem.
>
> Pete.
>
> "Scott Schnoll [MSFT]" wrote:
>
>> Nice!  So the issue was that you were using the RTM version of Forefront 
>> and
>> not SP1?
>>
>>
>> "PeteL"  wrote in message
>> news:90CB69D0-418E-4C1C-8A07-96162E2F9D12@microsoft.com...
>> > Installed Forefront SP1 onto clustered mailbox servers, problem went 
>> > away.
>> >
>> > Pete.
>> >
>> > "Scott Schnoll [MSFT]" wrote:
>> >
>> >> Are you able to start the CMS on the active node?  If so, what does
>> >> Get-StorageGroupCopyStatus show for continuous replication?
>> >>
>> >> If replication is healthy, you can try stopping the CMS and then using
>> >> Cluster Administrator to move the CMS group to the other node.
>> >>
>> >> Hope this helps.
>> >> -- 
>> >> Regards,
>> >>
>> >> Scott Schnoll
>> >> Microsoft Corporation
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights. Please do not send email directly to this alias. This alias is
>> >> for
>> >> newsgroup purposes only.
>> >>
>> >>
>> >> "PeteL"  wrote in message
>> >> news:B280216C-76FE-46B7-8FBC-46A11AB761C3@microsoft.com...
>> >> > Error:
>> >> > Move-ClusteredMailboxServer : Moving clustered mailbox server
>> >> > '[identity]'
>> >> > to '[passivenode]' failed because of a transient communication error
>> >> > with
>> >> > the
>> >> > Windows Cluster service.
>> >> > At line:1 char:27
>> >> > + Move-ClusteredMailboxServer <<<<
>> >> >
>> >> > Actions:
>> >> > We had Forefront installed on both mailbox servers, but this has 
>> >> > been
>> >> > removed.  The mailbox server would failover before, but is now 
>> >> > giving
>> >> > us
>> >> > the
>> >> > above error.  I found http://support.microsoft.com/kb/945554/en-us 
>> >> > but
>> >> > the
>> >> > registry setting is correct on the passive node, and the cluster 
>> >> > starts
>> >> > to
>> >> > failover, but then fails back with the above error.  I then have to
>> >> > start
>> >> > the
>> >> > Exchange database instances as the remain offline.
>> >> >
>> >> > Any help greatly appreciated, as I will be unable to install SP1 
>> >> > until
>> >> > Exchange will move.
>> >> >
>> >> > Pete.
>> >>
>> >>
>>
>>

date: Tue, 5 Feb 2008 10:04:32 -0800   author:   Scott Schnoll [MSFT]