server 2003 Failover cluster service fail to start

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
Fiducial_ITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Delphineous SilverwingGood Ol' GeekCommented:
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
Fiducial_ITAuthor Commented:
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
Delphineous SilverwingGood Ol' GeekCommented:
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
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Fiducial_ITAuthor Commented:
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
Delphineous SilverwingGood Ol' GeekCommented:
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
Fiducial_ITAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.