Mailbox Server Role Services not running: MSExchangeDelivery

Question

Running Exchange 2013 CU7 on Server 2012R2.
Ive been working on this project on and off for the last few months, as I am the only IT guy, and a new office construction at my company has had me running cable, moving offices, workstations, and phones.
This install of Exchange was working fine up until about a week ago. When I came back to finish its setup, I noticed that I was not able to send email internally anymore. Connecting to OWA says the message was sent, but it never arrives. After some more
investigation, it turns out the MSExchageDelivery service will not run.
Checking on this service, it indicates that it is starting/stopping, but never getting to the running stage. I have tried everything that I can think of, including uninstalling and re-installing the software. I have scoured the internet looking for solutions,
but not finding one that will take care of the problem.
Looking in the event viewer under Windows Logs -> Application I do see alot of information about MSExchangeTransportDelivery. Seems to be looping through a set of events....
1. Error MSExchangeTransportDelivery Failed to start listening (Error: 10048). Binding: 0.0.0.0:475
2. Error MSExchangeTransportDelivery This address is already in use. Binding: 0.0.0.0:475.
3. Error MSExchangeTransportDelivery Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsfot Exchage is [%2]. Make sure EdgeSync is running properly.
4. Information MSExchangeTransportDelivery The service will be stopped. Reason TCP/IP socket error. The service will stop.
5. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.TransportServerConfiguration has successfully completed.
6. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Data.Directory.SystemConfiguration.MailboxTransportServer has successfully completed.
7. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.X400AuthoritativeDomainTable has successfully completed.
8.Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.AcceptedDomainTable has successfully completed.
9.Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
10. Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.RemoteDomainTable has successfully completed.
11.Information MSExchangeTransportDelivery A configuration update for Microsoft.Exchange.Transport.TransportSettingsConfiguration has successfully completed.
12.Information MSExchangeTransportDelivery We are doing a full mailbox database reload as part of routing tables loading due to: First read.
Not sure where to go from here... any and all help is appreciated.

Answer 1

You're getting a tcp socket error and This address is already in use. Binding: 0.0.0.0:475.
Are you sure port 475 is not being used for some other service? Go to services and check if the
MSExchangeTransportDelivery is
currently stopped. If it is, open cmd and type netstat -ano and see if port 475 is showing up. If the MSExchangeTransportDelivery
is stopped it should not show up, if it is then it's being binded somewhere else and prob causing a conflict.
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Thank you for your help. MSExchangeTransportDelivery was stopped. When I ran the netstat command, it shows:
TCP    0.0.0.0:475            0.0.0.0:0              LISTENING       1600
TCP    127.0.0.1:475          127.0.0.1:35056        ESTABLISHED     1600
  TCP    127.0.0.1:475          127.0.0.1:35231        ESTABLISHED     1600
  TCP    127.0.0.1:475          127.0.0.1:35386        ESTABLISHED     1600
  TCP    127.0.0.1:475          127.0.0.1:35559        ESTABLISHED     1600
  TCP    127.0.0.1:475          127.0.0.1:35657        ESTABLISHED     1600
 UDP    0.0.0.0:475            *:*                                   
1600
So we can see that 475 is indeed in use. I followed this up with Process Explorer to find out what process had PID 1600. Turns out that a security dongle we use for network licensing is using that port. I will be moving the dongle to another server, and
will follow up here when I have results.