Re: Active Direcorty install hangs at Examining existing Enterprise Directory

From: Diana Smith [MSFT] (diasmith_at_online.microsoft.com)
Date: 04/07/04 

Date: Wed, 7 Apr 2004 15:00:17 -0400

Hello Mike,

You can test to see if you have a black hole router issue, test for
blackhole router with Ping <computer name or IP address> -f -l 1472
159211 Diagnoses and Treatment of Black Hole Routers
http://support.microsoft.com/?id=159211
314825 How to Troubleshoot Black Hole Router Issues
http://support.microsoft.com/?id=314825
120642 TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows
NT
http://support.microsoft.com/?id=120642

Thank You.

Diana.
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike A." <mike@ironsolutions.com> wrote in message
news:10763nr17iv337e@corp.supernews.com...
> We are attempting to install Active Directory on a Windows 2K server with
> Service Pack 4. The server is in a branch office connected via VPN to our
> main office where we have two domain controllers. One controller is Win2K
> Server and the other is Win2003 Server. When runing DCPROMO on the remote
> server it seems to progress through the steps until it gets to Examining
> existing Enterprise Directory Service where it seems to hang. The
following
> error message appears repeatedly in the dcpromoui.log file:
> dcpromoui t:0x20C 06191 Examining existing Enterprise Directory
> Service
> dcpromoui t:0x20C 06192 Enter ProgressDialog::WaitForButton
> dcpromoui t:0x20C 06193 Exit ProgressDialog::WaitForButton
> dcpromoui t:0x20C 06194 Calling DsRoleGetDcOperationProgress
> dcpromoui t:0x20C 06195 Error 0x3E5 (!0 => error, 0x3E5 =
> ERROR_IO_PENDING)
> dcpromoui t:0x20C 06196 OperationStatus : 0x0
>
> Initially we let this go on for almost 12 hours which caused the log file
to
> grow to more than 8MB at which point we cancelled the installation. Is
this
> caused by the WAN connection (T1 at both ends), or is this caused by the
> Win2003 Server AD environment in the main office? Could this be caused by
> an earlier aborted installation of AD on the server? Is this a DNS
problem?
> Any help with this problem would be greatly appreciated.
>
>

Loading