Old Exchange 2003 server no longer works since we removed and old DC

  • Thread starter Whiteford
  • Start date Views 3,822
Status
Not open for further replies.
W

Whiteford

Hi,

We have a Windows 2003 AD and have recently upgraded to Exchange 2007. We

still kept our old Exchange 2003 server live for old restores etc. We

recently removed an old DC, I just did a DCpromo etc and cleaned up the

metadata and DNS and we now have 3 healthy DC's working. The DC I removed

was the very first DC we built when upgrading our domain from Windows NT 4.0

to 2003.

Since I have removed the old DC our Exchange server no longer works the MTA

and Information Store server no longer start and the Event ID I get is:

Event ID 5000 MSExchangeIS Error 0x8004010f connecting to Active Directory

I have ran DCdiag and NTdiag and all come back fine. I have tried

reinstalling Exchnage but I get the same issues, is it best to remove

Exchange from AD and start from fresh? I have read I can use from the

Exchange 2003 CD the setup.exe /removeorg switch, but am no sure of this

will also remove the Exchnage 2007 setup from the schema.

Please advise, hopefully the old Exchange 2003 server is looking for our old

DC somewhere, I've done some basic checks.
 
R

Rich Matheisen [MVP]

On Sun, 25 Oct 2009 11:26:21 -0000, "Whiteford" <no@no.com> wrote:


> Hi,

> We have a Windows 2003 AD and have recently upgraded to Exchange 2007. We
> still kept our old Exchange 2003 server live for old restores etc. We
> recently removed an old DC, I just did a DCpromo etc and cleaned up the
> metadata and DNS and we now have 3 healthy DC's working. The DC I removed
> was the very first DC we built when upgrading our domain from Windows NT 4.0
> to 2003.

> Since I have removed the old DC our Exchange server no longer works the MTA
> and Information Store server no longer start and the Event ID I get is:

> Event ID 5000 MSExchangeIS Error 0x8004010f connecting to Active Directory

> I have ran DCdiag and NTdiag and all come back fine. I have tried
> reinstalling Exchnage but I get the same issues, is it best to remove
> Exchange from AD and start from fresh? I have read I can use from the
> Exchange 2003 CD the setup.exe /removeorg switch, but am no sure of this
> will also remove the Exchnage 2007 setup from the schema.

> Please advise, hopefully the old Exchange 2003 server is looking for our old
> DC somewhere, I've done some basic checks.


Check the "Directory Access" tab on the server's property page. Make

sure the "Automatically discover servers" box is checked on each of

the three specific choices in the "Show" drop-down list box.

It may take a little while for any changes to take effect.

You can set the "Diagnostics Logging" on that server for

"MSExchangeDSAccess Topology" to, say, "Maximum" and check the

Application Log for event-id 2080 to see the results of the the

DSAccess discovery.

-
Rich Matheisen

 
W

Whiteford

Hi,

the DC's are all the current live DC's :(

I just tried to create a new Storage group then a New DB under that and go

the popup error:

"A constraint violation occurred.

Facility: LDAP Provider

ID no: 8007202f

Exchange System Manager"

And in the event logs (EVENT ID 8260) the old DC appears!!! I'm happy but

shouldn't be as I don't know why.

Could not open LDAP session to directory 'old-DC.corp.local' using local

service credentials. Cannot access Address List configuration information.

Make sure the server 'old-DC.corp.local' is running. DC=corp,DC=local

Why can't i get it to see the new DC's?

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:p5m9e5pbmgjq6ob6bidbrqa5pavqme15l5@4ax.com...
> On Sun, 25 Oct 2009 11:26:21 -0000, "Whiteford" <no@no.com> wrote:
>
> >Hi,
>

>>We have a Windows 2003 AD and have recently upgraded to Exchange 2007.
> >We
> >still kept our old Exchange 2003 server live for old restores etc. We
> >recently removed an old DC, I just did a DCpromo etc and cleaned up the
> >metadata and DNS and we now have 3 healthy DC's working. The DC I removed
> >was the very first DC we built when upgrading our domain from Windows NT
> >4.0
> >to 2003.
>

>>Since I have removed the old DC our Exchange server no longer works the
> >MTA
> >and Information Store server no longer start and the Event ID I get is:
>

>>Event ID 5000 MSExchangeIS Error 0x8004010f connecting to Active Directory
>

>>I have ran DCdiag and NTdiag and all come back fine. I have tried
> >reinstalling Exchnage but I get the same issues, is it best to remove
> >Exchange from AD and start from fresh? I have read I can use from the
> >Exchange 2003 CD the setup.exe /removeorg switch, but am no sure of this
> >will also remove the Exchnage 2007 setup from the schema.
>

>>Please advise, hopefully the old Exchange 2003 server is looking for our
> >old
> >DC somewhere, I've done some basic checks.


> Check the "Directory Access" tab on the server's property page. Make
> sure the "Automatically discover servers" box is checked on each of
> the three specific choices in the "Show" drop-down list box.

> It may take a little while for any changes to take effect.

> You can set the "Diagnostics Logging" on that server for
> "MSExchangeDSAccess Topology" to, say, "Maximum" and check the
> Application Log for event-id 2080 to see the results of the the
> DSAccess discovery.
> -> Rich Matheisen
>
 
R

Rich Matheisen [MVP]

On Mon, 26 Oct 2009 14:27:55 -0000, "Whiteford" <no@no.com> wrote:

[ snip ]


> Why can't i get it to see the new DC's?


Don't know -- but it might pay to have a look at the registry on that

server:

http://technet.microsoft.com/en-us/library/bb124641(EXCHG.65).aspx

Even if the GUI says everything's okay, sometimes falling back to the

old manual ways of doing things works better.

I'd set up the configuration, domain, and global catalog values to use

the same DC in the registry. Then see if it still gives you the same

error. If it does, reboot the box one time and see if that changes

anything.

If the error goes away, remove all the registry stuff and go back to

using the auto-detect. If it fails again I think you might have

someing in the AD that wasn't removed cleanly. Check DNS, too. Maybe

there's still stuff in there (in the _msdcs zone) for the old machine.

Check the AD Sites and Services snap-in, too. Maybe there's left over

NTDS info for that machine.

-
Rich Matheisen

 
W

Whiteford

Thanks for finding the time to help on this, but still no luck.

Is it possible to remove Exchange 2003 attributes from AD? I can then

rebuild it from scratch, same name, SG's, DB's etc, the structure?

I have read I can run the Exchange 2003 setup.exe file with the switch

/removeorg ?

If I run that can I then reinstall Exchange 2003 also will it cause an issue

with our Exchange 2007 or is this switch nothing to do do with 2007?

Thanks

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:8lpce5ta8po32fsd77k49s00tp8uq7t82m@4ax.com...
> On Mon, 26 Oct 2009 14:27:55 -0000, "Whiteford" <no@no.com> wrote:

> [ snip ]
>
> >Why can't i get it to see the new DC's?


> Don't know -- but it might pay to have a look at the registry on that
> server:

> http://technet.microsoft.com/en-us/library/bb124641(EXCHG.65).aspx

> Even if the GUI says everything's okay, sometimes falling back to the
> old manual ways of doing things works better.

> I'd set up the configuration, domain, and global catalog values to use
> the same DC in the registry. Then see if it still gives you the same
> error. If it does, reboot the box one time and see if that changes
> anything.

> If the error goes away, remove all the registry stuff and go back to
> using the auto-detect. If it fails again I think you might have
> someing in the AD that wasn't removed cleanly. Check DNS, too. Maybe
> there's still stuff in there (in the _msdcs zone) for the old machine.
> Check the AD Sites and Services snap-in, too. Maybe there's left over
> NTDS info for that machine.
> -> Rich Matheisen
>
 
W

Whiteford

Ah, this old DC is in _msdcs zone in DNS, but I can't remove it.

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:8lpce5ta8po32fsd77k49s00tp8uq7t82m@4ax.com...
> On Mon, 26 Oct 2009 14:27:55 -0000, "Whiteford" <no@no.com> wrote:

> [ snip ]
>
> >Why can't i get it to see the new DC's?


> Don't know -- but it might pay to have a look at the registry on that
> server:

> http://technet.microsoft.com/en-us/library/bb124641(EXCHG.65).aspx

> Even if the GUI says everything's okay, sometimes falling back to the
> old manual ways of doing things works better.

> I'd set up the configuration, domain, and global catalog values to use
> the same DC in the registry. Then see if it still gives you the same
> error. If it does, reboot the box one time and see if that changes
> anything.

> If the error goes away, remove all the registry stuff and go back to
> using the auto-detect. If it fails again I think you might have
> someing in the AD that wasn't removed cleanly. Check DNS, too. Maybe
> there's still stuff in there (in the _msdcs zone) for the old machine.
> Check the AD Sites and Services snap-in, too. Maybe there's left over
> NTDS info for that machine.
> -> Rich Matheisen
>
 
R

Rich Matheisen [MVP]

On Tue, 27 Oct 2009 16:32:31 -0000, "Whiteford" <no@no.com> wrote:


> Thanks for finding the time to help on this, but still no luck.

> Is it possible to remove Exchange 2003 attributes from AD? I can then
> rebuild it from scratch, same name, SG's, DB's etc, the structure?


You can, but I'm guessing you'll still have the problem. Exchange,

assuming the DC isn't set in the registry, is finding the DC somehow.

Dunno how, but it's either in the AD sites as an NTDS object or it's

in DNS in the _msdcs zone.


> I have read I can run the Exchange 2003 setup.exe file with the switch
> /removeorg ?

> If I run that can I then reinstall Exchange 2003 also will it cause an issue
> with our Exchange 2007 or is this switch nothing to do do with 2007?


Well, if you remove the organization from the configuration container

you remove all of Exchange, not just a single server. That doesn't

sound like a good idea to me. :)

