Exchange Server

Phil Ermiya · Guest

Hi

(Big long post, but I'd rather put too much info in than too little)

We've just in the process of migrating a customers site from NT4/E55 to
W2003/E2003.

Here's what our customer had.

NT4 PDC with E5.5 (Call it NT-MX)
4 x NT4 BDC's

Here's what we've done:
Installed a new NT4 server as a BDC and promoted to PDC. (Call it 2K3)
Installed W2003 over the top and did all the dcpromo magic.

So far, so good. Everyone could still log in and AD and the NT SAMs seemed
to be synchronising between the 2003 DC and the NT BDC's.

Next I joined another W2003 server to the Domain and ran dcpromo on it.
(Call this one 2K3-MX, as it will be the Exchange Server). Still good,
checked replication and all seemed fine.

Ran Forestprep and all seemed ok.
Ran DomainPrep, that said it installed ok.
Ran the Orgprepcheck and that (eventually) said everything was good

Running DCDIAG on each 2003 DC showed some errors, but these disappeared
after time (presumeably replication related).

Ran the Active Directory Connector, which installed fine. Ran through all
the wizzy bits on it (No problems with resource mailboxes - took there of
that before all this started by going through the 5.5 server). Setup the
connections between 2K3-MX and NT-MX.

Waited a while and looked through the AD User manager and lo and behold, I
could see Exchange server tabs populated with information from the 5.5 DS.

Installed Exchange 2003 and joined the existing organisation.

Here's where it goes pear shaped. After installation, Windows reported that
the application MAD.EXE crashed twice. I rebooted the server and checked the
services. The System Attendant service was set to Automatic, but not
running. The Information Store and MTA were up and running though.

Manually started the System Attendant, which runs for about 10 seconds
before falling over again.

Event Log says the Service Control Manager reports that the System Attendant
service terminated unexpectedly with event id 7034.
Also logged was an application error in MAD.EXE with the faulting module
being NTDLL.DLL

Running sc query on the system attendant service comes back with FAILED
1060 - not an installed service.

Installed E2003 SP1 in the hope it might fix things but to no avail

Any advice would be much appreciated as I'm finding almost no references to
this particular combination of errors...

I'm wondering whether I should just delete the ADC connections, then try to
uninstall E2003 and re-run forest and domain preps, then re-install it.

If I do, will it do anything freaky to the 5.5 server or it's DS?

Thanks in advance

Phil Ermiya

	Exchange Server Forum Index -> Setup	All times are GMT
Page 1 of 1