Exchange 2003 Migration Disaster NEED HELP 1

[AndyNZ]

I have 1 Exchange 2000 server running Exchange SP3 on a Windows 2000 Server running Windows SP3.
I have built a new Windows 2003 server with SP1 and installed Exchange 2003 and Exchange 2003 SP1.
Thinking that this would be a simple join the organization and move mailbox method of migrating.

However.
The MSExchangeSA service hangs on startup I get the following errors in the Exchange 2003 servers event log.

Event ID: 9095
MSExchangeSA
The MAD Monitoring thread is initializing.

Event 9096
MSExchangeSA
The MAD Monitoring thread is initialized.

Event ID: 2114
MSExchangeDSAccess
Process WMIPRVSE.EXE -EMBEDDING (PID=1192). Topology Discovery failed, error 0x80040a02.

Event ID: 2114
MSExchangeDSAccess
Process MAD.EXE (PID=3196). Topology Discovery failed, error 0x80040a02.

Event ID: 1042
MSExchangeMU
Metabase Update failed to read the Configuration namespace property from the domain controller. Error code is 80040a01.

Event ID: 9098
MSExchangeSA
The MAD Monitoring thread was unable to read its configuration from the DS, error '0x80040a01'.

Event ID: 2114
MSExchangeDSAccess
Process MAD.EXE (PID=3196). Topology Discovery failed, error 0x80040a02.

Event ID: 8213
MSExchangeFBPublish
System Attendant Service failed to create session for virtual machine PGGEXCH01. The error number is 0xc10306ce.

Event ID: 2114
MSExchangeDSAccess
Process MAD.EXE (PID=3196). Topology Discovery failed, error 0x80040a02.


Event ID: 1042
MSExchangeMU
Metabase Update failed to read the Configuration namespace property from the domain controller. Error code is 80040a01.

Event ID: 2114
MSExchangeDSAccess
Process MAD.EXE (PID=3196). Topology Discovery failed, error 0x80040a02.

Event ID: 2102
MSExchangeDSAccess
Process MAD.EXE (PID=3196). All Domain Controller Servers in use are not responding:
Server1.mycompany.co.nz
Server2.mycompany.co.nz
Server3.mycompany.co.nz
Server4.mycompany.co.nz

Event ID: 2114
MSExchangeDSAccess
Process MAD.EXE (PID=3196). Topology Discovery failed, error 0x80040a02.

Event ID: 1042
MSExchangeMU
Metabase Update failed to read the Configuration namespace property from the domain controller. Error code is 80040a01.

Event ID: 2114
MSExchangeDSAccess
Process MAD.EXE (PID=3196). Topology Discovery failed, error 0x80040a02.

--------------------------------

These then constantly loop and the server will not reach the Windows Login screen.

Now... I have 4 domain controllers.

All running Windows 2000 SP3
3 DC's onsite configured as follows:
2 GC's
1 FSMO Role holder NOT a GC onsite

1 DC / GC offsite


All AD Controllers have been working perfectly for years.
No slow logons or strange errors in the event logs.

I NEED HELP!

The errors all seem to relate to Active Directory.
Is there a problem with the Schema?
The ForestPrep and DomainPrep both completed successfully during the Exchange 2003 setup.
Is it because im running a Windows 2003 server with SP1 in a Windows 2000 AD environment?
All the whitepapers tell me this is a supported configuration.

I've trolled through forums / MS Knowledge Base / Technet.
All to no avail.

Can someone PLEASE help!

 

[mstarrett]

Turn the firewall off on server 2003 sp1..

Mike

 

[AndyNZ]

I thought I checked that before I started the install...
Control Panel - Windows Firewall is not ticked..
But admittedly I left it at that and did not look any deeper.
Is Windows Firewall Enabled by default after you install W2k3 SP1 or do you have to turn it on manually?

I've left the server for the night so I can have a think.
I'll check the firewall first thing in the morning.

Thanks

 

[mstarrett]

No it does not automagically turn on but will ask you to turn on ICS service once you touch it. This is nice feature not to turn on firewall since I remote to 90% of my systems.
Is the MAD errors due to Mobile Device service on maybe.

Mike

 

[AndyNZ]

OK its not the Windows Firewall because it was never turned on.
If I run DCDiag from the Exchange 2003 server against all my DC's they all pass.
The account I installed Exchange 2003 under is a Schema Admin - Domain Admin - Enterprise Admin - Everything under the sun admin.
I've used Replmon to Check AD replication and it says all my Ad controllers are up to date.

Someone give me some more ideas!

 

[wdoellefeld]

Found something on a different forum that may help. This could be caused by a change in the Default Domain Controller Policy GPO. Make sure that the Exchange Enterprise Servers domain local group has the Manage Auditing and Security Log right (SeSecurityPrivilege). It's put there by domainprep, but may be removed if someone reapplies the default policy.

Reference:

http://support.microsoft.com/?id=314294

http://support.microsoft.com/?id=328646

FRCP

http://www.frcp.net

 

[marcn29]

See if this is related to your issue:

http://support.microsoft.com/?id=898060

 

[AndyNZ]

Weird my Default Domain Controller Policy seems unchanged...
I did notice Domain Prep ran very quickly during the install. It finished in about 2 seconds.
I assumed it worked fine as the install wizard checked it as successful, however given the Policy has not been updated it must have failed.
Im off back to work to re-run domain prep.
WISH ME LUCK!
I'll keep you all posted.

 

[AndyNZ]

wdoellefeld's post was right on the money!

""
My group policy wdoellefeld (TechnicalUser) 29 Apr 05 10:25
Found something on a different forum that may help. This could be caused by a change in the Default Domain Controller Policy GPO. Make sure that the Exchange Enterprise Servers domain local group has the Manage Auditing and Security Log right (SeSecurityPrivilege). It's put there by domainprep, but may be removed if someone reapplies the default policy.

Reference:

http://support.microsoft.com/?id=314294

http://support.microsoft.com/?id=328646

Added Exchange Enterprise Servers into the right GPO and everything came up roses!!!!

DomainPrep must not have run successfully, even though during the setup it had it as passed??!!

Ran domainprep again, this time from the command line and watched it closely. Ran through fine, but took longer this time so it must have worked.

Thanks for all your suggestions and help!

Go Tek-Tips!