Solved

server 2003 Failover cluster service fail to start

Posted on 2014-10-29
7
38 Views
Last Modified: 2016-06-14
Hi There, We have an 2003 Exchange Server failover cluster on two Windows 2003 enterprise SP2. Everything was ok until I failover to server2 and then restart the server1. The cluster service on server1 keep failing/stoping. When I check the cluster.log file I see this error below. Server2 cluster service is running just fine and is the active node. Both server has ran 5+ year with no problem with failover.

2014/10/29-20:07:42.153 ERR  [INIT] Unable to bind RPC to CDP, status 1703.
2014/10/29-20:07:42.153 ERR  [CS] ClusterInitialize failed 1703

I look up error code 1703 =  "The RPC protocol sequence not supported"

I have try to reset the tcp/ip and winsock using "netsh int ip reset" and "netsh winsock reset" and restart the server1. cluster service still fail to run and return same error code 1703.

I have check the registry of both server and protocol sequence are the same.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider

Rpc_Binding_Order = "ncacn_ip_tcp,ncacn_spx,ncacn_np,NETBIOS"
Rpc_Svr_Binding_Order = "ncacn_ip_tcp,ncacn_spx,ncacn_vns_spp"

Any suggestion?

Thanks
Tom - Network Admin
0
Comment
Question by:Fiducial_IT
  • 3
  • 3
7 Comments
 
LVL 19

Expert Comment

by:Delphineous Silverwing
Comment Utility
Here's a standard question - What changed?

Did someone perhaps evict the failing node from the cluster? Check the HKLM registry for the cluster hive on the working node. If the failing node is not listed, then it was evicted.
0
 

Author Comment

by:Fiducial_IT
Comment Utility
Only Issue we were having was we can't RDP- remote desktop to the server1.  Everything else on server1 was working ok (active node) for Exchange cluster, and file sharing server.  AFter we failover to server2 I had to hard power-off server1 since it was hung up on the shutdown process and never shutdown.

Yes- when server1 was having issue starting clsuter service I did evicted from the cluster and then re-added back. server2 was able to add server1 back to the cluster but fail to remote start the cluster service on server1.  Server1 show up on the cluster manager  with red X.
0
 
LVL 19

Expert Comment

by:Delphineous Silverwing
Comment Utility
When the node is evicted, the resource registrations are destroyed. The Exchange server cannot simply rejoin the cluster.

You'll need to uninstall Exchange from the failing node, evict it from the cluster and rejoin, then reinstall Exchange Server.
0
The problems with reply email signatures

Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

 

Author Comment

by:Fiducial_IT
Comment Utility
Good news,
I was able to add the 2nd node back to the exchange cluster service without uninstall exchange on the failing node.  It turn out the CSA account profile on the failing node was corrupted.  AFter re-created the profile I was able to run the add a cluster wizard and it join the cluster and start the clustering service just fine.  

only issue now when I do an failover  the  exchange infomation store instant fail to start on the node2. I think this is due to me uninstalling symantec Mail security since I read other are having similar issue as well with SMSE.
0
 
LVL 19

Expert Comment

by:Delphineous Silverwing
Comment Utility
It has been a couple years, but the last version of SMSE I worked with was not cluster aware/specific. Even though it is installed on one node, not being present on the other node will not keep Exchange from coming online.

The resource information for Exchange needs to be rewritten to the registry. This is where the Exchange reinstall becomes necessary.
0
 

Accepted Solution

by:
Fiducial_IT earned 0 total points
Comment Utility
Thank for your input. I luck out and it was Symantec Mail security for exchange that was the cause.  After re-installing SMSE I was able to failover and start all the exchange services.

The actual error was "Error 0x3ee starting the Microsoft Exchange Information Store. Failed to init VSERVER. " this was what causing the cluster service "Microsoft Exchange Information Store Instance" to fail.

Ticket can be closed
0

Featured Post

Want to promote your upcoming event?

Are you going to an event? Are you going to be exhibiting at a tradeshow? Talking at a conference? Using a promotional banner in your email signature ensures that your organization’s most important contacts stay in the know and can potentially spread the word about the event.

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now