Exchange 2003 Clustering - Unable to failover System Attendant
PFCU
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
Leif Pedersen [ MVP]
These might help:
http://support.microsoft.com/kb/910413
http://support.microsoft.com/kb/273428
Especially the part of running exbpa.
Leif
"PFCU" <PF...@discussions.microsoft.com> skrev i meddelelsen
news:190E6708-05D4-458D...@microsoft.com...
PFCU
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.
John Fullbright
node is a possible owner of those resources.
"Leif Pedersen [ MVP]" <leif.pede...@get2net.dk> wrote in message
news:261B2852-B7D5-44FE...@microsoft.com...
bon maria57
The exchange clustering - unable to failover systemattendant error is occurred when the clusters of exchange server are being corrupted. few months ago i have faced such type of issues with my exchange server. That time i was very frustrated. i just go for solution for this issue over Google. i found there Kernel software that works really good and very powerful. you can also find it at:: www.exchangerepairtool.com
PFC wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
03-Jan-08
Hi,
Any assistance is appreciated.
Thanks
Previous Posts In This Thread:
On Thursday, January 03, 2008 9:12 PM
PFC wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
Hi,
Any assistance is appreciated.
Thanks
On Saturday, January 05, 2008 11:05 AM
Leif Pedersen [ MVP] wrote:
Re: Exchange 2003 Clustering - Unable to failover System Attendant
Hi,
Especially the part of running exbpa.
Leif
On Monday, January 07, 2008 1:55 PM
PFC wrote:
Thanks.
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:
On Tuesday, January 08, 2008 12:30 AM
John Fullbright wrote:
The SA depends on the disk resources used by exchange.
The SA depends on the disk resources used by exchange. Make sure the 2nd
node is a possible owner of those resources.
Submitted via EggHeadCafe - Software Developer Portal of Choice
BizTalk: Parallel Processing with Correlation
http://www.eggheadcafe.com/tutorials/aspnet/6b1df1e9-e8fc-4dc1-a810-1245a8ef0208/biztalk-parallel-processing-with-correlation.aspx
bon maria57
The exchange clustering - unable to failover systemattendant error is occurred when the clusters of exchange server are being corrupted. few months ago i have faced such type of issues with my exchange server. That time i was very frustrated. i just go for solution for this issue over Google. i found there Kernel software that works really good and very powerful. you can also find it at:: www.exchangerepairtool.com
PFC wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
03-Jan-08
Hi,
Any assistance is appreciated.
Thanks
Previous Posts In This Thread:
On Thursday, January 03, 2008 9:12 PM
PFC wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
Hi,
Any assistance is appreciated.
Thanks
On Saturday, January 05, 2008 11:05 AM
Leif Pedersen [ MVP] wrote:
Re: Exchange 2003 Clustering - Unable to failover System Attendant
Hi,
Especially the part of running exbpa.
Leif
On Monday, January 07, 2008 1:55 PM
PFC wrote:
Thanks.
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:
On Tuesday, January 08, 2008 12:30 AM
John Fullbright wrote:
The SA depends on the disk resources used by exchange.
The SA depends on the disk resources used by exchange. Make sure the 2nd
node is a possible owner of those resources.
On Monday, August 09, 2010 3:52 AM
bon maria57 wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
Hi !
The exchange clustering - unable to failover systemattendant error is occurred when the clusters of exchange server are being corrupted. few months ago i have faced such type of issues with my exchange server. That time i was very frustrated. i just go for solution for this issue over Google. i found there Kernel software that works really good and very powerful. you can also find it at:: www.exchangerepairtool.com
Submitted via EggHeadCafe - Software Developer Portal of Choice
Custom Favorites Web Site with MongoDb and NoRM
http://www.eggheadcafe.com/tutorials/aspnet/7fbc7a01-5d30-4cd3-b373-51d4a0e1afa8/custom-favorites-web-site-with-mongodb-and-norm.aspx
bon maria57
The exchange clustering - unable to failover systemattendant error is occurred when the clusters of exchange server are being corrupted. few months ago i have faced such type of issues with my exchange server. That time i was very frustrated. i just go for solution for this issue over Google. i found there Kernel software that works really good and very powerful. you can also find it at:: www.exchangerepairtool.com
PFC wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
03-Jan-08
Hi,
Any assistance is appreciated.
Thanks
Previous Posts In This Thread:
On Thursday, January 03, 2008 9:12 PM
PFC wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
Hi,
Any assistance is appreciated.
Thanks
On Saturday, January 05, 2008 11:05 AM
Leif Pedersen [ MVP] wrote:
Leif
"Leif Pedersen [ MVP]" wrote:
On Monday, August 09, 2010 5:01 AM
bon maria57 wrote:
Exchange 2003 Clustering - Unable to failover System Attendant
Hi !
The exchange clustering - unable to failover systemattendant error is occurred when the clusters of exchange server are being corrupted. few months ago i have faced such type of issues with my exchange server. That time i was very frustrated. i just go for solution for this issue over Google. i found there Kernel software that works really good and very powerful. you can also find it at:: www.exchangerepairtool.com
Submitted via EggHeadCafe - Software Developer Portal of Choice
Changing WCF Service Implementation at Runtime
http://www.eggheadcafe.com/tutorials/aspnet/d9263dcc-f7ed-42f3-bc96-321461be3306/changing-wcf-service-implementation-at-runtime.aspx