|
|
|
date: Tue, 26 Feb 2008 14:42:30 +0800,
group: microsoft.public.exchange.clustering
back
Re: CCR Node reboot issue
Please re-read that article. I go to great lengths to explicitly state that
using the Cluster Tools to move or stop a CMS does not cause bad things; but
rather, it skips checking for bad things which have already happened. These
checks are performed by the Exchange tools, which is why we recommend using
them.
--
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.
"Mike "Talon" DeNapoli" wrote in
message news:ucbv5%23KeIHA.4312@TK2MSFTNGP03.phx.gbl...
> Hi:
>
> Try shutting down the CCR Exchange Virtual Server by using Powershell or
> via the Exchange cluster tools, and not via the Windows Cluster Manager
> systems, if that is how you're shutting it down.. Using anything but CCR
> to shut down a node can cause the DB to get marked as broken from a CCR
> perspective. This can happen during reboots or cluster moves.
>
> See this article:
> http://msexchangeteam.com/archive/2007/10/22/447317.aspx
>
> Hope it helps.
>
> Mike
>
> "Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
> news:5F4EDAC7-F927-4EA0-AC29-FF2AE9549A40@microsoft.com...
>> Recency,I got the issue is about CCR Information Store service.
>> After reboot passive node CCR it will show service error & in event log
>> as below:
>>
>> Source: Service Control Manager
>> Type:Error
>> Description:
>> Microsoft Exchange Information Storeservice terminated with
>> service-specific error 0(0x0).
>>
>> In services MMC the MSExchange Information service is not start,but I can
>> start it manually.
>>
>> Have any suggestion ?
>>
>> Thanks,
>>
>> Jammy
>>
>
>
date: Tue, 26 Feb 2008 12:07:11 -0800
author: Scott Schnoll [MSFT]
Re: CCR Node reboot issue
Thanks Mike & Scott respond.
In fact, I didn't use Cluster admin to manage CCR(Move,Stop or Start...)
I'v search in Google and find the KB945554 but it's has been recall by MS..
The full event log as below
Event Type: Error
Event Source: Service Control Manager Event Category: None
Event ID: 7024
Date: 2/14/08
Time: 12:32:55 PM
User: N/A
Description: The Microsoft Exchange Information Store service terminated
with service-specific error 0 (0x0).
For more information, see Help and Support Center
This issue is not any impact of production(casue can start it manaully after
reboot).
But in event log it just....
Best regards,
Jammy
"Scott Schnoll [MSFT]" wrote in message
news:OKPPtMLeIHA.4728@TK2MSFTNGP03.phx.gbl...
> Please re-read that article. I go to great lengths to explicitly state
> that using the Cluster Tools to move or stop a CMS does not cause bad
> things; but rather, it skips checking for bad things which have already
> happened. These checks are performed by the Exchange tools, which is why
> we recommend using them.
> --
> 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.
>
>
> "Mike "Talon" DeNapoli" wrote in
> message news:ucbv5%23KeIHA.4312@TK2MSFTNGP03.phx.gbl...
>> Hi:
>>
>> Try shutting down the CCR Exchange Virtual Server by using Powershell or
>> via the Exchange cluster tools, and not via the Windows Cluster Manager
>> systems, if that is how you're shutting it down.. Using anything but CCR
>> to shut down a node can cause the DB to get marked as broken from a CCR
>> perspective. This can happen during reboots or cluster moves.
>>
>> See this article:
>> http://msexchangeteam.com/archive/2007/10/22/447317.aspx
>>
>> Hope it helps.
>>
>> Mike
>>
>> "Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
>> news:5F4EDAC7-F927-4EA0-AC29-FF2AE9549A40@microsoft.com...
>>> Recency,I got the issue is about CCR Information Store service.
>>> After reboot passive node CCR it will show service error & in event log
>>> as below:
>>>
>>> Source: Service Control Manager
>>> Type:Error
>>> Description:
>>> Microsoft Exchange Information Storeservice terminated with
>>> service-specific error 0(0x0).
>>>
>>> In services MMC the MSExchange Information service is not start,but I
>>> can start it manually.
>>>
>>> Have any suggestion ?
>>>
>>> Thanks,
>>>
>>> Jammy
>>>
>>
>>
>
date: Wed, 27 Feb 2008 13:44:01 +0800
author: Jammy-MVP AM
Re: CCR Node reboot issue
Is this RTM or SP1? Also, do you have any storage groups on this system, or
have you removed them all? If you have storage groups, are they all
healthy, and have the appropriate files in the file system?
--
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.
"Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
news:0A1ACA6D-BF3A-444C-B989-32B14AF1550B@microsoft.com...
> Thanks Mike & Scott respond.
> In fact, I didn't use Cluster admin to manage CCR(Move,Stop or Start...)
> I'v search in Google and find the KB945554 but it's has been recall by
> MS..
> The full event log as below
>
> Event Type: Error
> Event Source: Service Control Manager Event Category: None
> Event ID: 7024
> Date: 2/14/08
> Time: 12:32:55 PM
> User: N/A
> Description: The Microsoft Exchange Information Store service terminated
> with service-specific error 0 (0x0).
> For more information, see Help and Support Center
>
> This issue is not any impact of production(casue can start it manaully
> after reboot).
> But in event log it just....
>
> Best regards,
>
> Jammy
>
> "Scott Schnoll [MSFT]" wrote in message
> news:OKPPtMLeIHA.4728@TK2MSFTNGP03.phx.gbl...
>> Please re-read that article. I go to great lengths to explicitly state
>> that using the Cluster Tools to move or stop a CMS does not cause bad
>> things; but rather, it skips checking for bad things which have already
>> happened. These checks are performed by the Exchange tools, which is why
>> we recommend using them.
>> --
>> 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.
>>
>>
>> "Mike "Talon" DeNapoli" wrote in
>> message news:ucbv5%23KeIHA.4312@TK2MSFTNGP03.phx.gbl...
>>> Hi:
>>>
>>> Try shutting down the CCR Exchange Virtual Server by using Powershell or
>>> via the Exchange cluster tools, and not via the Windows Cluster Manager
>>> systems, if that is how you're shutting it down.. Using anything but
>>> CCR to shut down a node can cause the DB to get marked as broken from a
>>> CCR perspective. This can happen during reboots or cluster moves.
>>>
>>> See this article:
>>> http://msexchangeteam.com/archive/2007/10/22/447317.aspx
>>>
>>> Hope it helps.
>>>
>>> Mike
>>>
>>> "Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
>>> news:5F4EDAC7-F927-4EA0-AC29-FF2AE9549A40@microsoft.com...
>>>> Recency,I got the issue is about CCR Information Store service.
>>>> After reboot passive node CCR it will show service error & in event
>>>> log as below:
>>>>
>>>> Source: Service Control Manager
>>>> Type:Error
>>>> Description:
>>>> Microsoft Exchange Information Storeservice terminated with
>>>> service-specific error 0(0x0).
>>>>
>>>> In services MMC the MSExchange Information service is not start,but I
>>>> can start it manually.
>>>>
>>>> Have any suggestion ?
>>>>
>>>> Thanks,
>>>>
>>>> Jammy
>>>>
>>>
>>>
>>
>
date: Wed, 27 Feb 2008 08:13:56 -0800
author: Scott Schnoll [MSFT]
Re: CCR Node reboot issue
The All Exchange Server 2007 is upgrate to SP1.
And all storage group copy status is healthy.
"Scott Schnoll [MSFT]" wrote in message
news:OO$WDvVeIHA.1208@TK2MSFTNGP05.phx.gbl...
> Is this RTM or SP1? Also, do you have any storage groups on this system,
> or have you removed them all? If you have storage groups, are they all
> healthy, and have the appropriate files in the file system?
> --
> 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.
>
>
>
> "Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
> news:0A1ACA6D-BF3A-444C-B989-32B14AF1550B@microsoft.com...
>> Thanks Mike & Scott respond.
>> In fact, I didn't use Cluster admin to manage CCR(Move,Stop or Start...)
>> I'v search in Google and find the KB945554 but it's has been recall by
>> MS..
>> The full event log as below
>>
>> Event Type: Error
>> Event Source: Service Control Manager Event Category: None
>> Event ID: 7024
>> Date: 2/14/08
>> Time: 12:32:55 PM
>> User: N/A
>> Description: The Microsoft Exchange Information Store service terminated
>> with service-specific error 0 (0x0).
>> For more information, see Help and Support Center
>>
>> This issue is not any impact of production(casue can start it manaully
>> after reboot).
>> But in event log it just....
>>
>> Best regards,
>>
>> Jammy
>>
>> "Scott Schnoll [MSFT]" wrote in message
>> news:OKPPtMLeIHA.4728@TK2MSFTNGP03.phx.gbl...
>>> Please re-read that article. I go to great lengths to explicitly state
>>> that using the Cluster Tools to move or stop a CMS does not cause bad
>>> things; but rather, it skips checking for bad things which have already
>>> happened. These checks are performed by the Exchange tools, which is
>>> why we recommend using them.
>>> --
>>> 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.
>>>
>>>
>>> "Mike "Talon" DeNapoli" wrote in
>>> message news:ucbv5%23KeIHA.4312@TK2MSFTNGP03.phx.gbl...
>>>> Hi:
>>>>
>>>> Try shutting down the CCR Exchange Virtual Server by using Powershell
>>>> or via the Exchange cluster tools, and not via the Windows Cluster
>>>> Manager systems, if that is how you're shutting it down.. Using
>>>> anything but CCR to shut down a node can cause the DB to get marked as
>>>> broken from a CCR perspective. This can happen during reboots or
>>>> cluster moves.
>>>>
>>>> See this article:
>>>> http://msexchangeteam.com/archive/2007/10/22/447317.aspx
>>>>
>>>> Hope it helps.
>>>>
>>>> Mike
>>>>
>>>> "Jammy-MVP" <Jammylo@ms4.hinet.net.NOSPAM> wrote in message
>>>> news:5F4EDAC7-F927-4EA0-AC29-FF2AE9549A40@microsoft.com...
>>>>> Recency,I got the issue is about CCR Information Store service.
>>>>> After reboot passive node CCR it will show service error & in event
>>>>> log as below:
>>>>>
>>>>> Source: Service Control Manager
>>>>> Type:Error
>>>>> Description:
>>>>> Microsoft Exchange Information Storeservice terminated with
>>>>> service-specific error 0(0x0).
>>>>>
>>>>> In services MMC the MSExchange Information service is not start,but I
>>>>> can start it manually.
>>>>>
>>>>> Have any suggestion ?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jammy
>>>>>
>>>>
>>>>
>>>
>>
>
date: Mon, 3 Mar 2008 19:22:03 +0800
author: Jammy-MVP AM
|
|
