Borked Exchange Server

[DSapseid]

Right my exchange server has been having a right paddy this morning i am currently runnning the diagnostic windows thingy to find what is wrong with it.

 

The question is that i feel i need to rebuild it an start again, i am just about to order a new secondary file server so could i put exchange on that, migrate it across. Rebuild current exchange then remigrate it back and put server 2008 on the new server?

 

Will that consfuse it?? Are there any docs as to how to successfully migrate exchange from one server to another. Both will be exchange 2003, or shall i take the opportunity to upgrade to 2007??

[Michael]

Whatever the problems are, I really wouldn't be considering upgrading to Exchange 2007 or upgrading to Windows Server 2008 in the position you're in.

 

Depending on what problem(s) you're having, do you have any error messages or anything to give us a clue what's happening? And if all else fails, do you have a backup so you can restore Exchange?

[DSapseid]

No error messages, most of the services are refusing to start giving some bizarre error about RPC server not being started when it is. Cant be pinged but can ping. Really bizarre! :confused:

[Michael]

The RPC (Remote Procedure Call) is a very important service as (to my knowledge) pretty much every other service has dependencies on it. I would recommend you reboot at the earliest opportunity and report back on your findings.

[DSapseid]

Have rebooted about 5 times and no difference!!

[apeo]

Does the eventlog tell you why the rpc service is failing?

[DSapseid]

Fixed it buy upgrading to R2 :confused: I thought the upgrade might fix any corrupted files and it did. Have persuaded management to let us have new server in summer though! Or before if it does it again!