ungraceful removal of a DC / event id 8026 & RUS on exchange server   

Hi,
 some time ago a DC failed and was never replaced. Due to hardware failure, 
dcpromo was never run to remove the server from the domain, and as a result 
some work has had to be carried out in AD to remove all references to the 
dead server.
Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in the 
log, ( ldap bind was unsuccesful on directory <servername.domainname.com> 
for distinguished name". Directory returned error [0x51] server down.

Looking into the error message it looks like its coming from RUS on the 
exchange box, and after checking whats in RUS, there is an entry in the for 
the dead server.

RUS has entrys for the current DC, as well as the old dead server, i have 
set the update interval in the servers rus properties to never, but is it 
safe to simply delete the server entry in RUS or is there a more gracefull 
way to remove it?

TIA

date: Wed, 9 Jul 2008 10:20:31 +0100   author:   Fred Smith

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

On Wed, 9 Jul 2008 10:20:31 +0100, "Fred Smith"
 wrote:

>Hi,
> some time ago a DC failed and was never replaced. Due to hardware failure, 
>dcpromo was never run to remove the server from the domain, and as a result 
>some work has had to be carried out in AD to remove all references to the 
>dead server.
>Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in the 
>log, ( ldap bind was unsuccesful on directory <servername.domainname.com> 
>for distinguished name". Directory returned error [0x51] server down.
>
>Looking into the error message it looks like its coming from RUS on the 
>exchange box, and after checking whats in RUS, there is an entry in the for 
>the dead server.
>
>RUS has entrys for the current DC, as well as the old dead server, i have 
>set the update interval in the servers rus properties to never, but is it 
>safe to simply delete the server entry in RUS or is there a more gracefull 
>way to remove it?
>
>TIA 


Ensure both the Enterprise and Domain RUS point to a valid DC.

date: Wed, 09 Jul 2008 09:20:59 -0400   author:   Andy David {MVP}

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

Hi Andy,
 i can confirm that both do point at a valid & active dc, so therefore can I 
delete the entry in RUS for the dead server?



"Andy David {MVP}"  wrote in message 
news:ome974l8i8b84llofad6lr29ap1ag7thum@4ax.com...
> On Wed, 9 Jul 2008 10:20:31 +0100, "Fred Smith"
>  wrote:
>
>>Hi,
>> some time ago a DC failed and was never replaced. Due to hardware 
>> failure,
>>dcpromo was never run to remove the server from the domain, and as a 
>>result
>>some work has had to be carried out in AD to remove all references to the
>>dead server.
>>Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in 
>>the
>>log, ( ldap bind was unsuccesful on directory <servername.domainname.com>
>>for distinguished name". Directory returned error [0x51] server down.
>>
>>Looking into the error message it looks like its coming from RUS on the
>>exchange box, and after checking whats in RUS, there is an entry in the 
>>for
>>the dead server.
>>
>>RUS has entrys for the current DC, as well as the old dead server, i have
>>set the update interval in the servers rus properties to never, but is it
>>safe to simply delete the server entry in RUS or is there a more gracefull
>>way to remove it?
>>
>>TIA
>
>
> Ensure both the Enterprise and Domain RUS point to a valid DC.
>

date: Wed, 9 Jul 2008 14:56:38 +0100   author:   Fred Smith

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

On Wed, 9 Jul 2008 14:56:38 +0100, "Fred Smith"
 wrote:

>Hi Andy,
> i can confirm that both do point at a valid & active dc, so therefore can I 
>delete the entry in RUS for the dead server?

Where is that entry listed exactly?


>
>
>
>"Andy David {MVP}"  wrote in message 
>news:ome974l8i8b84llofad6lr29ap1ag7thum@4ax.com...
>> On Wed, 9 Jul 2008 10:20:31 +0100, "Fred Smith"
>>  wrote:
>>
>>>Hi,
>>> some time ago a DC failed and was never replaced. Due to hardware 
>>> failure,
>>>dcpromo was never run to remove the server from the domain, and as a 
>>>result
>>>some work has had to be carried out in AD to remove all references to the
>>>dead server.
>>>Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in 
>>>the
>>>log, ( ldap bind was unsuccesful on directory <servername.domainname.com>
>>>for distinguished name". Directory returned error [0x51] server down.
>>>
>>>Looking into the error message it looks like its coming from RUS on the
>>>exchange box, and after checking whats in RUS, there is an entry in the 
>>>for
>>>the dead server.
>>>
>>>RUS has entrys for the current DC, as well as the old dead server, i have
>>>set the update interval in the servers rus properties to never, but is it
>>>safe to simply delete the server entry in RUS or is there a more gracefull
>>>way to remove it?
>>>
>>>TIA
>>
>>
>> Ensure both the Enterprise and Domain RUS point to a valid DC.
>>

date: Wed, 09 Jul 2008 11:07:39 -0400   author:   Andy David {MVP}

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

Make sure you run through these steps.

How to remove completely orphaned Domain Controller
http://support.microsoft.com/kb/555846



James Chong (MVP)
MCITP | EMA; MCSE | M, S,
Security, Project, ITIL
msexchangetips.blogspot.com



On Jul 9, 9:56 am, "Fred Smith"  wrote:
> Hi Andy,
>  i can confirm that both do point at a valid & active dc, so therefore can I
> delete the entry in RUS for the dead server?
>
> "Andy David {MVP}"  wrote in messagenews:ome974l8i8b84llofad6lr29ap1ag7thum@4ax.com...
>
>
>
> > On Wed, 9 Jul 2008 10:20:31 퍝, "Fred Smith"
> >  wrote:
>
> >>Hi,
> >> some time ago a DC failed and was never replaced. Due to hardware
> >> failure,
> >>dcpromo was never run to remove the server from the domain, and as a
> >>result
> >>some work has had to be carried out in AD to remove all references to the
> >>dead server.
> >>Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in
> >>the
> >>log, ( ldap bind was unsuccesful on directory <servername.domainname.com>
> >>for distinguished name". Directory returned error [0x51] server down.
>
> >>Looking into the error message it looks like its coming from RUS on the
> >>exchange box, and after checking whats in RUS, there is an entry in the
> >>for
> >>the dead server.
>
> >>RUS has entrys for the current DC, as well as the old dead server, i have
> >>set the update interval in the servers rus properties to never, but is it
> >>safe to simply delete the server entry in RUS or is there a more gracefull
> >>way to remove it?
>
> >>TIA
>
> > Ensure both the Enterprise and Domain RUS point to a valid DC.- Hide quoted text -
>
> - Show quoted text -

date: Wed, 9 Jul 2008 12:37:04 -0700 (PDT)   author:   Jamestechman

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

Hi Andy,
 if i look in the RUS properties in ESM, i can see 3 entries...the first to 
relate to the current exchange server and the new DC. The dead server is 
also listed in there, and has a 1 after the servername.
From what i can see, it looks like the entry for the old server needs to be 
removed somehow?

i can give more precise syntax in the morning (GMT) when i get back to work 
if that helps?

Cheers



"Andy David {MVP}"  wrote in message 
news:41l97415chmbuv20rn6002svsapdnqaorm@4ax.com...
> On Wed, 9 Jul 2008 14:56:38 +0100, "Fred Smith"
>  wrote:
>
>>Hi Andy,
>> i can confirm that both do point at a valid & active dc, so therefore can 
>> I
>>delete the entry in RUS for the dead server?
>
> Where is that entry listed exactly?
>
>
>>
>>
>>
>>"Andy David {MVP}"  wrote in 
>>message
>>news:ome974l8i8b84llofad6lr29ap1ag7thum@4ax.com...
>>> On Wed, 9 Jul 2008 10:20:31 +0100, "Fred Smith"
>>>  wrote:
>>>
>>>>Hi,
>>>> some time ago a DC failed and was never replaced. Due to hardware
>>>> failure,
>>>>dcpromo was never run to remove the server from the domain, and as a
>>>>result
>>>>some work has had to be carried out in AD to remove all references to 
>>>>the
>>>>dead server.
>>>>Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in
>>>>the
>>>>log, ( ldap bind was unsuccesful on directory 
>>>><servername.domainname.com>
>>>>for distinguished name". Directory returned error [0x51] server down.
>>>>
>>>>Looking into the error message it looks like its coming from RUS on the
>>>>exchange box, and after checking whats in RUS, there is an entry in the
>>>>for
>>>>the dead server.
>>>>
>>>>RUS has entrys for the current DC, as well as the old dead server, i 
>>>>have
>>>>set the update interval in the servers rus properties to never, but is 
>>>>it
>>>>safe to simply delete the server entry in RUS or is there a more 
>>>>gracefull
>>>>way to remove it?
>>>>
>>>>TIA
>>>
>>>
>>> Ensure both the Enterprise and Domain RUS point to a valid DC.
>>>

date: Thu, 10 Jul 2008 00:13:34 +0100   author:   Fred Smith

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

In reply to Andy's posting,
 if i look in the RUS menu within ESM, there are 3 entries....

1 recipient update service (enterprise configuration) /dns domainname.com / 
correct DC / Correct mailserver name

2 recipient update service (internaldomainname)/ domainname.com / correct DC 
/ Correct mailserver name

3 recipient update service (internaldomainname) 1 / dns domainname.com/ old 
dead dc name/ correct mailserver name


# 3 appears to be the legacy entry referrring to the previous DC which died, 
and was not dcpromo'ed.  i'm thinking that this is the entry which is 
causing the issue.

#1 & #2 appear to be correct, and refer to corredct domain names, dns names 
& DC server name.

I have set the update interval on #3 to never, to try and stop the service 
from interferring with things, however what would / could be the impact if 
the entry was deleted from the RUS services menu?

TIA






On Jul 9, 9:56 am, "Fred Smith"  wrote:
> Hi Andy,
> i can confirm that both do point at a valid & active dc, so therefore can 
> I
> delete the entry in RUS for the dead server?
>
> "Andy David {MVP}"  wrote in 
> messagenews:ome974l8i8b84llofad6lr29ap1ag7thum@4ax.com...
>
>
>
> > On Wed, 9 Jul 2008 10:20:31 +0100, "Fred Smith"
> >  wrote:
>
> >>Hi,
> >> some time ago a DC failed and was never replaced. Due to hardware
> >> failure,
> >>dcpromo was never run to remove the server from the domain, and as a
> >>result
> >>some work has had to be carried out in AD to remove all references to 
> >>the
> >>dead server.
> >>Our exchange box (2003 & exch 2003) is now bringing up event id 8026 in
> >>the
> >>log, ( ldap bind was unsuccesful on directory 
> >><servername.domainname.com>
> >>for distinguished name". Directory returned error [0x51] server down.
>
> >>Looking into the error message it looks like its coming from RUS on the
> >>exchange box, and after checking whats in RUS, there is an entry in the
> >>for
> >>the dead server.
>
> >>RUS has entrys for the current DC, as well as the old dead server, i 
> >>have
> >>set the update interval in the servers rus properties to never, but is 
> >>it
> >>safe to simply delete the server entry in RUS or is there a more 
> >>gracefull
> >>way to remove it?
>
> >>TIA
>
> > Ensure both the Enterprise and Domain RUS point to a valid DC.- Hide 
> > quoted text -
>
> - Show quoted text -

date: Thu, 10 Jul 2008 09:44:03 +0100   author:   Fred Smith

Re: ungraceful removal of a DC / event id 8026 & RUS on exchange server   

On Thu, 10 Jul 2008 09:44:03 +0100, "Fred Smith"
 wrote:

					[ snip ]

># 3 appears to be the legacy entry referrring to the previous DC which died, 
>and was not dcpromo'ed.  i'm thinking that this is the entry which is 
>causing the issue.
>
>#1 & #2 appear to be correct, and refer to corredct domain names, dns names 
>& DC server name.
>
>I have set the update interval on #3 to never, to try and stop the service 
>from interferring with things, however what would / could be the impact if 
>the entry was deleted from the RUS services menu?

If you have a working RUS for the domain, just delete the one (#3)
that's using the bogus GC.
---
Rich Matheisen
MCSE+I, Exchange MVP

date: Thu, 10 Jul 2008 21:47:44 -0400   author:   Rich Matheisen [MVP]