Unable to Raise Domain Functional Level

Hello All,

Any help provided would be greatly appreciated. All servers in my
environment are Windows 2003 server throughout the forest. One child domain
has previously had it's functional level raised without any problems. When
trying to raising another child domain from Windows 2000 Native to Windows
Server 2003 domain functional level, I get the following error:

The functional level could not be raised. The error is: The server is
unwilling to process the request.



Now when I run dcdiag, I receive the following (I've limited the text below
to the errors :

Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of latency in
replication. So follow up to resolve the following problems, only if the
same problem is reported on all DCs for a given domain or if the problem
persists after replication has had reasonable time to replicate changes.

[1] Problem: Missing Expected Value
Base Object: CN=LostAndFoundConfig,CN=Configuration,DC=bethco,DC=local
Base Object Description: "Server Object"
Value Object Attribute: serverReference
Value Object Description: "DC Account Object"

Recommended Action: This could hamper authentication (and thus replication,
etc). Check if this server is deleted, and if so clean up this DCs Account
Object. If the problem persists and this is not a deleted DC, authoratively
restore the DSA object from a good copy, for example the DSA on the DSA's
home server.

CNR-PR-DOMA00 failed test VerifyEnterpriseReferences


Additionally, when I run DNSLint, I receive the following:

Notes:
One or more DNS servers is not authoritative for the domain
Zone serial numbers were not identical on every DNS server
One or more zone files may have expired
SOA record data was unavailable and/or missing on one or more DNS servers

At least one CNAME record for an AD forest GUID was missing from a DNS server



This is listed for some of the DC's in the child domain that I want to have
the functional level raised. Not sure if this is an issue. As I understand,
DNSLint is only capable of verifiying records for a root domain, not the
records for DC's located in a child. If I am incorrect, by all means please
correct me.

SOA record data from server:
Authoritative name server: Unknown
Hostmaster: Unknown
Zone serial number: Unknown
Zone expires in: Unknown
Refresh period: Unknown
Retry delay: Unknown
Default (minimum) TTL: Unknown


No Domain Controllers have failed or have been removed from our domain.
NTDSUtil doesn't reveal any old DC's lurking about in the metadata. I've
been googling the above error phrases without much luck.

Any help provided would be greatly appreciated.
.

Relevant Pages

  • Re: Question about moving to Windows Server 2003 Domain Functional Level
    ... reinstalling NT to make it a member server was not an option. ... I Raised the Domain Functional Level to Windows Server ... 2003 Interim if the move to full 2003 Server level should break ...
    (microsoft.public.windows.server.active_directory)
  • Re: Server 2003 in Mixed Mode - Moving to Native
    ... Forrest Functional Level as well. ... earlier or Windows 2000, then do not raise the domain functional level to ... We have many Server 2000 Member Servers ... All we want to do is to move to Native Mode to take advantage of Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: Blank Forest Functional Level - Unable to fix
    ... Use NTDSUTIL on the new PDC ... Connect to the current server ... The domain functional level was Windows Server 2003. ... Server 2003 however the forest functional level is blank. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Question about moving to Windows Server 2003 Domain Functional Level
    ... 2003 Interim if the move to full 2003 Server level should break ... The PDC Emulator is still there and does all the things it does in the other ... certainly have non-Kerberos aware clients in a Server 2003 Domain Functional ... Native 2000 Domain Functional Level requirement. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Question about moving to Windows Server 2003 Domain Functional Level
    ... and 2003 Interim mode. ... Native 2000 Domain Functional Level requirement. ... I'd reinstall it as a member server. ... server can run on a domain in 2003 Interim mode. ...
    (microsoft.public.windows.server.active_directory)
Loading