-
Rich Matheisen

 
R

Rich Matheisen [MVP]

On Tue, 27 Oct 2009 16:43:39 -0000, "Whiteford" <no@no.com> wrote:


> Ah, this old DC is in _msdcs zone in DNS, but I can't remove it.


But you don't find it in the "Servers" container beneath one of the AD

Sites in the "Active Directory Sites and Services" snap-in? There

should be a NTDS beneath the server and the properties of that object

have a "DNS Alias". If the server was demoted you should be able to

remove the server from the AD site.

-
Rich Matheisen

 
W

Whiteford

So woudl that mean it will remove the Exchange 2007 servers to (removeorg)?

We only had 1 x Exchange 2003 server, and now we have 4 Exchange 2007

servers (2 x mbx and 2 x CAS).

I tried the removeorg on a cone DC and managed to reinstall the Exchange

2003 server, but had to build the structure again, which was fine.

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:609fe55a1og8c5ktumlm4u18a1s2ti18q0@4ax.com...
> On Tue, 27 Oct 2009 16:32:31 -0000, "Whiteford" <no@no.com> wrote:
>
> >Thanks for finding the time to help on this, but still no luck.
>

>>Is it possible to remove Exchange 2003 attributes from AD? I can then
> >rebuild it from scratch, same name, SG's, DB's etc, the structure?


> You can, but I'm guessing you'll still have the problem. Exchange,
> assuming the DC isn't set in the registry, is finding the DC somehow.
> Dunno how, but it's either in the AD sites as an NTDS object or it's
> in DNS in the _msdcs zone.
>
> >I have read I can run the Exchange 2003 setup.exe file with the switch
> >/removeorg ?
>

>>If I run that can I then reinstall Exchange 2003 also will it cause an
> >issue
> >with our Exchange 2007 or is this switch nothing to do do with 2007?


> Well, if you remove the organization from the configuration container
> you remove all of Exchange, not just a single server. That doesn't
> sound like a good idea to me. :)
> -> Rich Matheisen
>
 
W

Whiteford

The DNS alias is 82B9CF96-96E6-410F-A25B-76B5E658EE2F._msdcs.local under

sites > Name > Servers > DC name > NTDS settings

What is this?

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:l79fe5duu4otni43asmov6o7cle7o1q867@4ax.com...
> On Tue, 27 Oct 2009 16:43:39 -0000, "Whiteford" <no@no.com> wrote:
>
> >Ah, this old DC is in _msdcs zone in DNS, but I can't remove it.


> But you don't find it in the "Servers" container beneath one of the AD
> Sites in the "Active Directory Sites and Services" snap-in? There
> should be a NTDS beneath the server and the properties of that object
> have a "DNS Alias". If the server was demoted you should be able to
> remove the server from the AD site.
> -> Rich Matheisen
>
 
R

Rich Matheisen [MVP]

On Wed, 28 Oct 2009 16:13:45 -0000, "Whiteford" <no@no.com> wrote:


> So woudl that mean it will remove the Exchange 2007 servers to (removeorg)?


No, it will remove the entire Exchange organization.

-
Rich Matheisen

 
R

Rich Matheisen [MVP]

On Wed, 28 Oct 2009 16:22:33 -0000, "Whiteford" <no@no.com> wrote:


> The DNS alias is 82B9CF96-96E6-410F-A25B-76B5E658EE2F._msdcs.local under
> sites > Name > Servers > DC name > NTDS settings

> What is this?


It's a domain controller.

What's the name of the server container that holds that NTDS object.

Is it the name of a "live" DC or the name of the DC you think you got

rid of by running dcpromo on it?

-
Rich Matheisen

 
W

Whiteford

oh, I didn't know it would remove everything (Exchange 2003 and 2007), I

will leave that one :S

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:t6uhe5d5nm14jvhvkhrjep2vboj50nrg9p@4ax.com...
> On Wed, 28 Oct 2009 16:13:45 -0000, "Whiteford" <no@no.com> wrote:
>
> >So woudl that mean it will remove the Exchange 2007 servers to
> >(removeorg)?


> No, it will remove the entire Exchange organization.
> -> Rich Matheisen
>
 
W

Whiteford

It's the name of the good server, I can't find the old DC server anywhere.

Looking back at our helpdesk logs the decommission of the old DC did cause

the old Exchange 2003 server to stop working. Thing is we hae no users on

it, it is only for old restores, but I'd still like to have it on our live

Domain.

I could create a new domani with the same name and same Exchange server on a

separate VLAN/DMZ I suppose.

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:t8uhe5timljrib4eg2ob287nmour9ullla@4ax.com...
> On Wed, 28 Oct 2009 16:22:33 -0000, "Whiteford" <no@no.com> wrote:
>
> >The DNS alias is 82B9CF96-96E6-410F-A25B-76B5E658EE2F._msdcs.local under
> >sites > Name > Servers > DC name > NTDS settings
>

>>What is this?


> It's a domain controller.

> What's the name of the server container that holds that NTDS object.
> Is it the name of a "live" DC or the name of the DC you think you got
> rid of by running dcpromo on it?
> -> Rich Matheisen
>
 
R

Rich Matheisen [MVP]

On Thu, 29 Oct 2009 08:12:46 -0000, "Whiteford" <no@no.com> wrote:


> oh, I didn't know it would remove everything (Exchange 2003 and 2007), I
> will leave that one :S


Good thinking. :)

-
Rich Matheisen

 
R

Rich Matheisen [MVP]

On Thu, 29 Oct 2009 08:15:35 -0000, "Whiteford" <no@no.com> wrote:


> It's the name of the good server,


Well, then leave that one alone. :)


> I can't find the old DC server anywhere.
> Looking back at our helpdesk logs the decommission of the old DC did cause
> the old Exchange 2003 server to stop working. Thing is we hae no users on
> it, it is only for old restores, but I'd still like to have it on our live
> Domain.

> I could create a new domani with the same name and same Exchange server on a
> separate VLAN/DMZ I suppose.


The point is that if the DC and GC names aren't specified in the

registry of the Exchange server then it's discovering them in either

the AD or the DNS.

On the Exchange server, set the "Diagnostics Logging" for the

MSEXchangeDSAccess Topology" to "Maximum" for a hour. Check the

Application Log for Event-ID 2080. That'll show you what the server is

finding for directories.

-
Rich Matheisen

 
W

Whiteford

Event ID 2080 looks ok now, but still can't start the Inforamtion or MTA

service:

Process MAD.EXE (PID=1576). DSAccess has discovered the following servers

with the following characteristics:

(Server name | Roles | Reachability | Synchronized | GC capable | PDC |

SACL right | Critical Data | Netlogon | OS Version)

In-site:

DC1.local CDG 7 7 1 0 1 1 7 1

DC2.local CDG 7 7 1 0 1 1 7 1

Out-of-site:

DC3.local CDG 7 7 1 0 1 1 7 1

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:2qike5dd2n9h1t134nk3t90ualj3pi0bua@4ax.com...
> On Thu, 29 Oct 2009 08:15:35 -0000, "Whiteford" <no@no.com> wrote:
>
> >It's the name of the good server,


> Well, then leave that one alone. :)
>
> >I can't find the old DC server anywhere.
> >Looking back at our helpdesk logs the decommission of the old DC did cause
> >the old Exchange 2003 server to stop working. Thing is we hae no users on
> >it, it is only for old restores, but I'd still like to have it on our live
> >Domain.
>

>>I could create a new domani with the same name and same Exchange server on
> >a
> >separate VLAN/DMZ I suppose.


> The point is that if the DC and GC names aren't specified in the
> registry of the Exchange server then it's discovering them in either
> the AD or the DNS.

