Exchange 2003 Clustering - Unable to failover System Attenda

PFCU · Joined: 28 Sep 2007 Posts: 3

Hi,

I have a 2 node active-passive cluster (Windows 2003 SP2 and Exchange 2003
SP2). The system attendant does not start on the passive node when I initiate
a failover.

I see the following in the app and cluster logs.

Any assistance is appreciated.

Thanks

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 1010
Description:
Exchange System Attendant - CHN-EXMBXPR01: Failed to start the service
'MSExchangeSA'.

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 1003
Description:
Exchange System Attendant - CHN-EXMBXPR01: Failed to bring the resource
online.

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 1008

Description:
Exchange HTTP Virtual Server Instance 100 (): Failed to start or stop the
protocol instance. Possible causes are failure to open the metabase; failure
to set the start or stop command; or failure to start or stop protocol
instance in a timely fashion.

aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System Attendant
: [EXRES] DwStartService: failed to start
service 'MSExchangeSA'. Error 1053.
aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System Attendant
: [EXRES] EventLogging: Exchange System
Attendant - : Failed to start the service 'MSExchangeSA'. Error Code:
1053.
aa0:76c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System Attendant
: [EXRES] Thread exited:
DwOnlineSecondaryThread. Returning error 1053.
aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System Attendant
: [EXRES] DwOnlinePrimaryThread: secondary
thread failed. Error 1053.
aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System Attendant
: [EXRES] EventLogging: Exchange System
Attendant - : Failed to bring the resource online. Error Code: 1053.
aa0:79c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System Attendant
: [EXRES] Thread exited: DwOnlinePrimaryThread.
Returning error 1053.
86c:96c.01/03[23:57:31.054](013493) WARN [FM] FmpHandleResourceTransition:
Resource Name = e14d2deb-97b7-4d20-8dd0-2c4e3821fab6 [Exchange System
Attendant - ] old state=129 new state=4

Archived from group: microsoft>public>exchange>clustering

Leif Pedersen [ MVP] · Joined: 05 Aug 2007 Posts: 232

Hi,

These might help:
http://support.microsoft.com/kb/910413
http://support.microsoft.com/kb/273428

Especially the part of running exbpa.

Leif

"PFCU" skrev i meddelelsen @microsoft.com...
> Hi,
>
> I have a 2 node active-passive cluster (Windows 2003 SP2 and Exchange 2003
> SP2). The system attendant does not start on the passive node when I
> initiate
> a failover.
>
> I see the following in the app and cluster logs.
>
> Any assistance is appreciated.
>
> Thanks
>
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 1010
> Description:
> Exchange System Attendant - CHN-EXMBXPR01: Failed to start the service
> 'MSExchangeSA'.
>
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 1003
> Description:
> Exchange System Attendant - CHN-EXMBXPR01: Failed to bring the resource
> online.
>
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 1008
>
> Description:
> Exchange HTTP Virtual Server Instance 100 (): Failed to start or stop the
> protocol instance. Possible causes are failure to open the metabase;
> failure
> to set the start or stop command; or failure to start or stop protocol
> instance in a timely fashion.
>
>
> aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> Attendant
> : [EXRES] DwStartService: failed to start
> service 'MSExchangeSA'. Error 1053.
> aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> Attendant
> : [EXRES] EventLogging: Exchange System
> Attendant - : Failed to start the service 'MSExchangeSA'. Error Code:
> 1053.
> aa0:76c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System
> Attendant
> : [EXRES] Thread exited:
> DwOnlineSecondaryThread. Returning error 1053.
> aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> Attendant
> : [EXRES] DwOnlinePrimaryThread: secondary
> thread failed. Error 1053.
> aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> Attendant
> : [EXRES] EventLogging: Exchange System
> Attendant - : Failed to bring the resource online. Error Code: 1053.
> aa0:79c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System
> Attendant
> : [EXRES] Thread exited:
> DwOnlinePrimaryThread.
> Returning error 1053.
> 86c:96c.01/03[23:57:31.054](013493) WARN [FM] FmpHandleResourceTransition:
> Resource Name = e14d2deb-97b7-4d20-8dd0-2c4e3821fab6 [Exchange System
> Attendant - ] old state=129 new state=4
>
>
>

