DCpromo RPC error

Mathieu CHATEAU

on the KB:
CAUSE
This issue may occur when destination domain controllers...

So it would be on the destination DC (existing one)

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"CRG" <CRG@discussions.microsoft.com> wrote in message
news:07539536-D8A1-4A07-A351-8B68E7134C88@microsoft.com...
> TYVM for the quick response.
> We suspect that this may be a bandwidth issue.
>
> There is no NTDS key on the remote server in question. Should I add it or
> am
> I supposed to change it on the existing domain controller to which it
> connects?
>
> "Mathieu CHATEAU" wrote:
>
>> Active Directory changes do not replicate in Windows Server 2003
>> http://support.microsoft.com/kb/830746/en-us
>>
>>
>> To resolve this issue, increase the bandwidth of your network connection
>> so
>> that the Active Directory changes replicate in the five minute timeout
>> period. If you cannot increase the bandwidth of your network connection,
>> edit the registry on your Windows Server 2003-based computer to increase
>> the
>> value of the RPC timeout for Active Directory replication. To increase
>> the
>> RPC timeout value, follow these steps:
>> 1. Start Registry Editor.
>> 2. Locate the following registry subkey:
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NTDS\Parameters
>> 3. Right-click Parameters, point to New, and then click DWORD Value.
>> 4. Type RPC Replication Timeout (mins), and then press ENTER to name the
>> new
>> value.
>> 5. Right-click RPC Replication Timeout (mins), and then click Modify.
>> 6. In the Value data box, type the number of minutes that you want to use
>> for the RPC timeout for Active Directory replication, and then click OK.
>> On
>> a Windows Server 2003-based computer that is part of a Windows 2000
>> environment or that was upgraded from Windows 2000 Server, you may want
>> to
>> set this value to 45 minutes.
>> Note You must restart the computer to activate any changes that are made
>> to
>> RPC Replication Timeout (mins).
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "CRG" <CRG@discussions.microsoft.com> wrote in message
>> news:04766C0B-61D0-44E9-9F7D-1CEF6F3F50EB@microsoft.com...
>> > DNS is correct
>> > No firewall
>> > time is synched.
>> >
>> > "Mathieu CHATEAU" wrote:
>> >
>> >> Hello,
>> >>
>> >> dns pointing to DC ?
>> >> Any firewall between this future dc and the one it try to replicate
>> >> from
>> >> ?
>> >> Any clock issue ?
>> >>
>> >> --
>> >> Cordialement,
>> >> Mathieu CHATEAU
>> >> http://lordoftheping.blogspot.com
>> >>
>> >>
>> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
>> >> news:CAED0D9F-D3C4-409E-A392-ADDA7792FE27@microsoft.com...
>> >> > Trying to run DCpromo on a server at a remote location using remote
>> >> > desktop.
>> >> >
>> >> > In DCpromo during the replication phase the app gets hung on
>> >> > replicating
>> >> > an
>> >> > object and after a few minutes fails with
>> >> >
>> >> > "active directory could not replicate the directory partition
>> >> > CN=Configuration, DC=company,DC=com from the remote domain
>> >> > controller
>> >> > dc1.company.com.
>> >> > The remote procedure call was cancelled"
>> >> >
>> >> > No events on DCs give any clue. It hangs on the same object each
>> >> > time
>> >> > (in
>> >> > my
>> >> > case 3109 out of 4766).
>> >> >
>> >> > I have done this on 10 other remote servers in our environment
>> >> > without
>> >> > fail.
>> >> > I have used VNC as well as RDP with same results. I have removed the
>> >> > server
>> >> > from domain, deleted account, readded with same result.
>> >> > The failing server does appear in Sites and Services after it fails.
>> >> >
>> >> > Any ideas? TYIA
>> >> > CRG
>> >>
>> >>
>>

CRG

LordofPing
Fired too soon on that last post. It was TDQ (The Dumb Question)

Anyway I made the NTDS replication time 30 minutes on the "homecourt" DCs,
rebooted them and DCPromo went exactly the same as before. "remote procedure
call was cancelled" after a few minutes

"Mathieu CHATEAU" wrote:

