Exchange server 2003 SP2 causes the information store on the new server to not be able to start.
- From: "NICk" <nciero@xxxxxxxxx>
- Date: 19 May 2006 17:32:02 -0700
During the course of an Exchange migration, my new Exchange server died
after applying SP2. It is a 2000 server domain with an existing 2000
exchange server. They are all SP4. The new server is a brand new Dell
2800 with Windows 2003 server standard with sp1 and all hotfixes
applied prior to the install of Exchange 2003 Enterprise.
After installing Exchange 2003 Enterprise, I installed SP2 and the
information store as well as all other key services cannot be
restarted. This happened during the course of an Exchange migration
project. After preparing the existing 2000 server domain using adprep I
installed Exchange 2003 Enterprise on a new box and made it a part of
the existing Exchange org in preparation for moving email, public
folders and all Exchange services over to the new box. I was getting
closer to the point of moving the email boxes over to the new server
when I decided to go ahead and install Exchange 2003 SP2. After I
installed SP2 the information store became unavailable. I tried
re-installing the service pack and as well restarting the services, but
to no avail. The only error I get in the event log is a 2104
MSExchangeDSAccess . Basically the it equates to the exchange server
not being able to access the domain controllers. Both DC's had thier
Schema sucessfully modified and all was well (I had even created a test
user email account on the new server Exchange server and was able to
send mail both to and from that user account from the outside world)
All other functions on the network are functioning correctly. Will
thing I will note is that I did get some errors in regards to the
"network bridge" that I had created by bonding both NIC's on the new
Exchange server. The event log said something about a NIC bridge driver
error. When you go to view the NIC's in either control panel , or
directly, the hour glass appears for an infinate amount of time (the
time it would take Jesus to come back to the earth in flesh form).
Another note I will also add is that after having this issue I looked
around the web for answers. There was a microsoft article regarding
having to apply some hot fix prior to installing SP2. I tried applying
this after the fact and it hung up. So where I am at now is that the
old exchange server is still running. Users are unaffected by the new
server (thank god I did'nt move the mail boxes over yet, guess I have
been burned enough times so that I had at least that much forethought.)
I find it incredibly ironic that the application of a service pack
will actually break your server! It was all installed and ready to go,
I followed all the MS articles and how tos to a "T". (No Im not
bitter....) Any help that anyone can give would be appreciated. Again I
have tried numerous times to restart, or heck just stop the services so
that maybe I could reinstall the , at first glance, successful install
of SP2.
So basically the new server is down. There are really no other peices
of software installed yet.
Any help would be great...otherwise I will have to call India on
Monday.
.
- Follow-Ups:
- Prev by Date: Re: Is 6GB mailbox insane??
- Next by Date: Re: Is 6GB mailbox insane??
- Previous by thread: Re: Restrict outgoing mail
- Next by thread: Re: Exchange server 2003 SP2 causes the information store on the new server to not be able to start.
- Index(es):
Relevant Pages
|
