Attempt to connect to non-existent GC

gjb · Joined: 05 Aug 2007 Posts: 4

Hi,

The following event is being generated by one of my Exchange VSs. The DC/GC
concerned was removed from the org using the metadata cleanup KB article
about 2 weeks ago after it failed and could not be recovered.
I am at a loss as to why exchange servers are attempting to connect people
to it after all this time. Any advice greatly appreciated as I have rebuilt
the server and intend to re-dcpromo it in a few days time.

Regards,

Gerry

Archived from group: microsoft>public>exchange2000>active>directory>integration

Dave Howe [MSFT] · Joined: 06 Aug 2007 Posts: 4

On Thu, 29 Apr 2004 16:29:23 +0100, "gjb"
wrote:

>Hi,
>
>The following event is being generated by one of my Exchange VSs. The DC/GC
>concerned was removed from the org using the metadata cleanup KB article
>about 2 weeks ago after it failed and could not be recovered.
>I am at a loss as to why exchange servers are attempting to connect people
>to it after all this time. Any advice greatly appreciated as I have rebuilt
>the server and intend to re-dcpromo it in a few days time.
>
>Regards,
>
>Gerry
>

If you open the properties of the Exchange server, click on the
Directory Access tab. Do you see that GC listed or is it set to Auto
discover? Have you considered rebooting the Exchange server, or have
you already done that?

---

Dave Howe
Microsoft PSS

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

gjb · Joined: 05 Aug 2007 Posts: 4

Dave,

Thanks for the quick reply. That server is not listed. All the real DC/GC
are listed and it is set to autodiscover. Maybe a reboot will sort it.

"Dave Howe [MSFT]" wrote in message@4ax.com...
> On Thu, 29 Apr 2004 16:29:23 +0100, "gjb"
> wrote:
>
> >Hi,
> >
> >The following event is being generated by one of my Exchange VSs. The
DC/GC
> >concerned was removed from the org using the metadata cleanup KB article
> >about 2 weeks ago after it failed and could not be recovered.
> >I am at a loss as to why exchange servers are attempting to connect
people
> >to it after all this time. Any advice greatly appreciated as I have
rebuilt
> >the server and intend to re-dcpromo it in a few days time.
> >
> >Regards,
> >
> >Gerry
> >
>
> If you open the properties of the Exchange server, click on the
> Directory Access tab. Do you see that GC listed or is it set to Auto
> discover? Have you considered rebooting the Exchange server, or have
> you already done that?
>
> ---
>
> Dave Howe
> Microsoft PSS
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.

J.H · Joined: 05 Aug 2007 Posts: 10

Hi there,
I hope when you removed that DC/GC,,,that's not the first domain controller,
and that's not the only one DC/GC in your infrastructure, is that ?

right click on the server name in ESM, check for directory access if it is
still listed
the removed DC/GC. And also check in recipient update, what is the domain
controller
listed over there ? Per my experience, the domain controller listed in
recipient update is always
the first domain controller, primary domain controller. And if it is the one
you removed, you
will have problems!!!

Seizing domain controller will help!!!

Regards,
J.H

"gjb" wrote in message
news:%23H9iE7fLEHA.1272@tk2msftngp13.phx.gbl...
> Hi,
>
> The following event is being generated by one of my Exchange VSs. The
DC/GC
> concerned was removed from the org using the metadata cleanup KB article
> about 2 weeks ago after it failed and could not be recovered.
> I am at a loss as to why exchange servers are attempting to connect people
> to it after all this time. Any advice greatly appreciated as I have
rebuilt
> the server and intend to re-dcpromo it in a few days time.
>
> Regards,
>
> Gerry
>
>

Dave Howe [MSFT] · Joined: 06 Aug 2007 Posts: 4

On Thu, 29 Apr 2004 09:27:10 -0700, "J.H" wrote:

>Seizing domain controller will help!!!

But before you do that, you may want to drop to a command prompt and
type: NETDOM QUERY FSMO

If they all reference the removed domain controller, then JH is right,
you'll need to seize those roles.

---

Dave Howe
Microsoft PSS

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

gjb · Joined: 05 Aug 2007 Posts: 4

Thanks for all the responses, The failed DC was fully removed from AD/Exch
and roles siezed, RUS updated etc. It is not listed in any DC/GC list in
ESM.
I am thinking it was perhaps a request from an older outlook client with the
old GC value cached. I have not seen the error again and it was only
reported twice, so perhaps it has "gone away".

Thanks again,

Gerry
"Dave Howe [MSFT]" wrote in message@4ax.com...
> On Thu, 29 Apr 2004 09:27:10 -0700, "J.H" wrote:
>
>
> >Seizing domain controller will help!!!
>
> But before you do that, you may want to drop to a command prompt and
> type: NETDOM QUERY FSMO
>
> If they all reference the removed domain controller, then JH is right,
> you'll need to seize those roles.
>
> ---
>
> Dave Howe
> Microsoft PSS
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.

David Wyatt [MSFT] · Joined: 06 Aug 2007 Posts: 1

There could be manual selection enabled, or in the registry keys the server
is hard coded.
--
David Wyatt
MCSE, MCSA 2000/2003 Messaging

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

OWA initial login attempt Hi, Fairly new at SBS 2003 Exchange OWA deployment. Single Server. Is it true that I should be able to go to from within the network and attach with administator? I use the correct URL and I receive a login box. SITE=server, REA

Not connect to RPC Hi, I have encountered this intermittant problem, having error message and cannot open outlook 2003. The error message being 'The connection to the microsoft Exchange server is unavailable. Outlook must be online or connected to complete this action'. The

Connect to Exchange through VPN across USA We are connecting to the Exchange server through a site to site VPN but there seems to be a fairly substantial lagtime. Would it be wise to (or is is good practice) to put the mail store for those people somewhere on one of their servers?

I need connect to freebusy Please someone help me, I want to connect to next site "FreeBusyURL" but I can´t, how to conncect at this site? or how to configure this? The name of my server is "mensajeria" but only recive an

How to Connect a W2003 Server to Exchange I need to connect my W2003 Server to an Exchange Mailbox. I don't want to install outlook on my server... is there a way to install something like a client on my server?