Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 500
  • Last Modified:

Joining a new 2003 exchange server to 5.5 server getting MTA and MDB errors in log when verification tool is run

Hi,
I recently completed setting up a new 2003 exchange server that is supposed to coexist with our existing 5.5 server. When I run the verification tools I get numerous errors. I am able to verify the name within outlook but cannot actual open the new mailbox. It states that the server is unavailable. The following are the errors I am receiving.

--------> Config results from (objectClass=*) ...

DN = CN=NT04,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$server$msexchexchangeserver
  The exchange server does not have a responsible MTA server (msExchResponsibleMtaServer)

DN = CN=Microsoft DSA,CN=NT04,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$msexchsitereplicationservice
  The srs contains no home-mdb (homeMdb)
  The srs contains no home-mta (homeMta)

DN = CN=Public Information Store (NT04),CN=First Storage Group,CN=InformationStore,CN=NT04,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$msexchmdb$msexchpublicmdb
  The public mdb contains no home-mta (homeMta)

DN = CN=Microsoft System Attendant,CN=NT04,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$exchangeadminservice
  The system attendant contains no home-mdb (homeMdb)
  The system attendant contains no home-mta (homeMta)

DN = CN=Mailbox Store (MAIL),CN=First Storage Group,CN=InformationStore,CN=MAIL,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$msexchmdb$msexchprivatemdb
  The private mdb does not have a corresponding gateway object in the Active Directory

********* finished verifying 630 objects on 10/18/2004 at 10:05:41

Thanks in advance for any help you can give.
0
Darktide00
Asked:
Darktide00
  • 4
  • 2
1 Solution
 
munichpostmanCommented:
Hi,

Have you setup an Active Directory Connector, plus mailbox connection agreements to replicate information between Exchange 5.5 and Exchange 2003?

Was a Config_CA created on your ADC server during the installation of Exchange 2003?
Is the Config_CA pointing to a GC.

Has the SRS service started on the Exchange 2003 server?

Did you install the Exchange 2003 server in the same site as the Exchange 5.5 server?

If the answer to the above is no then please read the following:

http://www.msexchange.org/tutorials/Overview-Active-Directory-Connector.html

If the answer to the above is yes then do the following:

Rerun the recipient update service. Force an update, wait awhile then use LDP to query on to the mailboxes to see if they have Homemdb and Homemta attributes.

If not use ADModify.net to bulk add the correct attributes to the mailboxes.

http://blogs.msdn.com/exchange/archive/2004/08/04/208045.aspx
0
 
Darktide00Author Commented:
Hi,
Thanks for the quick response.....
I have done what you specified above. However,the AdModify.net is stating with an error that the mailboxes already are set to the correct mta and mdb settings. I still receive the same 5 errors as I listed above when using the verification tool. Any other ideas?
Thanks!
0
 
Darktide00Author Commented:
Ok,
I am down to one error message now.... Whew.... Any ideas on this message?

DN = CN=Mailbox Store (MAIL),CN=First Storage Group,CN=InformationStore,CN=MAIL,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$msexchmdb$msexchprivatemdb
  The private mdb does not have a corresponding gateway object in the Active Directory

Thanks in advance for your help!
0
Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
munichpostmanCommented:
Are you still experiencing the same errors? It looks to me as if the RUS hadn't finished updating yesterday.
0
 
Darktide00Author Commented:
Hi,
Yes I am still getting this one last error. I am still unable to open the test account I set up in Outlook.

DN = CN=Mailbox Store (MAIL),CN=First Storage Group,CN=InformationStore,CN=MAIL,CN=Servers,CN=WORKRITE,CN=Administrative Groups,CN=Workrite Uniform Company Inc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=workrite,DC=net
  object-class = top$msexchmdb$msexchprivatemdb
  The private mdb does not have a corresponding gateway object in the Active Directory
0
 
Darktide00Author Commented:
I mounted the mailbox store and this message went away.
I can now open the mailbox through outlook.
Thanks for your help!

One other question... I cannot send to anyone else except for the 2 test users within the mailbox store. I am unable to send to outside accounts such as AOL and receive undeliverable when I try to send from the old 5.5 accounts. Any ideas?
Thanks!
0
 
mbruton44Commented:
How did you fix the system attendant error?

I am getting the same error now.

Michael
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now