> on the KB:
> CAUSE
> This issue may occur when destination domain controllers...
>
> So it would be on the destination DC (existing one)
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "CRG" <CRG@discussions.microsoft.com> wrote in message
> news:07539536-D8A1-4A07-A351-8B68E7134C88@microsoft.com...
> > TYVM for the quick response.
> > We suspect that this may be a bandwidth issue.
> >
> > There is no NTDS key on the remote server in question. Should I add it or
> > am
> > I supposed to change it on the existing domain controller to which it
> > connects?
> >
> > "Mathieu CHATEAU" wrote:
> >
> >> Active Directory changes do not replicate in Windows Server 2003
> >> http://support.microsoft.com/kb/830746/en-us
> >>
> >>
> >> To resolve this issue, increase the bandwidth of your network connection
> >> so
> >> that the Active Directory changes replicate in the five minute timeout
> >> period. If you cannot increase the bandwidth of your network connection,
> >> edit the registry on your Windows Server 2003-based computer to increase
> >> the
> >> value of the RPC timeout for Active Directory replication. To increase
> >> the
> >> RPC timeout value, follow these steps:
> >> 1. Start Registry Editor.
> >> 2. Locate the following registry subkey:
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NTDS\Parameters
> >> 3. Right-click Parameters, point to New, and then click DWORD Value.
> >> 4. Type RPC Replication Timeout (mins), and then press ENTER to name the
> >> new
> >> value.
> >> 5. Right-click RPC Replication Timeout (mins), and then click Modify.
> >> 6. In the Value data box, type the number of minutes that you want to use
> >> for the RPC timeout for Active Directory replication, and then click OK.
> >> On
> >> a Windows Server 2003-based computer that is part of a Windows 2000
> >> environment or that was upgraded from Windows 2000 Server, you may want
> >> to
> >> set this value to 45 minutes.
> >> Note You must restart the computer to activate any changes that are made
> >> to
> >> RPC Replication Timeout (mins).
> >>
> >> --
> >> Cordialement,
> >> Mathieu CHATEAU
> >> http://lordoftheping.blogspot.com
> >>
> >>
> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
> >> news:04766C0B-61D0-44E9-9F7D-1CEF6F3F50EB@microsoft.com...
> >> > DNS is correct
> >> > No firewall
> >> > time is synched.
> >> >
> >> > "Mathieu CHATEAU" wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> dns pointing to DC ?
> >> >> Any firewall between this future dc and the one it try to replicate
> >> >> from
> >> >> ?
> >> >> Any clock issue ?
> >> >>
> >> >> --
> >> >> Cordialement,
> >> >> Mathieu CHATEAU
> >> >> http://lordoftheping.blogspot.com
> >> >>
> >> >>
> >> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
> >> >> news:CAED0D9F-D3C4-409E-A392-ADDA7792FE27@microsoft.com...
> >> >> > Trying to run DCpromo on a server at a remote location using remote
> >> >> > desktop.
> >> >> >
> >> >> > In DCpromo during the replication phase the app gets hung on
> >> >> > replicating
> >> >> > an
> >> >> > object and after a few minutes fails with
> >> >> >
> >> >> > "active directory could not replicate the directory partition
> >> >> > CN=Configuration, DC=company,DC=com from the remote domain
> >> >> > controller
> >> >> > dc1.company.com.
> >> >> > The remote procedure call was cancelled"
> >> >> >
> >> >> > No events on DCs give any clue. It hangs on the same object each
> >> >> > time
> >> >> > (in
> >> >> > my
> >> >> > case 3109 out of 4766).
> >> >> >
> >> >> > I have done this on 10 other remote servers in our environment
> >> >> > without
> >> >> > fail.
> >> >> > I have used VNC as well as RDP with same results. I have removed the
> >> >> > server
> >> >> > from domain, deleted account, readded with same result.
> >> >> > The failing server does appear in Sites and Services after it fails.
> >> >> >
> >> >> > Any ideas? TYIA
> >> >> > CRG
> >> >>
> >> >>
> >>
>

CRG

LordofPing
Fired too soon on that last post. It was TDQ (The Dumb Question)

Anyway I made the NTDS replication time 30 minutes on the "homecourt" DCs,
rebooted them and DCPromo went exactly the same as before. "remote procedure
call was cancelled" after a few minutes

"Mathieu CHATEAU" wrote:

