Solved

Exchange 2003 sp2 install hangs stopping services on new w2k3 sp2 box

Posted on 2007-04-10
10
918 Views
Last Modified: 2011-09-20
I am bringing up a new exchange 2003 server that will replace my current excahnge 2003 server.  So, this should be a straight install, transfer the mailboxes and roles, and remove the old server.....

However, I have installed the brand new server with w2k3 sp2, then updated the box with all the windows updates and drivers.  I installed exchange 2003 on the box without incident and it joined the existing admin group.  System Admin works fine.  Fantasic.  When I attempt to install excahnge sp2 on the new box the install ALWAYS hangs on stopping the services.  If I kill the process on the first service MTA, it then hangs at the next service and I have to kill each service one by one to get them to stop.

The old server is w2k3 sp1 with excahnge 2003 sp2.  The new server is w2k3 sp2 with excahnge 2003 no sp (fresh from cd).

I am logging into the new exchange server with the exchange admin account that I created when I origianlly migrated to E2k3.  That account is a member of the local admin group as well.

Is there a problem with w2k3 sp2?  Do I need to install exchange sp1 first?  Am I just missing a permissions problem?  My gut tells me to wipe the box and start over.  If that is the case can I simply do the following?:
1. uninstall exchange
2. disjoin from domain
3. wipe the box
4. clean dns
5. reload the box with the same name and start all over....

Thanks
John
0
Comment
Question by:questinc
  • 6
  • 4
10 Comments
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
You can wipe the machine using the mini list that you have provided above. I would probably be tempted to do the same.
There are no issues that I am aware of with Exchange 2003 SP2 and Windows 2003 SP2, so I don't think that would be the cause.
After installing Exchange, did you reboot the server?
Is there anything else on the machine, AV etc?

Simon.
0
 

Author Comment

by:questinc
Comment Utility
I have tried to reboot the server several times.  AV is not installed nor any other program.  Just the OS with a few performance tuning things like the boot.ini mod for /3gb and USERVA.  I do have Dell Open Manage as well, but I have used that before without issue.  I shoud be able to go directly to excahnge sp2 correct?  
I figure that I probably could get it to install by stopping all the services, though sometime tells me I will have problems with the server down the road.  
I did notice that for some reason I started to get this warning in ExBPA: Cannot connect to the routing master on port 691 on the old excahnge server.  The old server is hanging on by a thread which is why I am trying to get this new serer up ASAP and get the mailboxes moved.  I dont think that error is related but I thought I would throw it out there.

Cheers,
John
0
 

Author Comment

by:questinc
Comment Utility
I dismissed this as being the same warning to ignore with sp1, but when I went to install exchange on the w2k3 sp2 box I got the normal compatability warning that referenced the exchange 2003 server requirements via link 37488
http://www.microsoft.com/technet/prodtechnol/exchange/2003/sysreqs.mspx
even though all the requirements seem to been met.  Am I possibly missing a hotfix or update I need to apply before I install excahnge sp2?

The 2003 server install seeems fine.  Can I uninstall exchange and then reinstall without wiping the system or should I start all over?
Thanks
John
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
Comment Utility
You always get a warning when doing anything with Exchange 2003 on Windows 2003 SP1 or higher. There is an issue with clustering (IIRC) so most people can ignore it.

If you are getting problems connecting to the other server or the domain controllers then that would explain why the services fail to stop correctly. When you stop the services there are other things that are going on in the back ground.

Before you start wiping the machine, see whether switching the routing master to the new machine makes things move a little faster.

Simon.
0
 

Author Comment

by:questinc
Comment Utility
I switched the roles, restarted the server and then ran the update again.  It hung stopping the services. I did check to make sure the exchange security groups are still in the Users OU.   I am hesitant to keep it this way since this new server is not in production in any manner.

I did find that I could not telnet to 691 on the old exchange server even from itself.  I discovered the Exchange Routing Service was stopped (dont know why). It is set to automatic.  Once I started that I was able to telnet to 691 and the ExBPA came clean on that error.

I also found a bad DNS entry for the new exchange server pointing to an old address.  I updated the DNS records.

After doing all this I restarted the server again.  Waited about 10 minutes and then re-ran the update.  It hang stopped the System Attendant service.  I seem to remember something about XML version and the system attendant service.

Could the problems stem from connectivity or general issues with the current and soon to be replaced exchange server?  If so, reloading the new server 100 times would not help.
John

0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 

Author Comment

by:questinc
Comment Utility
The SA service finally stopped and the install completed.  I think it was a combination of the DNS issue which was messing with the SA service and maybe the routing service not running on the older server.

Thanks for your help.
John
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
If there are communication problems then that can cause problems.
What wiping the machine will often show is that the problem is outside of the machine. The problem continues after the rebuild.

Simon.
0
 

Author Comment

by:questinc
Comment Utility
Well, I when I installed the DST exchange patch it took the SA service 1 hour to stop.  IT finally did stop and install the patch.  No errors are in the logs to clue me in on why it is taking so long for the service to stop.  When I run EXBPA I have no issues on the new box except a few warnings about smpt and such (normal things)  In your opinion should I reload to rule our botched initial exchange install?  I cant have a production box that takes that long to install an updates as often as they happen.  The server does not experience any delay shutting down or starting up.  Only installing exchange updates.
0
 

Author Comment

by:questinc
Comment Utility
We just completed a move and folded 3 offices into one.  As a result we just ran dcpromo on two dcs.  I noticed that they are still in the recipient updates services list as connections 4 and 8.  Can I manually delete them out?  Could this be messing with the SA service?  They are still on the network just not a dc or gc anymore.
John
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
That is not the standard behaviour of Exchange. The services should not take that long to stop. I would therefore suspect that something is wrong within the server or domain.

The list of domain controllers is automatically updated by Exchange. If you restart the server the list should be updated. If it is not, then I would check that Exchange has a valid global catalog server available and that the DNS is configured correctly.

Those problems would tend to indicate an issue with AD, not Exchange.

Simon.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Resolve DNS query failed errors for Exchange
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…

763 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

9 Experts available now in Live!

Get 1:1 Help Now