PFCU · Joined: 28 Sep 2007 Posts: 3

Thanks. I had reviewed this information and did not find it relevant to the
issue. The SA is running fine on the current active node so, I do not think
it is a AD or GC related issue. It seems to be some corruption in the 2nd
node.

"Leif Pedersen [ MVP]" wrote:

> Hi,
>
> These might help:
> http://support.microsoft.com/kb/910413
> http://support.microsoft.com/kb/273428
>
> Especially the part of running exbpa.
>
> Leif
>
> "PFCU" skrev i meddelelsen
> @microsoft.com...
> > Hi,
> >
> > I have a 2 node active-passive cluster (Windows 2003 SP2 and Exchange 2003
> > SP2). The system attendant does not start on the passive node when I
> > initiate
> > a failover.
> >
> > I see the following in the app and cluster logs.
> >
> > Any assistance is appreciated.
> >
> > Thanks
> >
> > Event Type: Error
> > Event Source: MSExchangeCluster
> > Event Category: Services
> > Event ID: 1010
> > Description:
> > Exchange System Attendant - CHN-EXMBXPR01: Failed to start the service
> > 'MSExchangeSA'.
> >
> > Event Type: Error
> > Event Source: MSExchangeCluster
> > Event Category: Services
> > Event ID: 1003
> > Description:
> > Exchange System Attendant - CHN-EXMBXPR01: Failed to bring the resource
> > online.
> >
> > Event Type: Error
> > Event Source: MSExchangeCluster
> > Event Category: Services
> > Event ID: 1008
> >
> > Description:
> > Exchange HTTP Virtual Server Instance 100 (): Failed to start or stop the
> > protocol instance. Possible causes are failure to open the metabase;
> > failure
> > to set the start or stop command; or failure to start or stop protocol
> > instance in a timely fashion.
> >
> >
> > aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> > Attendant
> > : [EXRES] DwStartService: failed to start
> > service 'MSExchangeSA'. Error 1053.
> > aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> > Attendant
> > : [EXRES] EventLogging: Exchange System
> > Attendant - : Failed to start the service 'MSExchangeSA'. Error Code:
> > 1053.
> > aa0:76c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System
> > Attendant
> > : [EXRES] Thread exited:
> > DwOnlineSecondaryThread. Returning error 1053.
> > aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> > Attendant
> > : [EXRES] DwOnlinePrimaryThread: secondary
> > thread failed. Error 1053.
> > aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
> > Attendant
> > : [EXRES] EventLogging: Exchange System
> > Attendant - : Failed to bring the resource online. Error Code: 1053.
> > aa0:79c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System
> > Attendant
> > : [EXRES] Thread exited:
> > DwOnlinePrimaryThread.
> > Returning error 1053.
> > 86c:96c.01/03[23:57:31.054](013493) WARN [FM] FmpHandleResourceTransition:
> > Resource Name = e14d2deb-97b7-4d20-8dd0-2c4e3821fab6 [Exchange System
> > Attendant - ] old state=129 new state=4
> >
> >
> >
>

John Fullbright · Joined: 05 Aug 2007 Posts: 365

The SA depends on the disk resources used by exchange. Make sure the 2nd
node is a possible owner of those resources.