> on the KB:
> CAUSE
> This issue may occur when destination domain controllers...
>
> So it would be on the destination DC (existing one)
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "CRG" <CRG@discussions.microsoft.com> wrote in message
> news:07539536-D8A1-4A07-A351-8B68E7134C88@microsoft.com...
> > TYVM for the quick response.
> > We suspect that this may be a bandwidth issue.
> >
> > There is no NTDS key on the remote server in question. Should I add it or
> > am
> > I supposed to change it on the existing domain controller to which it
> > connects?
> >
> > "Mathieu CHATEAU" wrote:
> >
> >> Active Directory changes do not replicate in Windows Server 2003
> >> http://support.microsoft.com/kb/830746/en-us
> >>
> >>
> >> To resolve this issue, increase the bandwidth of your network connection
> >> so
> >> that the Active Directory changes replicate in the five minute timeout
> >> period. If you cannot increase the bandwidth of your network connection,
> >> edit the registry on your Windows Server 2003-based computer to increase
> >> the
> >> value of the RPC timeout for Active Directory replication. To increase
> >> the
> >> RPC timeout value, follow these steps:
> >> 1. Start Registry Editor.
> >> 2. Locate the following registry subkey:
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NTDS\Parameters
> >> 3. Right-click Parameters, point to New, and then click DWORD Value.
> >> 4. Type RPC Replication Timeout (mins), and then press ENTER to name the
> >> new
> >> value.
> >> 5. Right-click RPC Replication Timeout (mins), and then click Modify.
> >> 6. In the Value data box, type the number of minutes that you want to use
> >> for the RPC timeout for Active Directory replication, and then click OK.
> >> On
> >> a Windows Server 2003-based computer that is part of a Windows 2000
> >> environment or that was upgraded from Windows 2000 Server, you may want
> >> to
> >> set this value to 45 minutes.
> >> Note You must restart the computer to activate any changes that are made
> >> to
> >> RPC Replication Timeout (mins).
> >>
> >> --
> >> Cordialement,
> >> Mathieu CHATEAU
> >> http://lordoftheping.blogspot.com
> >>
> >>
> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
> >> news:04766C0B-61D0-44E9-9F7D-1CEF6F3F50EB@microsoft.com...
> >> > DNS is correct
> >> > No firewall
> >> > time is synched.
> >> >
> >> > "Mathieu CHATEAU" wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> dns pointing to DC ?
> >> >> Any firewall between this future dc and the one it try to replicate
> >> >> from
> >> >> ?
> >> >> Any clock issue ?
> >> >>
> >> >> --
> >> >> Cordialement,
> >> >> Mathieu CHATEAU
> >> >> http://lordoftheping.blogspot.com
> >> >>
> >> >>
> >> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
> >> >> news:CAED0D9F-D3C4-409E-A392-ADDA7792FE27@microsoft.com...
> >> >> > Trying to run DCpromo on a server at a remote location using remote
> >> >> > desktop.
> >> >> >
> >> >> > In DCpromo during the replication phase the app gets hung on
> >> >> > replicating
> >> >> > an
> >> >> > object and after a few minutes fails with
> >> >> >
> >> >> > "active directory could not replicate the directory partition
> >> >> > CN=Configuration, DC=company,DC=com from the remote domain
> >> >> > controller
> >> >> > dc1.company.com.
> >> >> > The remote procedure call was cancelled"
> >> >> >
> >> >> > No events on DCs give any clue. It hangs on the same object each
> >> >> > time
> >> >> > (in
> >> >> > my
> >> >> > case 3109 out of 4766).
> >> >> >
> >> >> > I have done this on 10 other remote servers in our environment
> >> >> > without
> >> >> > fail.
> >> >> > I have used VNC as well as RDP with same results. I have removed the
> >> >> > server
> >> >> > from domain, deleted account, readded with same result.
> >> >> > The failing server does appear in Sites and Services after it fails.
> >> >> >
> >> >> > Any ideas? TYIA
> >> >> > CRG
> >> >>
> >> >>
> >>
>

Mathieu CHATEAU

nevermind!

Was it just after 5 minutes ? Did the dc you are promoting use a different
one this time ?
Do you have any bandwith monitoring ?

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"CRG" <CRG@discussions.microsoft.com> wrote in message
news:053781A7-E467-4890-8173-8635ACABD231@microsoft.com...
> LordofPing
> Fired too soon on that last post. It was TDQ (The Dumb Question)
>
> Anyway I made the NTDS replication time 30 minutes on the "homecourt" DCs,
> rebooted them and DCPromo went exactly the same as before. "remote
> procedure
> call was cancelled" after a few minutes
>
> "Mathieu CHATEAU" wrote:
>
>> on the KB:
>> CAUSE
>> This issue may occur when destination domain controllers...
>>
>> So it would be on the destination DC (existing one)
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "CRG" <CRG@discussions.microsoft.com> wrote in message
>> news:07539536-D8A1-4A07-A351-8B68E7134C88@microsoft.com...
>> > TYVM for the quick response.
>> > We suspect that this may be a bandwidth issue.
>> >
>> > There is no NTDS key on the remote server in question. Should I add it
>> > or
>> > am
>> > I supposed to change it on the existing domain controller to which it
>> > connects?
>> >
>> > "Mathieu CHATEAU" wrote:
>> >
>> >> Active Directory changes do not replicate in Windows Server 2003
>> >> http://support.microsoft.com/kb/830746/en-us
>> >>
>> >>
>> >> To resolve this issue, increase the bandwidth of your network
>> >> connection
>> >> so
>> >> that the Active Directory changes replicate in the five minute timeout
>> >> period. If you cannot increase the bandwidth of your network
>> >> connection,
>> >> edit the registry on your Windows Server 2003-based computer to
>> >> increase
>> >> the
>> >> value of the RPC timeout for Active Directory replication. To increase
>> >> the
>> >> RPC timeout value, follow these steps:
>> >> 1. Start Registry Editor.
>> >> 2. Locate the following registry subkey:
>> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NTDS\Parameters
>> >> 3. Right-click Parameters, point to New, and then click DWORD Value.
>> >> 4. Type RPC Replication Timeout (mins), and then press ENTER to name
>> >> the
>> >> new
>> >> value.
>> >> 5. Right-click RPC Replication Timeout (mins), and then click Modify.
>> >> 6. In the Value data box, type the number of minutes that you want to
>> >> use
>> >> for the RPC timeout for Active Directory replication, and then click
>> >> OK.
>> >> On
>> >> a Windows Server 2003-based computer that is part of a Windows 2000
>> >> environment or that was upgraded from Windows 2000 Server, you may
>> >> want
>> >> to
>> >> set this value to 45 minutes.
>> >> Note You must restart the computer to activate any changes that are
>> >> made
>> >> to
>> >> RPC Replication Timeout (mins).
>> >>
>> >> --
>> >> Cordialement,
>> >> Mathieu CHATEAU
>> >> http://lordoftheping.blogspot.com
>> >>
>> >>
>> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
>> >> news:04766C0B-61D0-44E9-9F7D-1CEF6F3F50EB@microsoft.com...
>> >> > DNS is correct
>> >> > No firewall
>> >> > time is synched.
>> >> >
>> >> > "Mathieu CHATEAU" wrote:
>> >> >
>> >> >> Hello,
>> >> >>
>> >> >> dns pointing to DC ?
>> >> >> Any firewall between this future dc and the one it try to replicate
>> >> >> from
>> >> >> ?
>> >> >> Any clock issue ?
>> >> >>
>> >> >> --
>> >> >> Cordialement,
>> >> >> Mathieu CHATEAU
>> >> >> http://lordoftheping.blogspot.com
>> >> >>
>> >> >>
>> >> >> "CRG" <CRG@discussions.microsoft.com> wrote in message
>> >> >> news:CAED0D9F-D3C4-409E-A392-ADDA7792FE27@microsoft.com...
>> >> >> > Trying to run DCpromo on a server at a remote location using
>> >> >> > remote
>> >> >> > desktop.
>> >> >> >
>> >> >> > In DCpromo during the replication phase the app gets hung on
>> >> >> > replicating
>> >> >> > an
>> >> >> > object and after a few minutes fails with
>> >> >> >
>> >> >> > "active directory could not replicate the directory partition
>> >> >> > CN=Configuration, DC=company,DC=com from the remote domain
>> >> >> > controller
>> >> >> > dc1.company.com.
>> >> >> > The remote procedure call was cancelled"
>> >> >> >
>> >> >> > No events on DCs give any clue. It hangs on the same object each
>> >> >> > time
>> >> >> > (in
>> >> >> > my
>> >> >> > case 3109 out of 4766).
>> >> >> >
>> >> >> > I have done this on 10 other remote servers in our environment
>> >> >> > without
>> >> >> > fail.
>> >> >> > I have used VNC as well as RDP with same results. I have removed
>> >> >> > the
>> >> >> > server
>> >> >> > from domain, deleted account, readded with same result.
>> >> >> > The failing server does appear in Sites and Services after it
>> >> >> > fails.
>> >> >> >
>> >> >> > Any ideas? TYIA
>> >> >> > CRG
>> >> >>
>> >> >>
>> >>
>>