Skip navigation

Q. You receive 'Error when upgrading NIS Schema' when you attempt to upgrade Windows Services for UNIX 3.0 to Windows Services for UNIX 3.5?

When attempting to upgrade from Windows Services for UNIX 3.0 to Windows Services for UNIX 3.5 on Windows Server 2003, you receive an error like:

Error when upgrading NIS Schema. Please look at the log file at:

C:\Documents and Settings\Administrator\Local Settings\Temp\sfusch.log for more details on the error.

NOTE: The installation rolls back to version 3.0.

The sfusch.log file contains entries like:

SFUSCH.log
Start of schema extension. Time: Mon Aug 28 07:38:35 2006
Schema Naming Context
'CN=Schema,CN=Configuration,DC=example1,DC=com' 
FSMO Role Owner
'CN=Adatum,CN=Servers,CN=Example2,CN=Sites,CN=Configuration,DC=example1,DC=com' 
DNS Hostname of FSMO
'Adatum.example1.com'
Redirecting schema changes to 'CN=Adatum,CN=Servers,CN=Example2,CN=Sites,CN=Configuration,DC=example1,DC=com'
Default Naming Context
'DC=example1,DC=com'
Domain name = 'example1'
Done with getting information from Active Directory
Checking SFU schema version
Checking SFU V30 schema on server - Adatum
Verifying all extended schema attributes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended auxilliary schema classes. AD Server = 'Adatum'.
Checking existing SFU configuration version
Checking SFU V30 schema on server - Adatum
Verifying all extended schema attributes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended schema classes. AD Server = 'Adatum'.
Verifying all extended auxilliary schema classes. AD Server = 'Adatum'.
Marking DC as NIS server
SFU Schema Extension did not complete.
End of schema extension. Time: Mon Aug 28 07:38:39 2006
This behavior will occur if there are Active Directory objects that use the same CN ( Common Name) as the domain controller object under OU=Domain Controllers.

To resolve this problem:

1. Install thew Windows Server 2003 Support Tools by double-clicking the Suptools.msi file in the Support\Tools folder on the Windows Server 2003 CD-ROM.

2. Start / Run / adsiedit.msc / OK.

3. Expand Domain \[Adatum\].

4. Expand DC=example DC=com.

5. Locate and rename all objects that use the same CN as the domain controller object, but DO NOT rename the domain controller object.


Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish