Today we are announcing the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013. These releases include fixes to customer reported issues and updated functionality. Exc...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Team,
I was exploring the ExchangeSetup.log file to find out why a particular server was taking a long time to be fully installed. I ended finding that the setup desperately tries to start and wait for the NaSvc service... 36 times with a timeout of 25 seconds. So in the end, 15 minutes wasted until moving forward.
NaSvc is the Network Connectivity Assistant, and can't be started manually (despite having a startup type of Manual). So, is the wait worth it ?
Here's an example:
[10-16-2016 21:29:51.0289] [2] Will wait '25000' milliseconds for the service 'NcaSvc' to reach status 'Running'.
[10-16-2016 21:30:16.0452] [2] Service 'NcaSvc' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[10-16-2016 21:30:16.0452] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
(that, multiple times, e.g. a total of 36 times.
[10-16-2016 21:44:58.0609] [2] Service 'NcaSvc' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[10-16-2016 21:44:58.0609] [2] [WARNING] Service 'NcaSvc' failed to reach status 'Running' on this server.
[10-16-2016 21:44:58.0609] [2] Ending processing start-setupservice
- Seeing the same thing here on CU4 w/ Server 2016. After 15 minutes of checking it moved on.
- Sorry, typo on the service's name it's NcaSvc, not NaSvc.
And issue seems to happen with Exchange Server 2016 on Windows Server 2016. Didn't find the same traces with Exchange Server 2016 on Windows Server 2012 R2.