> On the Exchange server, set the "Diagnostics Logging" for the
> MSEXchangeDSAccess Topology" to "Maximum" for a hour. Check the
> Application Log for Event-ID 2080. That'll show you what the server is
> finding for directories.
> -> Rich Matheisen
>
 
W

Whiteford

I do also see this error, is it important:

Event ID 913 MSExchangeTransport:

Routing information in the Directory Service is either corrupt or

incomplete. Process Id: 1244 Process location:

C:\WINDOWS\system32\inetsrv\inetinfo.exe ComponentDN: CN=Comapny

Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=gb,DC=vo,DC=local

Event ID 2078 MSExchangeDSaccess

Process INETINFO.EXE (PID=1244). DSAccess is shutting down.

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:2qike5dd2n9h1t134nk3t90ualj3pi0bua@4ax.com...
> On Thu, 29 Oct 2009 08:15:35 -0000, "Whiteford" <no@no.com> wrote:
>
> >It's the name of the good server,


> Well, then leave that one alone. :)
>
> >I can't find the old DC server anywhere.
> >Looking back at our helpdesk logs the decommission of the old DC did cause
> >the old Exchange 2003 server to stop working. Thing is we hae no users on
> >it, it is only for old restores, but I'd still like to have it on our live
> >Domain.
>

>>I could create a new domani with the same name and same Exchange server on
> >a
> >separate VLAN/DMZ I suppose.


> The point is that if the DC and GC names aren't specified in the
> registry of the Exchange server then it's discovering them in either
> the AD or the DNS.

> On the Exchange server, set the "Diagnostics Logging" for the
> MSEXchangeDSAccess Topology" to "Maximum" for a hour. Check the
> Application Log for Event-ID 2080. That'll show you what the server is
> finding for directories.
> -> Rich Matheisen
>
 
R

Rich Matheisen [MVP]

On Fri, 30 Oct 2009 11:42:34 -0000, "Whiteford" <no@no.com> wrote:


> I do also see this error, is it important:


If inetinfo isn't running, yeah.



> Event ID 913 MSExchangeTransport:

> Routing information in the Directory Service is either corrupt or
> incomplete. Process Id: 1244 Process location:
> C:\WINDOWS\system32\inetsrv\inetinfo.exe ComponentDN: CN=Comapny
> Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=gb,DC=vo,DC=local

> Event ID 2078 MSExchangeDSaccess

> Process INETINFO.EXE (PID=1244). DSAccess is shutting down.


If all you're going to use this machine for is recovery work, I'd make

careful note of its configuration (location and names of file systrem

directories, etc.) and remove the machine using setup.exe. Then

reinstall the machine using the same name and configuration.

The machine isn't used for anything else, right? It's not the OAB

server, it has no public folder replicas, no user mailboxes, or any of

the other things that should be moved to the Exchange 2007 servers

before removing the last E2K3 server in the organization?

-
Rich Matheisen

 
W

Whiteford

This server is only used for restores of pre 2007 mailboxes. I have

uninstalled it before, but when I reinstall it, it seems AD puts everything

back, the names, DB locations etc. You suggest a clean install how could I

do this, as it sounds like the best way now?

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message

news:ki8ne5dafj0843ru4gd93e6attqkcnpin4@4ax.com...
> On Fri, 30 Oct 2009 11:42:34 -0000, "Whiteford" <no@no.com> wrote:
>
> >I do also see this error, is it important:


> If inetinfo isn't running, yeah.
>
>

>>Event ID 913 MSExchangeTransport:
>

>>Routing information in the Directory Service is either corrupt or
> >incomplete. Process Id: 1244 Process location:
> >C:\WINDOWS\system32\inetsrv\inetinfo.exe ComponentDN: CN=Comapny
> >Name,CN=Microsoft
> >Exchange,CN=Services,CN=Configuration,DC=gb,DC=vo,DC=local
>

>>Event ID 2078 MSExchangeDSaccess
>

>>Process INETINFO.EXE (PID=1244). DSAccess is shutting down.


> If all you're going to use this machine for is recovery work, I'd make
> careful note of its configuration (location and names of file systrem
> directories, etc.) and remove the machine using setup.exe. Then
> reinstall the machine using the same name and configuration.

> The machine isn't used for anything else, right? It's not the OAB
> server, it has no public folder replicas, no user mailboxes, or any of
> the other things that should be moved to the Exchange 2007 servers
> before removing the last E2K3 server in the organization?
> -> Rich Matheisen
>
 
Status
Not open for further replies.
Top