New Exchange 2019 Server, Transport Service won't start.

Copper Contributor

I am attempting to install a new 2019 On-Premise Exchange Server, but the transport service will not start.

This is installed on new VM with Server 2022 Datacenter, all updates. I went through all the prerequisites, and set it to use the same GPO used by the current Exchange 2016 server. I then ran the HealthCheck Powershell script and resolved all known issues.

 

After installation, the Transport Service would not start. I followed every recommended fix I could find, finally ended up uninstalling the server.

 

I then downloaded the newest CU ISO and attempted to reinstall it again, same thing, transport service fails upon startup.

 

Every time I try to start it, I get these 4 errors in the event log:

 

Event 12001, MSExchangeTransport
Failed to flush Kerberos ticket cache in Initialize: System.ComponentModel.Win32Exception (0x80004005): The parameter is incorrect
at Microsoft.Exchange.Security.SafeLsaUntrustedHandle.PurgeTicketCache(Int32 packageId)
at Microsoft.Exchange.Security.Kerberos.FlushTicketCache()
at Microsoft.Exchange.Transport.TransportService.TransportService.Initialize()
NativeErrorCode = 87

 

Event 4999, MSExchange Common
Watson report about to be sent for process id: 9260, with parameters: E12IIS, c-RTL-AMD64, 15.02.1258.028, MSExchangeTransport, M.Exchange.Net, M.E.S.SafeLsaUntrustedHandle.PurgeTicketCache, S.ComponentModel.Win32Exception, 7a7a-dumptidset, 15.02.1258.028.
ErrorReportingEnabled: True

 

Event 7009, Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Transport service to connect.

Event 7000, Service Control Manager
The Microsoft Exchange Transport service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

 

 

There is also this error that may or may not be related, comes up on a regular basis:

 

Event 1309, ASP.NET 4.0.30319.0
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/1/2023 11:38:41 AM
Event time (UTC): 12/1/2023 4:38:41 PM
Event ID: 71b044f6816744b8b49676b3ceed5a40
Event sequence: 2
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/3/ROOT/owa-1183-133459223026795567
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
Machine name: MAIL2

Process information:
Process ID: 2384
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM

Exception information:
Exception type: HttpException
Exception message: The parameter is incorrect
at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

The parameter is incorrect
at Microsoft.Exchange.Security.SafeLsaUntrustedHandle.PurgeTicketCache(Int32 packageId)
at Microsoft.Exchange.Security.Kerberos.FlushTicketCache()
at Microsoft.Exchange.Clients.Owa2.Server.Core.BaseApplication.ExecuteApplicationStart(Object sender, EventArgs e)
at Microsoft.Exchange.Clients.Owa2.Server.Core.Global.Application_Start(Object sender, EventArgs e)

Request information:
Request URL: https://localhost:444/owa/exhealth.check
Request path: /owa/exhealth.check
User host address: 127.0.0.1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM

Thread information:
Thread ID: 66
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

Anyone have any ideas on how to resolve this?

 

0 Replies