Windows 2003 Forest Update Problem

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

The server is the only DC and it's also running Exchange
2003. When I attempt the forestupdate I get this error:


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

[Status/Consequence]

Adprep verified the state of operation cn=4444c516-f43a-
4c12-9c4b-
b5c064941d61,cn=Operations,cn=ForestUpdates,CN=Configuratio
n,DC=DOMAIN,DC=com.

[Status/Consequence]

The operation has not run or is not currently running. It
will be run next.
Error message: Error(8212) while
running ""C:\WINNT\system32\LDIFde.exe" -i -u -
f "C:\WINNT\system32\debug\adprep\logs\20040104114313
\DisplaySpecifierUpgradeLdifActions.001.ldf" -
j "C:\WINNT\system32\debug\adprep\logs\20040104114313" -s
merlin.dowless.com". See error file: "C:\WINNT\system32
\debug\adprep\logs\20040104114313
\DisplaySpecifierUpgradeLdifError.001.txt." (0x80004005).

[User Action]

Check the log file Adprep.log, in the C:\WINNT\system32
\debug\adprep\logs\20040104114313 directory for more
information.
 
In
Jeff said:
The server is the only DC and it's also running Exchange
2003. When I attempt the forestupdate I get this error:


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

[Status/Consequence]

Adprep verified the state of operation cn=4444c516-f43a-
4c12-9c4b-
b5c064941d61,cn=Operations,cn=ForestUpdates,CN=Configuratio
n,DC=DOMAIN,DC=com.

[Status/Consequence]

The operation has not run or is not currently running. It
will be run next.
Error message: Error(8212) while
running ""C:\WINNT\system32\LDIFde.exe" -i -u -
f "C:\WINNT\system32\debug\adprep\logs\20040104114313
\DisplaySpecifierUpgradeLdifActions.001.ldf" -
j "C:\WINNT\system32\debug\adprep\logs\20040104114313" -s
merlin.dowless.com". See error file: "C:\WINNT\system32
\debug\adprep\logs\20040104114313
\DisplaySpecifierUpgradeLdifError.001.txt." (0x80004005).

[User Action]

Check the log file Adprep.log, in the C:\WINNT\system32
\debug\adprep\logs\20040104114313 directory for more
information.
Click to expand...

Could be DNS config error or just you may not be logged on as the Enterprise
Admin and Schema Admin.

To confirm not a DNS issue, just make sure you're only using the internal
DNS server (in IP properties) and NOT your ISP's or router. That will cause
numerous other errors if you are.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top