"AndyLandenSr" <AndyLandenSr.3x8pva@newsgroup> wrote in message
> I had a catastrophic failure of a PDC emulator
> (server01.landenhousecomputing.com). I was able to move the FSMO roles
> to another DC (seize) (exchange.landenhousecomputing.com). I removed
> references to server01 from AD Sites Services. I repointed (AD
> Integrated) DNS to exchange.landenhousecomputing.com. Rebooted multiple
> times. Since the crash, though,
> * No one can connect to Exchange email
> * I can't join a machine to the domain
> * I can't DCPromo server01's replacement
> * If I try to add a reverse lookup zone (AD integrated) for a different
> subnet, I get the following error:
> The zone cannot be created. There was a server failure.
> I receive a variety of event log errors (please see the attached).
> Also attached are results of DCDIAG.txt, NETDIAG.txt, and a copy of the
> netlogon.dns (NetLogonDotDNS.txt)
> Most of the online help suggests I had tried to do a domain rename. I
> haven't. Ever.
> The exchange server itself is fully functional - it sends and receives
> (Exch 2003 SP2), and I can connect locally or remotely using webmail.
> ANY ideas on where to go would help.
Did you run a Metadata Cleanup to remove the references from the dead DC?
How to remove data in Active Directory after an unsuccessful ...Type
metadata cleanup, and then press ENTER. Based on the options given, .... To
use the new syntax for metadata cleanup, follow these steps: Run ntdsutil.
Are any machines still using the old DC as a DNS server? Check your DHCP
Option 006. If using WINS and WINS was installed on the old DC, change that,
too in Option 046.
Is the current DC a GC? If not, and if you have only one domain, all DCs are
recommended to be GCs. This could be part of the problem. This is important
for Exchange as well, especially if it is installed on a DC, besides
offering logon and other AD functions.
Once you make all the changes, restart the DCs.
Make sure none of your machines are using your ISP's or some other external
DNS or the router, as a DNS address in their IP properties.
If the AD DNS domain name is a single label name, there will be additional
problems associated with this type of name.
Regarding Exchange being on a DC, needless to say, (not sure if you knew
this), it's not advised, recommended nor best practice to install Exchange
on a DC. A DC degrades drive performance by disabling the write-cache
function on the controller. It cannot be enabled while it's a DC. This
degrades Exchange performance, as well as can cause possible problems with
the way Exchange ESE process works with transactional logging, as well as
that if Exchange is on a DC, it will only use (locks itself) to that DC for
its GC and DC DSAccess functions (such as for GAL lookups, groups expansion,
etc). So if the DC function goes down, it will never look elsewhere.
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.