Cleaning up errors MSExchange ADAccess Event ID: 2106 and MSExchangeTransport Event ID:

  • Thread starter badincite
  • Start date Views 4,082
B

badincite

Couple of exchange errors i am trying to clear up

This is on server 2008 r2 and exchange 2010

Log Name: Application Source: MSExchange ADAccess Date: 6/25/2010 3:17:01 PM Event ID: 2106 Task Category: Topology Level: Warning Keywords: Classic User: N/A Computer: PER510.CCI.WORK Description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2588). Exchange Active Directory Provider failed to obtain DNS records for forest DC=CCI,DC=WORK. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight). Event Xml: <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event" > <System> <Provider Name=" MSExchange ADAccess" /> <EventID Qualifiers=" 32772" >2106</EventID> <Level>3</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime=" 2010-06-25T19:17:01.000000000Z" /> <EventRecordID>31666</EventRecordID> <Channel>Application</Channel> <Computer>PER510.CCI.WORK</Computer> <Security /> </System> <EventData> <Data>MSEXCHANGEADTOPOLOGYSERVICE.EXE</Data> <Data>2588</Data> <Data>DC=CCI,DC=WORK</Data> <Data>0</Data> <Data>100</Data> </EventData> </Event>

Log Name: Application Source: MSExchangeTransport Date: 6/24/2010 5:17:22 PM Event ID: 12014 Task Category: TransportService Level: Error Keywords: Classic User: N/A Computer: PER510.CCI.WORK Description: Microsoft Exchange could not find a certificate that contains the domain name mail.mydomainhere.com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector internet mail routing to mail.chesapeakecontrols.com with a FQDN parameter of mail.chesapeakecontrols.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key. Event Xml: <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event" > <System> <Provider Name=" MSExchangeTransport" /> <EventID Qualifiers=" 49156" >12014</EventID> <Level>2</Level> <Task>12</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime=" 2010-06-24T21:17:22.000000000Z" /> <EventRecordID>31395</EventRecordID> <Channel>Application</Channel> <Computer>PER510.CCI.WORK</Computer> <Security /> </System> <EventData> <Data>mail.chesapeakecontrols.com</Data> <Data>internet mail routing to mail.chesapeakecontrols.com</Data> </EventData> </Event>
 
B

busbar

please verify that DNS servers configured in the Exchange server points to internal DNS server (DC) and that those are up and running, also make sure to run dcdiag /fix on the DCsRegards, Mahmoud Magdy Watch Arabic Level 300 Videos about Exchange 2010 here: http://vimeo.com/user3271816 Read pretty advanced Exchange stuff I and other MVPs post here: http://www.enowconsulting.com/ese/blog.asp Or follow my blog: http://busbar.blogspot.com or our corp blog: http://ingazat.wordpress.com and if you Liked my post please mark it as helpful and accept it as an asnwer
 
B

badincite

Ran dcdiag there were no errors. I believe this was because I disabled ipv6 on one of my nics. Seemed to go away at least for now
 

Top