Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

event 5020 msexchangetransport 1

Status
Not open for further replies.

johng75

IS-IT--Management
Jul 14, 2004
247
0
0
US
event 5020 msexchangetransport

i getting the error:
Code:
Log Name:      Application
Source:        MSExchangeTransport
Date:          2/15/2012 12:21:19 PM
Event ID:      5020
Task Category: Routing
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      NEW.DOMAIN.COM
Description:
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 OLD.DOMAIN.COM in Routing Group CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=com in routing tables with the timestamp 2/15/2012 5:21:19 PM.
Event Xml:
<Event xmlns="[URL unfurl="true"]http://schemas.microsoft.com/win/2004/08/events/event">[/URL]
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="32772">5020</EventID>
    <Level>3</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-02-15T17:21:19.000Z" />
    <EventRecordID>2602303</EventRecordID>
    <Channel>Application</Channel>
    <Computer>NEW.DOMAIN.COM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>OLD.DOMAIN.COM</Data>
    <Data>CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=com</Data>
    <Data>2/15/2012 5:21:19 PM</Data>
  </EventData>
</Event>


the problem is the OLD doamin server crashed and didnt have a good backup... so now im stuck with just the exchange 2010 server, and would like to find a way to fix these errors...

ive gone line by line in ADSIEdit.msc and see no reference anywhere to the First Admistrative Group or the OLD server anywhere...
 
If the default AG is gone, there are generally more serious issues.

If you do a Get-RoutingGroupConnector, what's it show?

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.
 
the command shows no results...

Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"
 
So, in ADSIEdit, connecting to the config container, going to Configuration>Services>Microsoft Exchange>[Org Name]>Administrative Groups, the first AG doesn't show up?

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.
 
*doh* i was connecting to a different container...

i connected to the proper container, went thru the levels and found the First Administrative Group, and everything contained within...

ive read a few different articles, most say to just delete the SERVER entry and the 'branches' below it...

is there any reason i can go a few 'branches' higher and just delete the First Admin Group?
 
Do NOT delete the First AG.
Do NOT delete the First AG.
Do NOT delete the First AG.
Do NOT delete the First AG.
Do NOT delete the First AG.
Do NOT delete the First AG.
Do NOT delete the First AG.
Do NOT delete the First AG.

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.
 
soooo, im guessing you just recommend the server entry then?
lol

Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"
 
CN=First AG
CN=Servers
CN=(Server name)
CN=InfoStore
CN=Microsoft MTA
CN=Microsoft System Attendant
CN=Protocols


so just the (Server Name) and ones below it are what i should remove...?

Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"
 
If that server is no longer available, and you won't be doing a disaster recovery restore of it, kill it.

- of course, any time someone is in ADSIEDIT, I must add - I provide no warranty, nor assume no liability, from actions you take. YMMV. :)

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.
 
understood... CYA heard and acknowledged... lol

Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top