| Author |
 Topic  |
|
|
MadCow
Honorable But Hopeless Addict
Canada
1484 Posts
Status: offline |
 Posted - 07/25/2008 : 10:03:08 AM
|
Node failed successfully this morning but very curious to find out the failure cause.
Application Log show this on the failed Node:
Event Type: Error
Event Source: ClusSvc
Event Category: Failover Mgr
Event ID: 1069
Date: 7/25/2008
Time: 8:53:14 AM
User: N/A
Computer: ExchangeNODEB
Description:
Cluster resource 'Exchange HTTP Virtual Server Instance 100 (EVS1)' in Resource Group 'Exchange Group' failed.
and this is the email I received from my MOM Server later ....
Severity: Error
Status: New
Source: MSExchangeCluster
Name: Cluster service failed the Isalive check for the resource.
Description: Exchange HTTP Virtual Server Instance 100 (EVS1): The IsAlive check for this resource failed.
Domain: FOREST1
Agent: ExchangeNODEB
Time: 7/25/2008 08:53:14
Owner:
(view with http://MOM001:1272/?v=a&id=EC5EBBE7-E4B6-4F37-BD1A-354244F81559)
Advise Please.
Thank you.
|
Sunny
__________________________________________________________________________
"Everyone is susceptible to the notion that when you begin to do well, you begin to see no boundary lines and forget the rules apply" - Eliot Spitzer
|
|
|
clarinathan
Moderator
United Kingdom
4774 Posts
Status: offline |
Posted - 07/25/2008 : 3:10:04 PM
|
Well that doesn't give much to go on does it :)
A really useful error message.......
Are you getting anything logged in the Cluster.log file?
Cheers
Nathan |
Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.
Checkout the Messaging and Mobility User Group: http://www.mmmug.co.uk
Checkout my blog:
Unified Comms: - http://www.nathanwinters.co.uk |
 |
|
|
clarinathan
Moderator
United Kingdom
4774 Posts
Status: offline |
|
|
MadCow
Honorable But Hopeless Addict
Canada
1484 Posts
Status: offline |
Posted - 07/28/2008 : 09:04:01 AM
|
Thank you for your response.
I have read that link but not of much use for me at this point.
There is lots of information in the log .... the time is in some weird format but I searched for the word "failed" and repeatedly see the following ... so I picked this line from the cluster.log on the failed node.
Exchange HTTP Virtual Server Instance 100 (EVS1): The IsAlive check for this resource failed. Error Code: 10054.
|
Sunny
__________________________________________________________________________
"Everyone is susceptible to the notion that when you begin to do well, you begin to see no boundary lines and forget the rules apply" - Eliot Spitzer
|
Edited by - MadCow on 07/28/2008 09:55:55 AM |
|
|
|
clarinathan
Moderator
United Kingdom
4774 Posts
Status: offline |
Posted - 07/28/2008 : 1:24:55 PM
|
Seems like that service failed on the cluster node (or at least didn't respond.)
The question is why though.... unfortunately more info is needed.
That error code seems to often be associated with connection reset by server although not sure that is relevant in this context....?
Have you installed any updates recently
cheers
Nathan |
Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.
Checkout the Messaging and Mobility User Group: http://www.mmmug.co.uk
Checkout my blog:
Unified Comms: - http://www.nathanwinters.co.uk |
|
|
|
MadCow
Honorable But Hopeless Addict
Canada
1484 Posts
Status: offline |
Posted - 07/28/2008 : 1:46:09 PM
|
Thank you for your response.
nothing was installed/modified. |
Sunny
__________________________________________________________________________
"Everyone is susceptible to the notion that when you begin to do well, you begin to see no boundary lines and forget the rules apply" - Eliot Spitzer
|
|
|
|
MadCow
Honorable But Hopeless Addict
Canada
1484 Posts
Status: offline |
Posted - 11/06/2008 : 5:52:37 PM
|
Microsoft applied a Hotfix for this IsAlive on my Exchange Nodes.
Its KB899485 but only available when you contact the mothership it is not available online.
|
Sunny
__________________________________________________________________________
"Everyone is susceptible to the notion that when you begin to do well, you begin to see no boundary lines and forget the rules apply" - Eliot Spitzer
|
|
|
|
philrobeson
Here To Stay
USA
165 Posts
Status: offline |
Posted - 11/07/2008 : 07:01:12 AM
|
| I'm sorry I didn't see this earlier...we had this problem a couple of months ago and that Hotfix you mentioned (KB899485) is what fixed ours as well. In the future, though, if you know of anyone who also runs into this problem, tell them to set the HTTP resource so it does not affect the group upon failure...they may not have OWA for the accounts on that server while they are fixing it, but they'll still have mail. |
Phil Robeson
MIS/M, MCSE |
|
|
|
MadCow
Honorable But Hopeless Addict
Canada
1484 Posts
Status: offline |
Posted - 12/09/2008 : 4:21:27 PM
|
FYI.
The issue was back even after slapping the hotfix and now applied this registry entry and since then it seems to be stable.. ....
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
Type: REG_DWORD
Name: EnableAggressiveMemoryUsage
Value: 1
Apply only on the node which is spitting the IsAlive Error.
|
Sunny
__________________________________________________________________________
"Everyone is susceptible to the notion that when you begin to do well, you begin to see no boundary lines and forget the rules apply" - Eliot Spitzer
|
|
|
| |
Topic |
|
Cluster Node Bounced ...
