|
|
|
date: Tue, 20 Nov 2007 13:25:38 +0100,
group: microsoft.public.exchange.clustering
back
Exchange 2007 CCR - Cluster Node Problem
000fa8.00000fb4::2007/11/20-09:16:54.212 WARN [INIT] The cluster service is shutting down.
00000fa8.00000fb4::2007/11/20-09:16:54.212 WARN [FM] Shutdown: Failover Manager requested to shutdown groups.
00000950.000009b4::2007/11/20-09:16:54.556 WARN [RM] Going away, Status = 1, Shutdown = 0.
00000950.000009b4::2007/11/20-09:16:54.556 ERR [RM] Active Resource = 00000000
00000950.000009b4::2007/11/20-09:16:54.556 ERR [RM] Resource State is 1, ""
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <Second Storage Group/Public Folder Database (STCMAIL)>: [EXRES] ExchangeResourceControl: Received state change reason 5 (Rundown)
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <First Storage Group/Mailbox Database (STCMAIL)>: [EXRES] ExchangeResourceControl: Received state change reason 5 (Rundown)
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Information Store <Exchange Information Store Instance (STCMAIL)>: [EXRES] ExchangeResourceControl: Received state change reason 5 (Rundown)
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange System Attendant <Exchange System Attendant Instance (STCMAIL)>: [EXRES] ExchangeResourceControl: Received state change reason 5 (Rundown)
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <Second Storage Group/Public Folder Database (STCMAIL)>: [EXRES] ExchangeClose: Close requested.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <Second Storage Group/Public Folder Database (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: Count=0.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <Second Storage Group/Public Folder Database (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: releasing resource private data.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <First Storage Group/Mailbox Database (STCMAIL)>: [EXRES] ExchangeClose: Close requested.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <First Storage Group/Mailbox Database (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: Count=0.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Database Instance <First Storage Group/Mailbox Database (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: releasing resource private data.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Information Store <Exchange Information Store Instance (STCMAIL)>: [EXRES] ExchangeClose: Close requested.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Information Store <Exchange Information Store Instance (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: Count=0.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange Information Store <Exchange Information Store Instance (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: releasing resource private data.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange System Attendant <Exchange System Attendant Instance (STCMAIL)>: [EXRES] ExchangeClose: Close requested.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange System Attendant <Exchange System Attendant Instance (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: Count=0.
00000950.000009b4::2007/11/20-09:16:54.556 WARN Microsoft Exchange System Attendant <Exchange System Attendant Instance (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::Release: releasing resource private data.
00000a50.00000bbc::2007/11/20-09:20:05.902 WARN [JOIN] JoinVersion data for sponsor 172.30.124.95 is invalid, status 1722.
00000a50.00000bb4::2007/11/20-09:20:34.841 WARN [JOIN] Unable to resolve JoinVersion endpoint for sponsor 10.10.0.11, status 1726.
00000a50.00000bb4::2007/11/20-09:20:34.841 WARN [JOIN] JoinVersion data for sponsor 10.10.0.11 is invalid, status 1726.
00000a50.00000bb0::2007/11/20-09:20:35.839 WARN [JOIN] Unable to resolve JoinVersion endpoint for sponsor 172.30.124.92, status 1726.
00000a50.00000bb0::2007/11/20-09:20:35.839 WARN [JOIN] JoinVersion data for sponsor 172.30.124.92 is invalid, status 1726.
00000a50.00000bb8::2007/11/20-09:20:35.839 WARN [JOIN] Unable to resolve JoinVersion endpoint for sponsor STOMAIL02, status 1726.
00000a50.00000bb8::2007/11/20-09:20:35.839 WARN [JOIN] JoinVersion data for sponsor STOMAIL02 is invalid, status 1726.
00000a50.00000ae8::2007/11/20-09:20:35.839 ERR [JOIN] Unable to connect to any sponsor node.
00000a50.00000ae8::2007/11/20-09:20:35.839 WARN [INIT] Failed to join cluster, status 53
00000a50.00000ae8::2007/11/20-09:20:35.839 ERR [FM] Failed to get quorum disk signature, error 2.
00000d48.00000d60::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: FsArb: Creating arbitration thread
00000d48.00000d68::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: ArbitrateThread begin: ActiveMemberBitmask 0x6 MNSFileShare: \\stomail03\MNS_FSW_STCMAIL
00000d48.00000d68::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: ArbitrateThread current AliveSet=0
00000d48.00000d74::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: Probing for connectivity to fileshare \\stomail03\MNS_FSW_STCMAIL
00000d48.00000d7c::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: Probe thread for Replica 1 Addr 10.10.0.10
00000d48.00000d78::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: Probe thread for Replica 2 Addr 10.10.0.11
00000d48.00000d80::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: Probe thread for Replica 1 Addr 172.30.124.91
00000d48.00000d84::2007/11/20-09:20:36.042 ERR Majority Node Set <Majority Node Set>: Probe thread for Replica 2 Addr 172.30.124.92
00000d48.00000d7c::2007/11/20-09:20:36.058 ERR Majority Node Set <Majority Node Set>: CreateTreeConnection(10.10.0.10\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 0x0 hdl 0x33c
00000d48.00000d80::2007/11/20-09:20:36.058 ERR Majority Node Set <Majority Node Set>: CreateTreeConnection(172.30.124.91\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 0x0 hdl 0x32c
00000d48.00000d78::2007/11/20-09:20:36.058 ERR Majority Node Set <Majority Node Set>: CreateTreeConnection(10.10.0.11\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 0x0 hdl 0x340
00000d48.00000d84::2007/11/20-09:20:36.058 ERR Majority Node Set <Majority Node Set>: CreateTreeConnection(172.30.124.92\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 0x0 hdl 0x330
00000d48.00000d7c::2007/11/20-09:20:36.058 ERR Majority Node Set <Majority Node Set>: Probe Thread probe replica 1 suceeded, ShareSet 2
00000d48.00000d74::2007/11/20-09:20:40.036 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:20:45.028 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:20:50.020 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:20:55.013 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:00.005 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:04.997 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:09.989 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:14.982 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:19.974 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:24.966 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:29.958 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:34.950 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:39.943 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:44.935 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:49.927 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:54.919 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:21:59.912 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:04.904 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:09.896 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:14.888 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:19.880 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:24.873 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:29.865 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000d48.00000d74::2007/11/20-09:22:34.857 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000a50.00000ae8::2007/11/20-09:22:35.856 ERR [FM] FmGetQuorumResource failed, error 1223.
00000a50.00000ae8::2007/11/20-09:22:35.856 ERR [INIT] ClusterForm: Could not get quorum resource. No fixup attempted. Status = 5086
00000a50.00000ae8::2007/11/20-09:22:35.856 ERR [INIT] Failed to form cluster, status 5086.
00000a50.00000ae8::2007/11/20-09:22:35.856 ERR [CS] ClusterInitialize failed 5086
00000a50.00000ae8::2007/11/20-09:22:35.856 WARN [INIT] The cluster service is shutting down.
00000a50.00000ae8::2007/11/20-09:22:35.856 WARN [FM] Shutdown: Failover Manager requested to shutdown groups.
00000a50.00000ae8::2007/11/20-09:22:35.871 WARN [MM] MMLeave is called when rgp=NULL.
00000a50.00000ae8::2007/11/20-09:22:35.871 ERR [CS] Service Stopped. exit code = 5086
00000d48.00000d4c::2007/11/20-09:22:36.090 WARN [RM] Going away, Status = 1, Shutdown = 0.
00000d48.00000d4c::2007/11/20-09:22:36.090 ERR [RM] Active Resource = 00000000
00000d48.00000d4c::2007/11/20-09:22:36.090 ERR [RM] Resource State is 1, ""
00000d48.00000d4c::2007/11/20-09:22:36.090 ERR Majority Node Set <Majority Node Set>: FsExit Active volume at exit, Root=2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$
00000d48.00000d74::2007/11/20-09:22:39.849 ERR Majority Node Set <Majority Node Set>: CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc881965f14$) returned 183
00000fb4.00000fc0::2007/11/20-09:23:41.269 ERR [DM] DmInitialize: The hive was loaded- rollback, unload and reload again
00000fb4.00000fc0::2007/11/20-09:23:41.332 WARN [JOIN] Attempting join with sponsor 10.10.0.11.
00000fb4.00000fc0::2007/11/20-09:23:41.441 WARN [MM] MmQuorumArbitrationTimeout 180.
00000fb4.00000fc0::2007/11/20-09:23:42.065 WARN [NM] Cryptor: Data is not encrypted.
00000fb4.00000fc0::2007/11/20-09:23:42.065 WARN [NM] Cryptor received unencrypted data.
00000fb4.00000fc0::2007/11/20-09:23:42.065 WARN [DM] Obtained new database.
00000fb4.00000fc0::2007/11/20-09:23:42.065 WARN [DM] DmpSafeDatabaseCopy:: SetFileAttrib on BkpPath C:\WINDOWS\Cluster\CLUSDB.BKP$ failed, Status=2
00000930.00000a7c::2007/11/20-09:23:42.627 WARN Network Name <Cluster Name>: Unable to read ResourceData parameter, error=2
00000930.00000a7c::2007/11/20-09:23:42.627 WARN Network Name <Cluster Name>: Unable to read CreatingDC parameter, error=2
00000930.00000a7c::2007/11/20-09:23:42.642 WARN Microsoft Exchange System Attendant <Exchange System Attendant Instance (STCMAIL)>: [EXRES] ExchangeOpen: Open requested.
00000930.00000a7c::2007/11/20-09:23:42.658 WARN Microsoft Exchange System Attendant <Exchange System Attendant Instance (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::AddRef: Count=1.
00000930.00000a78::2007/11/20-09:23:42.658 WARN Microsoft Exchange Information Store <Exchange Information Store Instance (STCMAIL)>: [EXRES] ExchangeOpen: Open requested.
00000930.00000a78::2007/11/20-09:23:42.658 WARN Microsoft Exchange Information Store <Exchange Information Store Instance (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::AddRef: Count=1.
00000930.00000a7c::2007/11/20-09:23:42.658 WARN Microsoft Exchange Database Instance <First Storage Group/Mailbox Database (STCMAIL)>: [EXRES] ExchangeOpen: Open requested.
00000930.00000a7c::2007/11/20-09:23:42.658 WARN Microsoft Exchange Database Instance <First Storage Group/Mailbox Database (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::AddRef: Count=1.
00000930.00000a78::2007/11/20-09:23:42.658 WARN Microsoft Exchange Database Instance <Second Storage Group/Public Folder Database (STCMAIL)>: [EXRES] ExchangeOpen: Open requested.
00000930.00000a78::2007/11/20-09:23:42.658 WARN Microsoft Exchange Database Instance <Second Storage Group/Public Folder Database (STCMAIL)>: [EXRES] EXCHANGE_RESOURCE::AddRef: Count=1.
00000fb4.00000ff8::2007/11/20-09:23:43.173 WARN [FM] FmDeleteResourceType: Resource type Microsoft Message Queue Server does not exist...
00000fb4.00000fc0::2007/11/20-09:23:43.173 WARN [EVT] Set propagation state to 0000
00000fb4.000008a4::2007/11/20-09:23:43.438 WARN [FM] FmDeleteResourceType: Resource type IIS Server Instance does not exist...
00000fb4.00000ff8::2007/11/20-09:23:43.438 WARN [FM] FmDeleteResourceType: Resource type SMTP Server Instance does not exist...
00000fb4.000008a4::2007/11/20-09:23:43.438 WARN [FM] FmDeleteResourceType: Resource type NNTP Server Instance does not exist...
00000fb4.00000ff8::2007/11/20-09:23:43.438 WARN [FM] FmDeleteResourceType: Resource type IIS Virtual Root does not exist...
00000fb4.000008a4::2007/11/20-09:23:43.438 WARN [FM] FmDeleteResourceType: Resource type Time Service does not exist...
date: Tue, 20 Nov 2007 13:25:38 +0100
author: Jamelia
Re: Exchange 2007 CCR - Cluster Node Problem
Dear Jamelia,
Just looking at the very limited sniplet of the cluster.log, here are my
findings purely based on the cluster.log file
The cluster-node tries to join the cluster, but for some reason cannot
"talk" to the other nodes:
2007/11/20-09:20:05.902 WARN [JOIN] JoinVersion data for sponsor
172.30.124.95 is invalid, status 1722.
Status 1722 means RPC_S_SERVER_UNAVAILABLE
Then you see:
2007/11/20-09:20:35.839 WARN [JOIN] JoinVersion data for sponsor STOMAIL02
is invalid, status 1726.
Status 1726 means RPC_S_CALL_FAILED
Finally it gives up trying to join:
2007/11/20-09:20:35.839 ERR [JOIN] Unable to connect to any sponsor node.
Next step for the node is to form its own cluster, and will try to get
control on the Quorum resource (File Share Witness in this case)
You can see it accessing the FSW:
2007/11/20-09:22:34.857 ERR Majority Node Set <Majority Node Set>:
CreateDirectory(\\stomail03\MNS_FSW_STCMAIL\2d4d4f9e-8c3e-4c22-8a53-3dc88196
5f14$) returned 183
The return code 183 means ERROR_ALREADY_EXISTS
From this we can conclude that the other node is still alive and defending
the Arbitration.
2007/11/20-09:22:35.856 ERR [INIT] ClusterForm: Could not get quorum
resource. No fixup attempted. Status = 5086
Status 5086 means ERROR_QUORUM_DISK_NOT_FOUND
(old error defined before there were MNS/FSW clusters, but still the error
when a node cannot get quorum control)
This means 2 things:
1) this node cannot join the cluster
2) it cannot form the cluster and cannot get control on the quorum resource
Finally it has no other option than to terminate itself
2007/11/20-09:22:35.856 WARN [INIT] The cluster service is shutting down
This will result in the events in the system event log which you have posted
in your other post.
All this is proper behaviour of your cluster.
I would suggest that you start by looking at the network, why is this node
not capable of talking to the other nodes in the cluster.
HTH & Rgds,
Edwin.
"Jamelia" wrote in message
news:03941767-8686-4E23-A311-8C932645A9EB@microsoft.com...
> Hi,
>
> I have recently installed Exchange in an CCR environment and for some
reason
> I cant figure out, one of my cluster nodes is taking quit some time to
> startup after a normal reboot.
> There are some errors in the cluster log and if someone could help me to
> sort them out it would be very appreciated.
>
> Also, in the system log I see that both the cluster service and print
> spooler fail to start the first time but after another try they are both
> successful.
>
> Regards,
> Jamelia
>
date: Wed, 21 Nov 2007 09:44:55 -0000
author: Edwin vMierlo [MVP]
Re: Exchange 2007 CCR - Cluster Node Problem
For the MSExchangeADAccess errors, see
http://support.microsoft.com/kb/298879/en-us and use the MinUseDC value.
For the MSExchangeTransportLogSearch errors, it's a know issue and can
safely be ignored on the passive node. From the MS site:
"Error with event ID 7005 is by design This error can be ignored. The
Microsoft Exchange Transport Log Search service
(MSExchangeTransportLogSearch) logs error event ID 7005
(ComputerNameNotCurrentlyAvailableException) every 10 minutes on the passive
node in a cluster. This action occurs because MSExchangeTransportLogSearch
can't obtain the configuration of a clustered mailbox server. On clustered
nodes, the Mailbox server name is not the same as Environment.MachineName
Therefore, MSExchangeTransportLogSearch can't find the local server, which
is what is used to perform message tracking searches. The transport log
search service works only on the active node; on the passive node, it just
waits to become active. "
"Jamelia" wrote in message
news:54D73078-4B75-4E2E-86E6-20FEACE7F719@microsoft.com...
> Thank you all for your replies!!
>
> After some more troubleshooting it turned out that the troubling Cluster
> Node had the service "Windows Firewall/Internet Connection Sharing (ICS)"
> started but the Firewall was set to Offline.
>
> I change the startup type to manual and now the server boots up as
> expected and the Cluster- and Printer Service is starting up just fine.
>
> I do get some Exchange-related errors in the Application Log for
> MSExchange ADAccess and MSExchangeTransportLogSearch. It seems like these
> sources is trying to start before the cluster service does, but I dont
> think this is a clusterissu.
>
> Have a nice Day,
> Jamelia
>
>
>
>
> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
> news:eFGeAUDLIHA.1204@TK2MSFTNGP03.phx.gbl...
>> You have an RPC communications failure between the nodes (1722). You
>> could start by troubleshooting RPC connectivity.
>>
>>
>> "Jamelia" wrote in message
>> news:03941767-8686-4E23-A311-8C932645A9EB@microsoft.com...
>>> Hi,
>>>
>>> I have recently installed Exchange in an CCR environment and for some
>>> reason
>>> I cant figure out, one of my cluster nodes is taking quit some time to
>>> startup after a normal reboot.
>>> There are some errors in the cluster log and if someone could help me to
>>> sort them out it would be very appreciated.
>>>
>>> Also, in the system log I see that both the cluster service and print
>>> spooler fail to start the first time but after another try they are both
>>> successful.
>>>
>>> Regards,
>>> Jamelia
>>>
>>
>>
>
date: Wed, 21 Nov 2007 06:12:12 -0800
author: John Fullbright fjohn@donotspamnetappdotcom
Re: Exchange 2007 CCR - Cluster Node Problem
Forgot the link for the MS reference. It's the release notes.
http://download.microsoft.com/download/8/d/c/8dc5a8ca-e75e-47c0-b655-e0f82b90780d/RelNotes.htm
"John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
news:OSKsHiELIHA.6108@TK2MSFTNGP03.phx.gbl...
> For the MSExchangeADAccess errors, see
> http://support.microsoft.com/kb/298879/en-us and use the MinUseDC value.
>
> For the MSExchangeTransportLogSearch errors, it's a know issue and can
> safely be ignored on the passive node. From the MS site:
>
> "Error with event ID 7005 is by design This error can be ignored. The
> Microsoft Exchange Transport Log Search service
> (MSExchangeTransportLogSearch) logs error event ID 7005
> (ComputerNameNotCurrentlyAvailableException) every 10 minutes on the
> passive
> node in a cluster. This action occurs because MSExchangeTransportLogSearch
> can't obtain the configuration of a clustered mailbox server. On clustered
> nodes, the Mailbox server name is not the same as Environment.MachineName
> Therefore, MSExchangeTransportLogSearch can't find the local server, which
> is what is used to perform message tracking searches. The transport log
> search service works only on the active node; on the passive node, it just
> waits to become active. "
>
>
>
>
>
> "Jamelia" wrote in message
> news:54D73078-4B75-4E2E-86E6-20FEACE7F719@microsoft.com...
>> Thank you all for your replies!!
>>
>> After some more troubleshooting it turned out that the troubling Cluster
>> Node had the service "Windows Firewall/Internet Connection Sharing (ICS)"
>> started but the Firewall was set to Offline.
>>
>> I change the startup type to manual and now the server boots up as
>> expected and the Cluster- and Printer Service is starting up just fine.
>>
>> I do get some Exchange-related errors in the Application Log for
>> MSExchange ADAccess and MSExchangeTransportLogSearch. It seems like these
>> sources is trying to start before the cluster service does, but I dont
>> think this is a clusterissu.
>>
>> Have a nice Day,
>> Jamelia
>>
>>
>>
>>
>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> news:eFGeAUDLIHA.1204@TK2MSFTNGP03.phx.gbl...
>>> You have an RPC communications failure between the nodes (1722). You
>>> could start by troubleshooting RPC connectivity.
>>>
>>>
>>> "Jamelia" wrote in message
>>> news:03941767-8686-4E23-A311-8C932645A9EB@microsoft.com...
>>>> Hi,
>>>>
>>>> I have recently installed Exchange in an CCR environment and for some
>>>> reason
>>>> I cant figure out, one of my cluster nodes is taking quit some time to
>>>> startup after a normal reboot.
>>>> There are some errors in the cluster log and if someone could help me
>>>> to
>>>> sort them out it would be very appreciated.
>>>>
>>>> Also, in the system log I see that both the cluster service and print
>>>> spooler fail to start the first time but after another try they are
>>>> both
>>>> successful.
>>>>
>>>> Regards,
>>>> Jamelia
>>>>
>>>
>>>
>>
>
>
date: Wed, 21 Nov 2007 06:29:45 -0800
author: John Fullbright fjohn@donotspamnetappdotcom
Re: Exchange 2007 CCR - Cluster Node Problem
Thank you John for clearing this up for me about EventID 7005!
Do you know if its expected to have this errors as well:
Source: MSExchangeServiceHost
Event ID: 2011
Description: An unexpected failure has occurred. No modules were loaded and
the service will perform no work. Diagnostic information: The Windows
Cluster service encountered an error during function OpenCluster:
It seems to me that Exchange is trying to start all services before the
cluster node has joined the cluster. Its only at startup I see these
events...
Thanks again,
Jamelia
"John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
news:eubi4rELIHA.6008@TK2MSFTNGP05.phx.gbl...
> Forgot the link for the MS reference. It's the release notes.
>
> http://download.microsoft.com/download/8/d/c/8dc5a8ca-e75e-47c0-b655-e0f82b90780d/RelNotes.htm
>
>
> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
> news:OSKsHiELIHA.6108@TK2MSFTNGP03.phx.gbl...
>> For the MSExchangeADAccess errors, see
>> http://support.microsoft.com/kb/298879/en-us and use the MinUseDC value.
>>
>> For the MSExchangeTransportLogSearch errors, it's a know issue and can
>> safely be ignored on the passive node. From the MS site:
>>
>> "Error with event ID 7005 is by design This error can be ignored. The
>> Microsoft Exchange Transport Log Search service
>> (MSExchangeTransportLogSearch) logs error event ID 7005
>> (ComputerNameNotCurrentlyAvailableException) every 10 minutes on the
>> passive
>> node in a cluster. This action occurs because
>> MSExchangeTransportLogSearch
>> can't obtain the configuration of a clustered mailbox server. On
>> clustered
>> nodes, the Mailbox server name is not the same as Environment.MachineName
>> Therefore, MSExchangeTransportLogSearch can't find the local server,
>> which
>> is what is used to perform message tracking searches. The transport log
>> search service works only on the active node; on the passive node, it
>> just
>> waits to become active. "
>>
>>
>>
>>
>>
>> "Jamelia" wrote in message
>> news:54D73078-4B75-4E2E-86E6-20FEACE7F719@microsoft.com...
>>> Thank you all for your replies!!
>>>
>>> After some more troubleshooting it turned out that the troubling Cluster
>>> Node had the service "Windows Firewall/Internet Connection Sharing
>>> (ICS)" started but the Firewall was set to Offline.
>>>
>>> I change the startup type to manual and now the server boots up as
>>> expected and the Cluster- and Printer Service is starting up just fine.
>>>
>>> I do get some Exchange-related errors in the Application Log for
>>> MSExchange ADAccess and MSExchangeTransportLogSearch. It seems like
>>> these sources is trying to start before the cluster service does, but I
>>> dont think this is a clusterissu.
>>>
>>> Have a nice Day,
>>> Jamelia
>>>
>>>
>>>
>>>
>>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>>> news:eFGeAUDLIHA.1204@TK2MSFTNGP03.phx.gbl...
>>>> You have an RPC communications failure between the nodes (1722). You
>>>> could start by troubleshooting RPC connectivity.
>>>>
>>>>
>>>> "Jamelia" wrote in message
>>>> news:03941767-8686-4E23-A311-8C932645A9EB@microsoft.com...
>>>>> Hi,
>>>>>
>>>>> I have recently installed Exchange in an CCR environment and for some
>>>>> reason
>>>>> I cant figure out, one of my cluster nodes is taking quit some time to
>>>>> startup after a normal reboot.
>>>>> There are some errors in the cluster log and if someone could help me
>>>>> to
>>>>> sort them out it would be very appreciated.
>>>>>
>>>>> Also, in the system log I see that both the cluster service and print
>>>>> spooler fail to start the first time but after another try they are
>>>>> both
>>>>> successful.
>>>>>
>>>>> Regards,
>>>>> Jamelia
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
date: Wed, 21 Nov 2007 16:12:23 +0100
author: Jamelia
Re: Exchange 2007 CCR - Cluster Node Problem
MSExchangeServiceHost basically configures Outlook Anywhere on a CAS. A
clustered mailbox server has no CAS role, so this sounds normal to me.
John
"Jamelia" wrote in message
news:640006F5-A030-49E4-A51A-F9B44A557D75@microsoft.com...
> Thank you John for clearing this up for me about EventID 7005!
>
> Do you know if its expected to have this errors as well:
> Source: MSExchangeServiceHost
> Event ID: 2011
> Description: An unexpected failure has occurred. No modules were loaded
> and the service will perform no work. Diagnostic information: The Windows
> Cluster service encountered an error during function OpenCluster:
>
> It seems to me that Exchange is trying to start all services before the
> cluster node has joined the cluster. Its only at startup I see these
> events...
>
> Thanks again,
> Jamelia
>
>
>
>
> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
> news:eubi4rELIHA.6008@TK2MSFTNGP05.phx.gbl...
>> Forgot the link for the MS reference. It's the release notes.
>>
>> http://download.microsoft.com/download/8/d/c/8dc5a8ca-e75e-47c0-b655-e0f82b90780d/RelNotes.htm
>>
>>
>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> news:OSKsHiELIHA.6108@TK2MSFTNGP03.phx.gbl...
>>> For the MSExchangeADAccess errors, see
>>> http://support.microsoft.com/kb/298879/en-us and use the MinUseDC value.
>>>
>>> For the MSExchangeTransportLogSearch errors, it's a know issue and can
>>> safely be ignored on the passive node. From the MS site:
>>>
>>> "Error with event ID 7005 is by design This error can be ignored. The
>>> Microsoft Exchange Transport Log Search service
>>> (MSExchangeTransportLogSearch) logs error event ID 7005
>>> (ComputerNameNotCurrentlyAvailableException) every 10 minutes on the
>>> passive
>>> node in a cluster. This action occurs because
>>> MSExchangeTransportLogSearch
>>> can't obtain the configuration of a clustered mailbox server. On
>>> clustered
>>> nodes, the Mailbox server name is not the same as
>>> Environment.MachineName
>>> Therefore, MSExchangeTransportLogSearch can't find the local server,
>>> which
>>> is what is used to perform message tracking searches. The transport log
>>> search service works only on the active node; on the passive node, it
>>> just
>>> waits to become active. "
>>>
>>>
>>>
>>>
>>>
>>> "Jamelia" wrote in message
>>> news:54D73078-4B75-4E2E-86E6-20FEACE7F719@microsoft.com...
>>>> Thank you all for your replies!!
>>>>
>>>> After some more troubleshooting it turned out that the troubling
>>>> Cluster Node had the service "Windows Firewall/Internet Connection
>>>> Sharing (ICS)" started but the Firewall was set to Offline.
>>>>
>>>> I change the startup type to manual and now the server boots up as
>>>> expected and the Cluster- and Printer Service is starting up just fine.
>>>>
>>>> I do get some Exchange-related errors in the Application Log for
>>>> MSExchange ADAccess and MSExchangeTransportLogSearch. It seems like
>>>> these sources is trying to start before the cluster service does, but I
>>>> dont think this is a clusterissu.
>>>>
>>>> Have a nice Day,
>>>> Jamelia
>>>>
>>>>
>>>>
>>>>
>>>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>>>> news:eFGeAUDLIHA.1204@TK2MSFTNGP03.phx.gbl...
>>>>> You have an RPC communications failure between the nodes (1722). You
>>>>> could start by troubleshooting RPC connectivity.
>>>>>
>>>>>
>>>>> "Jamelia" wrote in message
>>>>> news:03941767-8686-4E23-A311-8C932645A9EB@microsoft.com...
>>>>>> Hi,
>>>>>>
>>>>>> I have recently installed Exchange in an CCR environment and for some
>>>>>> reason
>>>>>> I cant figure out, one of my cluster nodes is taking quit some time
>>>>>> to
>>>>>> startup after a normal reboot.
>>>>>> There are some errors in the cluster log and if someone could help me
>>>>>> to
>>>>>> sort them out it would be very appreciated.
>>>>>>
>>>>>> Also, in the system log I see that both the cluster service and print
>>>>>> spooler fail to start the first time but after another try they are
>>>>>> both
>>>>>> successful.
>>>>>>
>>>>>> Regards,
>>>>>> Jamelia
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
date: Wed, 21 Nov 2007 11:55:44 -0800
author: John Fullbright fjohn@donotspamnetappdotcom
|
|
