2003 to 2008 Forestprep failure

[egadmin]

I am trying to prepare my forest and domain to 2008. When I run adprep
/forestprep I get the following error:

ADPREP WARNING:

Before running adprep, all Windows 2000 Active Directory Domain Controllers
in t
he forest should be upgraded to Windows 2000 Service Pack 4 (SP4) or later.

[User Action]
If ALL your existing Windows 2000 Active Directory Domain Controllers meet
this
requirement, type C and then press ENTER to continue. Otherwise, type any
other
key and press ENTER to quit.


c
.................................................................................
.................................................................................
.................................................................................
.............
Adprep was unable to complete because the call back function failed.
[Status/Consequence]
Error message: C:\WINDOWS\debug\adprep\logs\20080305101638\LDIF.log The
process
cannot access the file because it is being used by another process.
(0x80070020).
[User Action]
Check the log file ADPrep.log, in the
C:\WINDOWS\debug\adprep\logs\2008030510163
8 directory for more information.


Adprep was unable to update forest information.
[Status/Consequence]
Adprep requires access to existing forest-wide information from the schema
maste
r in order to complete this operation.
[User Action]
Check the log file, ADPrep.log, in the
C:\WINDOWS\debug\adprep\logs\200803051016
38 directory for more information.

I can't seem to find anything related to this on the Internet. The following
is the last few lines of the ADPrep.log:



Updating change from:" International ISDN Number (Others)" to "International
ISDN Number (Others)" for locale 409, object inetOrgPerson-Display and
property attributeDisplayNames.

Adprep was unable to complete because the call back function failed.

[Status/Consequence]

Error message: C:\WINDOWS\debug\adprep\logs\20080305101638\LDIF.log The
process cannot access the file because it is being used by another process.

(0x80070020).

[User Action]

Check the log file ADPrep.log, in the
C:\WINDOWS\debug\adprep\logs\20080305101638 directory for more information.



Adprep was unable to update forest information.

[Status/Consequence]

Adprep requires access to existing forest-wide information from the schema
master in order to complete this operation.

[User Action]

Check the log file, ADPrep.log, in the
C:\WINDOWS\debug\adprep\logs\20080305101638 directory for more information.

I am logged in as Enterprise and Schema Admin when this happens. I also
cannot find anything else that is using or trying to access the LDIF.log. I
am kind of stuck at this point. Thanks in advance for your help.

[Jian-Ping Zhu [MSFT]]

After some research, I find out that if LDIF.log is used by other process,
Forestprep may fail. So, please check first whether the LDIF.log is really
used by some other process. You could use the Process Explorer tool to
check what process is handling the log file.

After installing the tool, please click Find -> Find Handle or DLL and then
please enter the whole path of the log file
(C:\WINDOWS\debug\adprep\logs\20080305101638\LDIF.log) and click the Search
button. After that, please stop the process which is handling the log file
and try forest prepare again.

The following article provides an introduction of Process Explorer.
http://technet.microsoft.com/zh-cn/s...53(en-us).aspx

You can download Process Explorer from this link:
http://download.sysinternals.com/Fil...ssExplorer.zip

[Jian-Ping Zhu [MSFT]]

I understand that when you use Process Explorer tool to check the file
there is no processes that have an open handle on it. It is possible that
the file handle has been released when you use the Process Explorer to
check. It is reported that some third party applications, especially
Antiivrus software, may cause this issue. To troubleshoot this problem
efficiently, please temporarily disable or uninstall your Anti-virus
software and any other hard disk scan tool to test this issue again. To
isolate the influence of additional applications, please boot the system
into a Clean Boot environment and then run the Forestprep command again:

1. Click Start->Run...->type msconfig and press Enter
2. Click Services tab and select Hide All Microsoft Services and Disable
All third party Services.
3. Click Startup tab and Disable All startup items
4. Click OK and choose Restart
5. After reboot, check whether the problem still occurs

If the issue still exists, please try to rename or delete the LDIF.log file
and check whether this is possible.

I look forward to hearing from you. : )\

[egadmin]

Well your suggestion worked. It appears it was McAfee 8.5i that was the hold
up. I had to uninstall as I am running McAfee ePO sever and it will not
allow turning off services. Once I uninstalled and rebooted the entire
forestprep, domainprep, gpprep, and rodcprep took less than 5 minutes to
complete without errors. Thanks a lot for your help.

[Jian-Ping Zhu [MSFT]]

I am glad to hear that this problem has been resolved successfully. It is
my pleasure to work with you on this issue.

If you need further assistance, please feel free to let me know.

Thanks for using newsgroup and hope you have a nice day!

[jmutua]

hi,
i am migrating from windows 2003 domain to windows 2008 domain. I need to extend the schema on the current domain and when i run adprep >adprep/forestprep, command i get the following error

"attributeSyntax" attribute value for objects defined in Windows 2000 schema and
extended schema do not match.


A previous schema extension has defined the attribute value as "2.5.5.5" for obj
ect "CN=preferredLanguage,CN=Schema,CN=Configuration,DC=xxx,DC=co,DC=ke" diff
erently than the schema extension needed for Windows Server 2008.
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the schema to res
olve the inconsistency. Then run adprep again.

anyone with a solution for this?

[Jian-Ping Zhu [MSFT]]

Please understand that in order to avoid possible confusion and make the
troubleshooting clear, we generally only focus on one issue per thread.
Therefore, if the information mentioned before could not help, please
kindly create a new post in this newsgroup queue.

Thanks again for your understanding.

[GregoryH]

I just wanted to say that McAfee 8.5 was the source of an ADPREP failure for me as well. All I had to do was stop all the services for McAfee (I don't have ePO) and it worked fine. Good work on finding the source of this issue guys.

[liuji_dragon]

Howdy!

I'm having the close to the same problem with a Windows SBS 2003 server. The exact error message I'm running into when attempting an adprep /forestprep is:

********************

Updating change from:" International ISDN Number (Others)" to "International ISDN Number (Others)" for locale 409, object inetOrgPerson-Display and property attributeDisplayNames.

Adprep was unable to complete because the call back function failed.

[Status/Consequence]

Error message: Cannot change thread mode after it is set.

(0x80010106).

[User Action]

Check the log file ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\20091117155746 directory for more information.



Adprep set the value of registry key System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to 0



Adprep was unable to update forest information.

[Status/Consequence]

Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.

[User Action]

Check the log file, ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\20091117155746 directory for more information.

********************

This comes from the adprep.log. I've uninstalled Symantec Antivirus and all related components from the server. I've used Process Explorer to look for any processes that have a lock on LDIF.log (using the full path) and didn't find any processes that have a lock on it. I was able to change the name of the file without any problem, so it doesn't look like anything is using it.

I have a number of directories under the C:\WINDOWS\debug\adprep\logs\ area for each day I've tried running adprep /forestprep.

I've checked the startup processes using msconfig and disabled a few things I didn't see as necessary and rebooted - still a no go.

dcdiag and netdiag come back with perfect results. I'm running as a membe of the schema admin group and checked that this server holds all the FSMO roles in the domain. This is the only domain controller and I'd like to get rid of it after I transfer everything to a new server running Windows Server 2008. Any ideas? This is driving me crazy.

[liuji_dragon]

Actually, after looking at it, I think I'll start a new thread since the [Status/Consequence] field is different than the issue in this thread. Sorry!

If anyone has any suggestions, I'd be happy to hear them though. :)

[thiagobeier]

Hi guys I got the same errors and I tried everything i read here and then I stopped the antivirus and I got it.
Regards,