Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Thu, 3 Jan 2008 18:12:00 -0800,    group: microsoft.public.exchange.clustering        back       


Exchange 2003 Clustering - Unable to failover System Attendant    
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 
<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 
<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 
<Exchange System Attendant - >: [EXRES] Thread exited: 
DwOnlineSecondaryThread. Returning error 1053.
aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System Attendant 
<Exchange System Attendant - >: [EXRES] DwOnlinePrimaryThread: secondary 
thread failed. Error 1053.
aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System Attendant 
<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 
<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
date: Thu, 3 Jan 2008 18:12:00 -0800   author:   PFCU

Re: Exchange 2003 Clustering - Unable to failover System Attendant    
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 
news:190E6708-05D4-458D-A4B9-8D4753578135@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
> <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
> <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
> <Exchange System Attendant - >: [EXRES] Thread exited:
> DwOnlineSecondaryThread. Returning error 1053.
> aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System 
> Attendant
> <Exchange System Attendant - >: [EXRES] DwOnlinePrimaryThread: secondary
> thread failed. Error 1053.
> aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System 
> Attendant
> <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
> <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
>
>
>
date: Sat, 5 Jan 2008 17:05:42 +0100   author:   Leif Pedersen [ MVP]

Re: Exchange 2003 Clustering - Unable to failover System Attendant    
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 
> news:190E6708-05D4-458D-A4B9-8D4753578135@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
> > <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
> > <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
> > <Exchange System Attendant - >: [EXRES] Thread exited:
> > DwOnlineSecondaryThread. Returning error 1053.
> > aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System 
> > Attendant
> > <Exchange System Attendant - >: [EXRES] DwOnlinePrimaryThread: secondary
> > thread failed. Error 1053.
> > aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System 
> > Attendant
> > <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
> > <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
> >
> >
> > 
>
date: Mon, 7 Jan 2008 10:55:00 -0800   author:   PFCU

Re: Exchange 2003 Clustering - Unable to failover System Attendant    
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 
news:261B2852-B7D5-44FE-8258-15C04930A568@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 
> news:190E6708-05D4-458D-A4B9-8D4753578135@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
>> <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
>> <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
>> <Exchange System Attendant - >: [EXRES] Thread exited:
>> DwOnlineSecondaryThread. Returning error 1053.
>> aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System 
>> Attendant
>> <Exchange System Attendant - >: [EXRES] DwOnlinePrimaryThread: secondary
>> thread failed. Error 1053.
>> aa0:79c.01/03[23:57:31.054](013493) ERR  Microsoft Exchange System 
>> Attendant
>> <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
>> <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
>>
>>
>>
>
date: Mon, 7 Jan 2008 21:30:51 -0800   author:   John Fullbright fjohn@donotspamnetappdotcom

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us