"Leif Pedersen [ MVP]" wrote in message @microsoft.com...
> Hi,
>
> These might help:
> http://support.microsoft.com/kb/910413
> http://support.microsoft.com/kb/273428
>
> Especially the part of running exbpa.
>
> Leif
>
> "PFCU" skrev i meddelelsen
> @microsoft.com...
>> Hi,
>>
>> I have a 2 node active-passive cluster (Windows 2003 SP2 and Exchange
>> 2003
>> SP2). The system attendant does not start on the passive node when I
>> initiate
>> a failover.
>>
>> I see the following in the app and cluster logs.
>>
>> Any assistance is appreciated.
>>
>> Thanks
>>
>> Event Type: Error
>> Event Source: MSExchangeCluster
>> Event Category: Services
>> Event ID: 1010
>> Description:
>> Exchange System Attendant - CHN-EXMBXPR01: Failed to start the service
>> 'MSExchangeSA'.
>>
>> Event Type: Error
>> Event Source: MSExchangeCluster
>> Event Category: Services
>> Event ID: 1003
>> Description:
>> Exchange System Attendant - CHN-EXMBXPR01: Failed to bring the resource
>> online.
>>
>> Event Type: Error
>> Event Source: MSExchangeCluster
>> Event Category: Services
>> Event ID: 1008
>>
>> Description:
>> Exchange HTTP Virtual Server Instance 100 (): Failed to start or stop the
>> protocol instance. Possible causes are failure to open the metabase;
>> failure
>> to set the start or stop command; or failure to start or stop protocol
>> instance in a timely fashion.
>>
>>
>> aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
>> Attendant
>> : [EXRES] DwStartService: failed to start
>> service 'MSExchangeSA'. Error 1053.
>> aa0:76c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
>> Attendant
>> : [EXRES] EventLogging: Exchange System
>> Attendant - : Failed to start the service 'MSExchangeSA'. Error
>> Code:
>> 1053.
>> aa0:76c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System
>> Attendant
>> : [EXRES] Thread exited:
>> DwOnlineSecondaryThread. Returning error 1053.
>> aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
>> Attendant
>> : [EXRES] DwOnlinePrimaryThread: secondary
>> thread failed. Error 1053.
>> aa0:79c.01/03[23:57:31.054](013493) ERR Microsoft Exchange System
>> Attendant
>> : [EXRES] EventLogging: Exchange System
>> Attendant - : Failed to bring the resource online. Error Code: 1053.
>> aa0:79c.01/03[23:57:31.054](013493) INFO Microsoft Exchange System
>> Attendant
>> : [EXRES] Thread exited:
>> DwOnlinePrimaryThread.
>> Returning error 1053.
>> 86c:96c.01/03[23:57:31.054](013493) WARN [FM]
>> FmpHandleResourceTransition:
>> Resource Name = e14d2deb-97b7-4d20-8dd0-2c4e3821fab6 [Exchange System
>> Attendant - ] old state=129 new state=4
>>
>>
>>
>

Failover not working in clustering I have 3 clustering node. Active, Active & Passive. After failover from active to passvive, it works for 15 minutes. After which, on user Outlook 2003, it shows "Trying to connect...". Run ESM from Exchange server, try to expand SG, it hangs. In the Event

Microsoft Exchange 2003 Clustering Problems with outlook 200 Hi all I have a two node exchange virtual server.all installed correctly, but when i created a exchange mailbox for my test user and try and add the exchange account to outlook I get an error. "The name could not be matched to a name in the

failover for Exchange 2007 Hi, I am looking for a technical solution to have a failover for our Exchange server. See below our Site A located in New York, Exchange 2003 running on W2003 st ed R2 sp2, domain windows 2003. Site B (backup site) located in LA. Sites A (

Exchange version for CAS/HT clustering Hi there, I wish to use NLB to load balance the CAS role (on same box as HT.) My only question is - is Exchange Server 2007 St. Edition sufficient to do this, or should it be Enterprise? We have both versions available, but I am curious. Thanks!

Clustering in Exchange 2007 I know in Exchange 2007 the mailbox-role servers have to have only that role to enable Exchange clustering. My question is how would one go about providing redundancy for the rest of the system. i.e. the Edge-role server and the multi-role server? Can th