This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 63%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEM%3C/text%3E%3C/svg%3E)
Hello,
Yesterday I have installed Cumliative Update "15.1.2507.32" on our Exchange Server 2016. After the update we couldn't send and receive emails. I checked the Event Logs and found this error logs:
And Microsoft Exchange Transport Service couldn't start.
I have noticed that Port 2525 is used by "microsoft.exchange.directory.topologyservice". After stopping it, MS Exchange Service could start and we can send and recive emails. But restarting Windows, "microsoft.exchange.directory.topologyservice" takes Port 2525 again.
Could you please help to solve this issue? Hope to hear from you very soon.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @Elvin Mammadov ,
And Microsoft Exchange Transport Service couldn't start.
Is there any error message when you attempt to manually start Microsoft Exchange Transport Service?
Is MSExchangeADTopology (microsoft.exchange.directory.topologyservice) running properly?
By the way, did you find out Port 2525 was used by MSExchangeADTopology using the powershell command below?
Get-Process -Id (Get-NetTCPConnection -LocalPort 2525).OwningProcess
Could you run the following command to check the receive connectors and share the output here? Be sure to remove all personal information involved:
Get-ReceiveConnector | ft Identity,Enabled,TransportRole,Bindings
I run the given comamnds and got the following results. After the reboot, now Port 2525 is used by other service. It happened after the last August update for Exchange Server 2016.
When I start the Transport service, it gives the following error message.
In the Event logs, I have found also this error message:
Watson report about to be sent for process id: 12388, with parameters: E12IIS, c-RTL-AMD64, 15.01.2507.032, MSExchangeTransport, M.Exchange.Net, M.E.P.WorkerProcessManager.HandleWorkerExited, M.E.ProcessManager.WorkerProcessRequestedAbnormalTerminationException, 5e2b-dumptidset, 15.01.2507.032.
ErrorReportingEnabled: False
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 70%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
Any news on this - i recently had this on EX2016(Windows Server 2016) fully patched.
Is there a fix to prevent this behaviour?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 69%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDX%3C/text%3E%3C/svg%3E)
The same issue happened on my exchange 2016 Version 15.1 (Build 2308.8) from few days ago.
"Failed to start listening (Error: 10048). Binding: 0.0.0.0:2525."
The transport service needs this port for hub transport.
Recently no hotfix was installed.
Hi Yuki Sun,
Yesterday after reboot, Port 2525 was used by another service, I have found and stopped that service and then i could start Transport service, then I restarted the Windows again, but this time it didn't happen. it happens after 1-2 reboots.
We have installed Exchange SU Aug V2 directly, V1 was installed, because it was hidden in WSUS Server. I have checked that Microsoft says, if SU Aug V2 is already installed, there is no need to install SU Aug V1. I am not sure, if we needed to install SU Aug V1.
I run the Healthchecker script, everything is green, there is no errors and vulnerabilities.
But I don't know why after some reboots, Port 2525 is used by another service, it happended after SU Aug V2.
Hi @Elvin Mammadov ,
From the screenshot, seems like everything is back to normal now, including the Transport service, right?
I have checked that Microsoft says, if SU Aug V2 is already installed, there is no need to install SU Aug V1. I am not sure, if we needed to install SU Aug V1.
No need to install SU Aug V1 in this case. Especially you have run the Healthchecker script and everything is green : )
As regards to your concern about the port 2525, I've tried searching a lot earlier but didn't find similar reports or official document stating if this is normal or not. But given current situation, if everything is working properly now, I assume you can just ignore this temporarily.
Hi @Elvin Mammadov ,
After the reboot, now Port 2525 is used by other service.
I tried running the aforementioned command in my Exchange 2019 environment and Port 2525 is used by "EdgeTransport":
Aside from the Exchange Transport Service, have you checked the status of the other Exchange services? Can you also run Test-ServiceHealth to check the result?
It happened after the last August update for Exchange Server 2016.
Which version of the Aug SU did you install, V1 or V2? You can run the Exchange Health Checker to see if any additional steps might be needed in your current setup. More information about the Aug SU, you can take a look at the following blog:
Re-release of August 2023 Exchange Server Security Update packages
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.