Cleaning up errors after installation of Exchange 2010 in a co-existing environment setup.
At this point the new Exchange 2010 Server is peacefully co-existing with the Exchange 2003 Server. I have not changed routing or anything.
Referring back to Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 2, I ran into a few errors during my 2 week testing period. These errors appeared every 15 minutes in the event log and were always in the same group of 3.
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGY (PID=1416). The site monitor API was unable to verify the site name for this Exchange computer – Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.
——————————————————
Event ID: 2604
Source: MSExchange ADAccess
After hours of scouring the web I found the problem revolved around the network bindings on the new Exchange 2010 Server. The server itself had 4 NIC cards with only a single card in use. This caused problems when it was trying to retrieve information from servers.
- Log on to the computer by using an account that has Administrator rights.
- Click Start, click Run, type ncpa.cpl, and then click OK.
- In the Network Connections dialog box, press ALT+N to display the Advanced menu.
- Click Advanced Settings.
- In the Connections box, click the active network connection, and then click the arrow to move the connection to the top of the list.
- Click OK.
- Restart the Microsoft Exchange Active Directory Topology service. When you restart this service, the following dependent services must also be stopped and restarted:
- Microsoft Exchange Transport Log Search
- Microsoft Exchange Transport Log
- Microsoft Exchange Service Host
- Microsoft Exchange Search Indexer
- Microsoft Exchange Replication Service
- Microsoft Exchange Mail Submission
- Microsoft Exchange Mailbox Assistants
- Microsoft Exchange File Distribution
- Microsoft Exchange EdgeSync
- Microsoft Exchange Anti-spam Update
- Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 2
- Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 1
Did you find this solution helpful?
What other odd errors have you run across?
Pingback: The Whiteboard | Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 5
Pingback: The Whiteboard | Exchange 2003 to Exchange 2010: The “Swing” Migration – Part 4