Re: adprep /forestprep error message: Cannot change thread mode after it is set

Hello liuji_dragon,

As already stated in the other postings you read before, did you try with
Process Monintor from http://live.sysinternals.com/ to check if the adprep
logfile is blocked?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hey Meinolf!
>
> I has previously glanced at them, but not the verbose logs. I went
> through both dcdiag /v and netdiag /v and found a no major issues.
> Netdom query fsmo also shows the old DC holds all 5 FSMO roles.
> I've attached the output from dcdiag /v and netdiag /v in case you'd
> like to peruse them. Keep in mind I did a search/replace on most of
> the identifying information (i.e. the name of the domain controller
> was replaced with Old_DC, the domain name with Domain, ip addresses,
> etc).
>
> After updates, uninstalls, cleanup work, etc., I'm still getting the
> exact same error in 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: Cannot change thread mode after it is set.
>
> (0x80010106).
>
> [User Action]
>
> Check the log file ADPrep.log, in the
> C:\WINDOWS\debug\adprep\logs\20100116144152 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\20100116144152 directory for more
> information. *************************************************
>
> Any other ideas? Thanks for your help!
>
> +-------------------------------------------------------------------+
> |Filename: dcdiag.txt |
> |Download:
> http://forums.techarena.in/attachmen...hmentid=10586|
> +-------------------------------------------------------------------+
>
> http://forums.techarena.in
>