- Application pool suffered fatal communication error windows process activation service
- Asked by:
- Question
- Application pool suffered fatal communication error windows process activation service
- Вопрос
- Ответы
- Все ответы
- Application pool suffered fatal communication error windows process activation service
- Вопрос
- Ответы
- Все ответы
Application pool suffered fatal communication error windows process activation service
Asked by:
Question
We recently started using AppFabric 1.1 and now want to host a WCF service in IIS/WAS with a MSMQ endpoint.
Configuration and code appear to be correct as the same bits and configuration sometimes work, sometimes doesn’t. When it doesn’t work we get this warning in the EventLog:
The data contains the error 0x80070218 which means ERROR_PIPE_LISTENING.
I’ve seen on another thread that may be an issue with the fact that AppFabric services have no dependencies on WPA service, which could cause some problems. I tried restarting the services in order but it doesn’t help.
A bit of the background scenario.
— Private queue in localhost/private/Kaplan.Our.Web.Site.Name/ServiceName.svc
— WCF service configured with the correct address (net.msmq://localhost/private/Kaplan.Our.Web.Site.Name/ServiceName.svc) and the default binding configuration except exactlyOnce which is set to false for now.
— Service activated without the .svc file (File Less Activation)
Note: All our code and configuration appears correct. Hitting http://ourwebsite.local/ServiceName.svc in the browser displays the default WCF page and activates the service, making it process existing messages in the queue. So this leads me to believe that is something on Microsoft side.
Does anyone have any idea of what this might be, or at least how to gather more information about the error (log, tracing, etc)? (Note, enabling WCF tracing in the server doesn’t help, because the service is not activated when the apppool starts).
Application pool suffered fatal communication error windows process activation service
Вопрос
Некоторое время назад я провел миграцию c Exchange 2010 на 2016cu11 (windows 2016). Всё работало штатно, однако после установки обновления для Windows 2016 KB4493470 вместе с обновлением для Exchange KB4487563 в системных логах с периодичностью в несколько минут стала появляться ошибка:
A process serving application pool ‘MSExchangeServicesAppPool’ suffered a fatal communication error with the Windows Process Activation Service. The process id was ‘ разные числа >’. The data field contains the error number.
1. Рвутся, восстанавливаются соединения с Outlook на всех Mac,
2. В Outlook не отображаются сведения о доступности переговорных комнат (долго обновляет, после чего пишет, что не удается связаться с сервером), через owa доступность показывает без проблем.
3. Один пользователь заметил, что через owa письма в ящике не показывает вообще никакие, в Outlook же все работает.
Удаление обновления KB4487563 ничего не изменило. Сегодня ночью буду откатывать обновление для Windows.
Буду признателен за любую помощь.
Ответы
Сделал все по инструкции:
In fact, I would say that this process not only solved my issue but also got rid of a majority of the little warnings and errors on both my Exchange 2013 and Lync 2013 servers. they seem to enjoy life more when they can exchange tokens directly with each other.
For a majority of you, you will have the certificate in place, and setting up the integration will be super easy. If by chance, you do not have the cert, then this is your easy 2 min fix.
1. New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName «cn= Microsoft Exchange Server Auth Certificate» -DomainName «*.yourdomain.com» -FriendlyName «Microsoft Exchange Server Auth Certificate» -Services smtp
Do not accept to replace the SMTP certificate when prompted
2. Note the thumbprint of the new certificate. Let us assume it is 7A39541F8DF58D4821967DD8F899B27410F7C081
4. Set-AuthConfig -NewCertificateThumbprint 7A39541F8DF58D4821967DD8F899B27410F7C081 –NewCertificateEffectiveDate $a
Accept to continue despite the fact that the certificate effective date is not 48 hours into the future
5. Set-AuthConfig –PublishCertificate
6. Make sure to remove any potential reference to the previous certificate (which might not exist anymore) by doing Set-AuthConfig -ClearPreviousCertificate.
После всего этого сделал iisreset /stop /start и, на всякий случай, shutdown -r -t 0
Возможно заработало. Жду завтра.
Все ответы
1. Сделайте Recycle Pool если ещё не делали.
Установил дебаггер, в процессе разбирательства обратил внимание на ошибку в Application от ASP.NET 4.0.30319.0
An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/2/ROOT/EWS
Process ID: 28880
Exception: Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException
Message: Missing signing certificate.
StackTrace: at Microsoft.Exchange.Security.OAuth.V1ProfileLocalTokenIssuer..ctor(ILocalConfiguration localConfiguration)
at Microsoft.Exchange.Security.OAuth.V1ProfileOAuthTokenBuilder..ctor(ILocalConfiguration localConfiguration, ITokenIssuerHelper tokenIssuerHelper, OAuthSnapshot oAuthSnapshot)
at Microsoft.Exchange.Security.OAuth.OAuthExchangeToExchangeTokenFactory..ctor()
at Microsoft.Exchange.Services.Core.GetClientAccessToken.<>c. b__49_0()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at Microsoft.Exchange.Services.Core.GetClientAccessToken.GetExchangeUserTokenForConnectors(ADUser user)
at Microsoft.Exchange.Services.Core.GetClientAccessToken.CreateConnectorsToken(ADUser user)
at Microsoft.Exchange.Services.Core.GetClientAccessToken.ExecuteGetClientAccessToken()
at Microsoft.Exchange.Services.Core.GetClientAccessToken.Execute()
at Microsoft.Exchange.Services.Core.ExceptionHandler`1.Execute(IRequestDetailsLogger logger, CreateServiceResult createServiceResult, Int32 index, ExecutionOption executionOption)
at Microsoft.Exchange.Services.Core.BaseStepServiceCommand`3.InternalExecuteStep(Boolean& isBatchStopResponse)
at Microsoft.Exchange.Services.Core.ServiceCommandBase`1. b__82_0()
at Microsoft.Exchange.Services.Core.ServiceCommandBase`1.<>c__DisplayClass88_0. b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate)
at Microsoft.Exchange.Services.Core.ServiceDiagnostics.SendWatsonReportOnUnhandledException(ICallContext callContext, Action methodDelegate)
at Microsoft.Exchange.Services.Core.ServiceCommandBase`1.ExecuteHelper(Func`1 action)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1.<>c__DisplayClass11_0. b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.SendWatsonReportOnGrayException(Action callback, Action exceptionHandlerCallback, Boolean isGrayExceptionTaskFailure)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1.ExecuteHelper(Func`1 multiStepAction)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1. b__7_0()
at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase`1.TrackLatency[TResult](Enum latencyMetadata, Func`1 method)
at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase`1.TrackLatency[TResult](Enum latencyMetadata, Func`1 method, Double& latencyValue)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1.InternalExecute(TimeSpan queueAndDelay, TimeSpan totalTime)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.<>c__DisplayClass33_0. b__0()
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.LocalTimedCall(Action action)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.ExecuteWithinCallContext(Action action)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.Execute(TimeSpan queueAndDelayTime, TimeSpan totalTime)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.ExecuteLoop(Boolean synchronously)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Эта ошибка происходит в ту же секунду, в которую валится msexchangeserviceapppool. В сертификатах всё в порядке, по крайней мере через GUI. Развернул рядом еще один чистый эксчейндж cu12 на Win 16 cu5, думаю, перекидывать на него концы, если не придумаю, как пролечить правильно asp и сертификаты — надеюсь, я в правильную сторону копаю.
Application pool suffered fatal communication error windows process activation service
Вопрос
Некоторое время назад я провел миграцию c Exchange 2010 на 2016cu11 (windows 2016). Всё работало штатно, однако после установки обновления для Windows 2016 KB4493470 вместе с обновлением для Exchange KB4487563 в системных логах с периодичностью в несколько минут стала появляться ошибка:
A process serving application pool ‘MSExchangeServicesAppPool’ suffered a fatal communication error with the Windows Process Activation Service. The process id was ‘ разные числа >’. The data field contains the error number.
1. Рвутся, восстанавливаются соединения с Outlook на всех Mac,
2. В Outlook не отображаются сведения о доступности переговорных комнат (долго обновляет, после чего пишет, что не удается связаться с сервером), через owa доступность показывает без проблем.
3. Один пользователь заметил, что через owa письма в ящике не показывает вообще никакие, в Outlook же все работает.
Удаление обновления KB4487563 ничего не изменило. Сегодня ночью буду откатывать обновление для Windows.
Буду признателен за любую помощь.
Ответы
Сделал все по инструкции:
In fact, I would say that this process not only solved my issue but also got rid of a majority of the little warnings and errors on both my Exchange 2013 and Lync 2013 servers. they seem to enjoy life more when they can exchange tokens directly with each other.
For a majority of you, you will have the certificate in place, and setting up the integration will be super easy. If by chance, you do not have the cert, then this is your easy 2 min fix.
1. New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName «cn= Microsoft Exchange Server Auth Certificate» -DomainName «*.yourdomain.com» -FriendlyName «Microsoft Exchange Server Auth Certificate» -Services smtp
Do not accept to replace the SMTP certificate when prompted
2. Note the thumbprint of the new certificate. Let us assume it is 7A39541F8DF58D4821967DD8F899B27410F7C081
4. Set-AuthConfig -NewCertificateThumbprint 7A39541F8DF58D4821967DD8F899B27410F7C081 –NewCertificateEffectiveDate $a
Accept to continue despite the fact that the certificate effective date is not 48 hours into the future
5. Set-AuthConfig –PublishCertificate
6. Make sure to remove any potential reference to the previous certificate (which might not exist anymore) by doing Set-AuthConfig -ClearPreviousCertificate.
После всего этого сделал iisreset /stop /start и, на всякий случай, shutdown -r -t 0
Возможно заработало. Жду завтра.
Все ответы
1. Сделайте Recycle Pool если ещё не делали.
Установил дебаггер, в процессе разбирательства обратил внимание на ошибку в Application от ASP.NET 4.0.30319.0
An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/2/ROOT/EWS
Process ID: 28880
Exception: Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException
Message: Missing signing certificate.
StackTrace: at Microsoft.Exchange.Security.OAuth.V1ProfileLocalTokenIssuer..ctor(ILocalConfiguration localConfiguration)
at Microsoft.Exchange.Security.OAuth.V1ProfileOAuthTokenBuilder..ctor(ILocalConfiguration localConfiguration, ITokenIssuerHelper tokenIssuerHelper, OAuthSnapshot oAuthSnapshot)
at Microsoft.Exchange.Security.OAuth.OAuthExchangeToExchangeTokenFactory..ctor()
at Microsoft.Exchange.Services.Core.GetClientAccessToken.<>c. b__49_0()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at Microsoft.Exchange.Services.Core.GetClientAccessToken.GetExchangeUserTokenForConnectors(ADUser user)
at Microsoft.Exchange.Services.Core.GetClientAccessToken.CreateConnectorsToken(ADUser user)
at Microsoft.Exchange.Services.Core.GetClientAccessToken.ExecuteGetClientAccessToken()
at Microsoft.Exchange.Services.Core.GetClientAccessToken.Execute()
at Microsoft.Exchange.Services.Core.ExceptionHandler`1.Execute(IRequestDetailsLogger logger, CreateServiceResult createServiceResult, Int32 index, ExecutionOption executionOption)
at Microsoft.Exchange.Services.Core.BaseStepServiceCommand`3.InternalExecuteStep(Boolean& isBatchStopResponse)
at Microsoft.Exchange.Services.Core.ServiceCommandBase`1. b__82_0()
at Microsoft.Exchange.Services.Core.ServiceCommandBase`1.<>c__DisplayClass88_0. b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate)
at Microsoft.Exchange.Services.Core.ServiceDiagnostics.SendWatsonReportOnUnhandledException(ICallContext callContext, Action methodDelegate)
at Microsoft.Exchange.Services.Core.ServiceCommandBase`1.ExecuteHelper(Func`1 action)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1.<>c__DisplayClass11_0. b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.SendWatsonReportOnGrayException(Action callback, Action exceptionHandlerCallback, Boolean isGrayExceptionTaskFailure)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1.ExecuteHelper(Func`1 multiStepAction)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1. b__7_0()
at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase`1.TrackLatency[TResult](Enum latencyMetadata, Func`1 method)
at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase`1.TrackLatency[TResult](Enum latencyMetadata, Func`1 method, Double& latencyValue)
at Microsoft.Exchange.Services.Core.Types.ServiceTask`1.InternalExecute(TimeSpan queueAndDelay, TimeSpan totalTime)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.<>c__DisplayClass33_0. b__0()
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.LocalTimedCall(Action action)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.ExecuteWithinCallContext(Action action)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.Execute(TimeSpan queueAndDelayTime, TimeSpan totalTime)
at Microsoft.Exchange.Services.Core.Types.BaseServiceTask`1.ExecuteLoop(Boolean synchronously)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Эта ошибка происходит в ту же секунду, в которую валится msexchangeserviceapppool. В сертификатах всё в порядке, по крайней мере через GUI. Развернул рядом еще один чистый эксчейндж cu12 на Win 16 cu5, думаю, перекидывать на него концы, если не придумаю, как пролечить правильно asp и сертификаты — надеюсь, я в правильную сторону копаю.
