|
|
|
date: Sat, 17 Dec 2005 23:46:41 -0600,
group: microsoft.public.exchange2000.clustering
back
Please help! System Attendant failed to start on cluster.
Hi all,
I have a problem with Exchange 2000 running on cluster, when I tried to move
the Exchange virtual server from node2 to node1, the System Attendant failed
to come online. Here is what I have setup: two clusters, each cluster run
an active/passive Exchange 2000 server with lastest service packs and hot
fixes. The OS is Windows 2000 with SP4 and all the lates patches. The
problem is exactly the same on both clusters. Right now, Exchange can only
run on Node2 on both clusters.
As far as I know, every thing was working until last weekend when one of
the team member applied Microsoft Security patches to the node1of both
clusters. Last night, when I tried to do the same for node2 but before I
could do that, I found out that Exchange now won't start on node1.
When I attempted to start the System Attendant manually from the service
console then it started, however if I tried to start the service again from
the Cluster Admin console then the service failed. So I think it may have
to do with cluster and or AD permission. I had checked and ensure the
cluster service account has all the user rights and permissions required.
Also I checked to ensure no GPO was apply to the OU that contains the
cluster servers. I think one way of fixing the problem is to re-install
Exchange and all the service packs and hot fixes however I would like to
know exactly what is the cause of the problem.
I turned on the Diagnostic logging for the SA and DSAccess but nothing
showed up that can help me troubleshoot this problem.
Any suggestions or tips on helping me fix this problem is greatly
apprecated. Thank you for your time and effort. Have a great holidays
season.
Cuong
Here are some errors from the System and Cluster logs:
Event Type: Information
Event Source: MSExchangeSA
Event Category: General
Event ID: 9009
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Microsoft Exchange System Attendant is stopping 'ABV_DG.DLL'.
For more information, click
http://www.microsoft.com/contentredirect.asp.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9149
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Microsoft Exchange System Attendant failed to start Exchange server
'EX-CO'. Error code '0xc00703e5'.
For more information, click
http://www.microsoft.com/contentredirect.asp.
Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2128
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Exchange System Attendant: Cluster Service failed the rpc call to
start the resource
For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: e5 03 07 c0 ..
Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2066
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Exchange System Attendant: Cluster Service failed a resource rpc call
when trying to bring the resource online
For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: e5 03 07 c0 ..
Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2065
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Exchange System Attendant: Failed to bring the resource online
For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: e5 03 07 c0 ..
Event Type: Information
Event Source: MSExchangeSA
Event Category: General
Event ID: 9015
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Microsoft Exchange System Attendant is being stopped for Exchange
server 'EX-CO'.
For more information, click
http://www.microsoft.com/contentredirect.asp.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9150
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Microsoft Exchange System Attendant failed to stop Exchange server
'EX-CO'. Error code '0xc1034a70'.
For more information, click
http://www.microsoft.com/contentredirect.asp.
Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 2129
Date: 12/16/2005
Time: 9:16:40 PM
User: N/A
Computer: SRV-COCL1
Description:
Exchange System Attendant: Cluster Service failed the rpc call to stop
the resource
For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 00 00 00 00 ....
Event Type: Error
Event Source: ClusSvc
Event Category: Services
Event ID: 1069
Date: 12/16/2005
Time: 9:25:21 PM
User: N/A
Computer: SRV-COCL1
Description:
Cluster resource 'Exchange System Attendant' failed.
Event Type: Error
Event Source: ClusSvc
Event Category: Services
Event ID: 1069
Date: 12/16/2005
Time: 9:25:23 PM
User: N/A
Computer: SRV-COCL1
Description:
Cluster resource 'Exchange System Attendant' failed.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 12/16/2005
Time: 9:25:23 PM
User: N/A
Computer: SRV-COCL1
Description:
The Microsoft Exchange System Attendant service terminated
unexpectedly. It has done this 1 time(s). The following corrective
action will be taken in 0 milliseconds: No action.
Here are some of the errors from the cluser.log:
00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource: created
resource be3de5ed-5bc2-4435-a0eb-a3ddbf5eaa76, resid 1034040
00000714.00000724::2005/12/16-21:06:30.492 [FM] Initializing resource
6bd4cacf-5993-4b08-927f-612f7d311979 from the registry.
00000714.00000724::2005/12/16-21:06:30.492 [FM] Name for Resource
6bd4cacf-5993-4b08-927f-612f7d311979 is 'EX-CO'.
00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource:
creating resource 6bd4cacf-5993-4b08-927f-612f7d311979 in shared resource
monitor
000008cc.00000924::2005/12/16-21:06:30.492 Network Name <EX-CO>: Unable to
read resource data parameter, error=2
000008cc.00000924::2005/12/16-21:06:30.492 Network Name <EX-CO>: Unable to
read creating DC parameter, error=2
000008cc.00000924::2005/12/16-21:06:30.492 Network Name <EX-CO>: Successful
open of resid 638664
00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource: created
resource 6bd4cacf-5993-4b08-927f-612f7d311979, resid 1035208
00000714.00000724::2005/12/16-21:06:30.492 [FM] Initializing resource
6531dd31-7442-4568-a757-a317898508dc from the registry.
00000714.00000724::2005/12/16-21:06:30.492 [FM] Name for Resource
6531dd31-7442-4568-a757-a317898508dc is 'Exchange System Attendant'.
00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource:
creating resource 6531dd31-7442-4568-a757-a317898508dc in shared resource
monitor
000008cc.000008d8::2005/12/16-21:06:30.507 Microsoft Exchange System
Attendant <Exchange System Attendant>: [EXRES] Open requested.
000008cc.000008d8::2005/12/16-21:06:30.507 Microsoft Exchange System
Attendant <Exchange System Attendant>: [EXRES] Could not read the registry
key for the location of event logging levels, using default 0, the error
code is 2.
00000714.00000774::2005/12/16-21:06:32.664 [GUM] GumSendUpdate: queuing
update type 1 context 0
00000714.00000774::2005/12/16-21:06:32.664 [GUM] GumSendUpdate: Dispatching
seq 25526 type 1 context 0 to node 1
00000714.00000774::2005/12/16-21:06:32.664 [DM] DmWriteToQuorumLog Entry
Seq#=25526 Type=0 Size=148
00000714.00000774::2005/12/16-21:06:32.664 [DM] DmpUpdateCreateKey: Creating
key <Resources\6531dd31-7442-4568-a757-a317898508dc\Parameters>...
00000714.00000774::2005/12/16-21:06:32.664 [DM] DmWriteToQuorumLog Entry
Seq#=25526 Type=0 Size=148
00000714.00000774::2005/12/16-21:06:32.664 [GUM] GumSendUpdate: completed
update seq 25526 type 1 context 0
00000714.00000724::2005/12/16-21:06:32.664 [FM] FmpRmCreateResource: created
resource 6531dd31-7442-4568-a757-a317898508dc, resid 1043104
00000714.00000724::2005/12/16-21:06:32.664 [FM] Initializing resource
c6c0788b-6cfc-4210-a864-a37e16174bd4 from the registry.
00000714.00000724::2005/12/16-21:06:32.664 [FM] Name for Resource
c6c0788b-6cfc-4210-a864-a37e16174bd4 is 'Disk J:'.
00000714.00000724::2005/12/16-21:06:32.664 [FM] FmpRmCreateResource:
creating resource c6c0788b-6cfc-4210-a864-a37e16174bd4 in shared resource
monitor
date: Sat, 17 Dec 2005 23:46:41 -0600
author: Trinity
Re: Please help! System Attendant failed to start on cluster.
chceck if you have
Abv_dg.dll in ..\Exchsrvr\Bin
if not copy from the installation media in the Setup\i386\Exchange\Bin
folder
"Trinity" wrote in message
news:11q9tu6gba28s8f@corp.supernews.com...
> Hi all,
>
> I have a problem with Exchange 2000 running on cluster, when I tried to
> move
> the Exchange virtual server from node2 to node1, the System Attendant
> failed
> to come online. Here is what I have setup: two clusters, each cluster
> run
> an active/passive Exchange 2000 server with lastest service packs and hot
> fixes. The OS is Windows 2000 with SP4 and all the lates patches. The
> problem is exactly the same on both clusters. Right now, Exchange can
> only
> run on Node2 on both clusters.
>
> As far as I know, every thing was working until last weekend when one of
> the team member applied Microsoft Security patches to the node1of both
> clusters. Last night, when I tried to do the same for node2 but before I
> could do that, I found out that Exchange now won't start on node1.
>
> When I attempted to start the System Attendant manually from the service
> console then it started, however if I tried to start the service again
> from
> the Cluster Admin console then the service failed. So I think it may have
> to do with cluster and or AD permission. I had checked and ensure the
> cluster service account has all the user rights and permissions required.
> Also I checked to ensure no GPO was apply to the OU that contains the
> cluster servers. I think one way of fixing the problem is to re-install
> Exchange and all the service packs and hot fixes however I would like to
> know exactly what is the cause of the problem.
>
> I turned on the Diagnostic logging for the SA and DSAccess but nothing
> showed up that can help me troubleshoot this problem.
>
> Any suggestions or tips on helping me fix this problem is greatly
> apprecated. Thank you for your time and effort. Have a great holidays
> season.
>
> Cuong
>
> Here are some errors from the System and Cluster logs:
>
> Event Type: Information
> Event Source: MSExchangeSA
> Event Category: General
> Event ID: 9009
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Microsoft Exchange System Attendant is stopping 'ABV_DG.DLL'.
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Event Type: Error
> Event Source: MSExchangeSA
> Event Category: General
> Event ID: 9149
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Microsoft Exchange System Attendant failed to start Exchange server
>
> 'EX-CO'. Error code '0xc00703e5'.
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 2128
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Exchange System Attendant: Cluster Service failed the rpc call to
>
> start the resource
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Data:
> 0000: e5 03 07 c0 ..
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 2066
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Exchange System Attendant: Cluster Service failed a resource rpc call
>
> when trying to bring the resource online
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Data:
> 0000: e5 03 07 c0 ..
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 2065
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Exchange System Attendant: Failed to bring the resource online
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Data:
> 0000: e5 03 07 c0 ..
> Event Type: Information
> Event Source: MSExchangeSA
> Event Category: General
> Event ID: 9015
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Microsoft Exchange System Attendant is being stopped for Exchange
>
> server 'EX-CO'.
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Event Type: Error
> Event Source: MSExchangeSA
> Event Category: General
> Event ID: 9150
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Microsoft Exchange System Attendant failed to stop Exchange server
>
> 'EX-CO'. Error code '0xc1034a70'.
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Event Type: Error
> Event Source: MSExchangeCluster
> Event Category: Services
> Event ID: 2129
> Date: 12/16/2005
> Time: 9:16:40 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Exchange System Attendant: Cluster Service failed the rpc call to stop
>
> the resource
>
> For more information, click
>
> http://www.microsoft.com/contentredirect.asp.
> Data:
> 0000: 00 00 00 00 ....
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Services
> Event ID: 1069
> Date: 12/16/2005
> Time: 9:25:21 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Cluster resource 'Exchange System Attendant' failed.
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Services
> Event ID: 1069
> Date: 12/16/2005
> Time: 9:25:23 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> Cluster resource 'Exchange System Attendant' failed.
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7031
> Date: 12/16/2005
> Time: 9:25:23 PM
> User: N/A
> Computer: SRV-COCL1
> Description:
> The Microsoft Exchange System Attendant service terminated
>
> unexpectedly. It has done this 1 time(s). The following corrective
>
> action will be taken in 0 milliseconds: No action.
>
> Here are some of the errors from the cluser.log:
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource:
> created
> resource be3de5ed-5bc2-4435-a0eb-a3ddbf5eaa76, resid 1034040
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] Initializing resource
> 6bd4cacf-5993-4b08-927f-612f7d311979 from the registry.
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] Name for Resource
> 6bd4cacf-5993-4b08-927f-612f7d311979 is 'EX-CO'.
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource:
> creating resource 6bd4cacf-5993-4b08-927f-612f7d311979 in shared resource
> monitor
> 000008cc.00000924::2005/12/16-21:06:30.492 Network Name <EX-CO>: Unable to
> read resource data parameter, error=2
> 000008cc.00000924::2005/12/16-21:06:30.492 Network Name <EX-CO>: Unable to
> read creating DC parameter, error=2
> 000008cc.00000924::2005/12/16-21:06:30.492 Network Name <EX-CO>:
> Successful
> open of resid 638664
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource:
> created
> resource 6bd4cacf-5993-4b08-927f-612f7d311979, resid 1035208
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] Initializing resource
> 6531dd31-7442-4568-a757-a317898508dc from the registry.
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] Name for Resource
> 6531dd31-7442-4568-a757-a317898508dc is 'Exchange System Attendant'.
> 00000714.00000724::2005/12/16-21:06:30.492 [FM] FmpRmCreateResource:
> creating resource 6531dd31-7442-4568-a757-a317898508dc in shared resource
> monitor
> 000008cc.000008d8::2005/12/16-21:06:30.507 Microsoft Exchange System
> Attendant <Exchange System Attendant>: [EXRES] Open requested.
> 000008cc.000008d8::2005/12/16-21:06:30.507 Microsoft Exchange System
> Attendant <Exchange System Attendant>: [EXRES] Could not read the registry
> key for the location of event logging levels, using default 0, the error
> code is 2.
> 00000714.00000774::2005/12/16-21:06:32.664 [GUM] GumSendUpdate: queuing
> update type 1 context 0
> 00000714.00000774::2005/12/16-21:06:32.664 [GUM] GumSendUpdate:
> Dispatching
> seq 25526 type 1 context 0 to node 1
> 00000714.00000774::2005/12/16-21:06:32.664 [DM] DmWriteToQuorumLog Entry
> Seq#=25526 Type=0 Size=148
> 00000714.00000774::2005/12/16-21:06:32.664 [DM] DmpUpdateCreateKey:
> Creating
> key <Resources\6531dd31-7442-4568-a757-a317898508dc\Parameters>...
> 00000714.00000774::2005/12/16-21:06:32.664 [DM] DmWriteToQuorumLog Entry
> Seq#=25526 Type=0 Size=148
> 00000714.00000774::2005/12/16-21:06:32.664 [GUM] GumSendUpdate: completed
> update seq 25526 type 1 context 0
> 00000714.00000724::2005/12/16-21:06:32.664 [FM] FmpRmCreateResource:
> created
> resource 6531dd31-7442-4568-a757-a317898508dc, resid 1043104
> 00000714.00000724::2005/12/16-21:06:32.664 [FM] Initializing resource
> c6c0788b-6cfc-4210-a864-a37e16174bd4 from the registry.
> 00000714.00000724::2005/12/16-21:06:32.664 [FM] Name for Resource
> c6c0788b-6cfc-4210-a864-a37e16174bd4 is 'Disk J:'.
> 00000714.00000724::2005/12/16-21:06:32.664 [FM] FmpRmCreateResource:
> creating resource c6c0788b-6cfc-4210-a864-a37e16174bd4 in shared resource
> monitor
>
>
date: Tue, 31 Jan 2006 17:54:43 +0100
author: Evo
|
|
