Event IDs 16025 and 205

Hi

A newly installed Exchange 2013 Server (Mailbox and Client Access roles) shows every 5 minutes the event id's 16025 and 205 in the eventlog.

Both events are shown twice at the same time. First 205 then 16025 and again 205 and 16025.

Level: Error
Id 205 - Source: MSExchange Common
Id 16025 - Source: MSExchangeFrontEndTransport

Both have exactly the same description:
No DNS servers could be retrieved from network adapter 0957d69c-9b06-4b72-aa6b-ac825435b485. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results

Get-NetworkConnectionInfo shows the following results:
RunspaceId  : e854435f-ffbe-4ccb-81d9-7e729284e26a
Name        : Microsoft Hyper-V Network Adapter
DnsServers  : {10.10.32.34, 10.10.32.42}
IPAddresses : {10.10.32.45, 10.10.32.44, fe80::9cb9:ad68:c7cc:2052}
AdapterGuid : 0957d69c-9b06-4b72-aa6b-ac825435b485
MacAddress  : 00:1D:D8:B7:1E:2A
Identity    : 0957d69c-9b06-4b72-aa6b-ac825435b485
IsValid     : True
ObjectState : Unchanged

Mailflow is working, I would like to get rid of these error events.

Any suggestions?

Regards
Peter



  • Edited by PeterN22 Friday, March 27, 2015 7:43 AM
March 27th, 2015 7:40am

To resolve these errors, try one of the following methods:

Open the Exchange Management Console locally on the Hub Transport server or Edge Transport server. Configure the internal DNS lookups to use all available network adapters, or a specific adapter that exists on the Hub Transport server or Edge Transport server.

or

Open the Exchange Management Shell. Run the Get-NetworkConnectionInfo cmdlet locally on the Hub Transport server or Edge Transport server. Note the GUID of the network adapters. Use the GUID of the desired network adapter as the value for the InternalDNSAdapterGUID parameter on the Set-TransportServer cmdlet. If you want to use the DNS settings of all available network adapters, enter a GUID of 00000000-0000-0000-0000-000000000000.

  • Edited by Blake Jason Friday, March 27, 2015 10:44 AM
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 10:42am

Hi,

According to your description, I understand that Exchange server experience an circulating error(Event ID 205, 16025), however mail flow works fine.
If I misunderstand your concern, please do not hesitate to let me know.

Basic on Event ID, I find an Microsoft article with a deep analysis. For your reference:
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=205&EvtSrc=MSExchange+Common&LCID=1033
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=16025&EvtSrc=MSExchangeTransport&LCID=1033

For your question, please try below steps for troubleshooting:
Step1:
  1. Go to the Registry HKLM\System\Currentcontrolset\services\Tcpip\Adapters.
  2. The GUID we have in 16025 would be seen missing from here.
  3. If the GUID is present DO NOT DELETE it from the registry.
Step2:
  1. Login EAC and switch to Servers.
  2. Select a mailbox server to edit, double check the internal and external DNS configuration in DNS lookups.
  3. Restart Microsoft Exchange Transport service.

Thanks

March 30th, 2015 5:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics