This guide provides a step-by-step solution to resolve the Fatal Communication Error with the Windows Process Activation Service. This error typically occurs when there is an issue with the communication between IIS (Internet Information Services) and WAS (Windows Process Activation Service), which may lead to application pools shutting down or web applications becoming unresponsive.
Table of Contents
- Prerequisites
- Identify the root cause
- Step-by-step solution
- FAQs
- Related links
Prerequisites
Before we begin, ensure that you have the following:
- Administrative access to the server experiencing the issue
- Basic understanding of IIS
Identify the root cause
To identify the root cause of the Fatal Communication Error with the Windows Process Activation Service, follow these steps:
- Open Event Viewer on the server
- Navigate to Application and Services Logs > Microsoft > Windows > Application Server-Applications
- Look for any error events with the Source:
Microsoft-Windows-WAS - Review the error message and note any specific error codes or details
This information will help you determine the root cause of the issue and select the appropriate solution.
Step-by-step solution
Once you have identified the root cause, follow the appropriate steps below to resolve the issue.
Step 1: Restart WAS and IIS services
- Open the Services console (
services.msc) on the server - Locate the Windows Process Activation Service and World Wide Web Publishing Service
- Restart both services by right-clicking each service and selecting Restart
Step 2: Verify proper configuration
- Open IIS Manager on the server
- Click on the server node in the left pane
- Double-click on the Configuration Editor feature
- In the Section drop-down, navigate to system.applicationHost/applicationPools
- Verify that the configuration is correct and matches the expected settings for your environment
- If changes are required, edit the settings and click Apply in the top-right corner
Step 3: Repair .NET Framework
If the issue persists, there may be a problem with the .NET Framework installation. Follow these steps to repair the installation:
- Download the .NET Framework Repair Tool
- Run the tool with administrative privileges
- Follow the on-screen prompts to repair the .NET Framework installation
FAQs
1. What is the Windows Process Activation Service (WAS)?
WAS is a component of IIS that manages the application pool and worker processes for web applications. It is responsible for starting, stopping, and recycling worker processes to ensure optimal performance and resource usage.
2. What causes the Fatal Communication Error with WAS?
The error can be caused by various issues, including incorrect configuration settings, problems with the .NET Framework installation, or issues with the communication between IIS and WAS.
3. How do I check the status of WAS on my server?
You can check the status of WAS by opening the Services console (services.msc) and locating the Windows Process Activation Service. The current status will be displayed in the Status column.
4. Can I disable WAS if I am not using IIS?
If you are not using IIS or any applications that rely on WAS, you can disable the service. However, it is recommended to keep the service enabled and running to avoid potential issues with future applications or updates.
5. How can I monitor WAS events and errors?
You can monitor WAS events and errors using the Event Viewer. Navigate to Application and Services Logs > Microsoft > Windows > Application Server-Applications to view WAS logs.
- IIS Official Website
- .NET Framework Repair Tool
- Microsoft Docs: Troubleshoot IIS
I’m seeing in the CF logs leading up to the crash:
Jun 04, 2014 11:11:31 AM org.apache.coyote.ajp.AjpProcessor getRealPathFromServer
SEVERE: Error in getRealPathFromConn
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.apache.coyote.ajp.AjpProcessor.getRealPathFromServer(AjpProcessor.java:402)
at org.apache.coyote.ajp.AbstractAjpProcessor.getRealPath(AbstractAjpProcessor.java:1276)
at org.apache.naming.resources.FileDirContext.doGetRealPath(FileDirContext.java:202)
at org.apache.naming.resources.BaseDirContext.getRealPath(BaseDirContext.java:424)
at org.apache.catalina.core.StandardContext.getRealPath(StandardContext.java:4660)
at org.apache.catalina.core.ApplicationContext.getRealPath(ApplicationContext.java:432)
at org.apache.catalina.core.ApplicationContextFacade.getRealPath(ApplicationContextFacade.java:333)
at coldfusion.runtime.ServletContextWrapper.doGetRealPath(ServletContextWrapper.java:184)
at coldfusion.runtime.ServletContextWrapper._doGetRealPath(ServletContextWrapper.java:116)
at coldfusion.runtime.ServletContextWrapper.getRealPath(ServletContextWrapper.java:98)
at coldfusion.filter.FusionContext.getRealPath(FusionContext.java:999)
at coldfusion.filter.FusionContext.getRealPath(FusionContext.java:937)
at coldfusion.runtime.RuntimeServiceImpl.resolveTemplatePath(RuntimeServiceImpl.java:866)
at coldfusion.tagext.lang.IncludeTag.setTemplate(IncludeTag.java:420)
at cfApplication2ecfc1835967654.runPage(C:\Data\http\domain\apps\Application.cfc:3)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:246)
at coldfusion.filter.SilentFilter.invoke(SilentFilter.java:47)
at coldfusion.runtime.TemplateProxyFactory.resolveComponentHelper(TemplateProxyFactory.java:538)
at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:248)
at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:159)
at coldfusion.runtime.TemplateProxyFactory.resolveFile(TemplateProxyFactory.java:120)
at coldfusion.cfc.CFCProxy.<init>(CFCProxy.java:138)
at coldfusion.cfc.CFCProxy.<init>(CFCProxy.java:84)
at coldfusion.runtime.AppEventInvoker.<init>(AppEventInvoker.java:64)
at coldfusion.filter.PathFilter.resolveApplicationScope(PathFilter.java:195)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:124)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:94)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:58)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)
at coldfusion.CfmServlet.service(CfmServlet.java:219)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.intergral.fusionreactor.j2ee.filterchain.WrappedFilterChain.doFilter(WrappedFilterChain.java:97)
at com.intergral.fusionreactor.j2ee.filter.FusionReactorRequestHandler.doNext(FusionReactorRequestHandler.java:472)
at com.intergral.fusionreactor.j2ee.filter.FusionReactorRequestHandler.doHttpServletRequest(FusionReactorRequestHandler.java:312)
at com.intergral.fusionreactor.j2ee.filter.FusionReactorRequestHandler.doFusionRequest(FusionReactorRequestHandler.java:192)
at com.intergral.fusionreactor.j2ee.filter.FusionReactorRequestHandler.handle(FusionReactorRequestHandler.java:507)
at com.intergral.fusionreactor.j2ee.filter.FusionReactorCoreFilter.doFilter(FusionReactorCoreFilter.java:36)
at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.intergral.fusionreactor.j2ee.filterchain.WrappedFilterChain.doFilter(WrappedFilterChain.java:79)
at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.intergral.fusionreactor.agent.filter.FusionReactorStaticFilter.doFilter(FusionReactorStaticFilter.java:53)
at com.intergral.fusionreactor.agent.pointcuts.NewFilterChainPointCut$1.invoke(NewFilterChainPointCut.java:41)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:422)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:198)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Dear All,
I have configured UNC based web farm for IIS 7.5 sites on multiple server for one of major project and cross checked by browsing on each server. As the first page of site is .html file website god browsed and when tried to browse .aspx page got below error
Tried below option to resolve the issue
Dropped and re-created App Pool ( as in some cases it works ) but in this scenario it didn’t worked so checked app pool running in which identity and authentication for website it was running under NETWORK SERVICE
So tried by giving permissions to NETWORK SERVICE to Shared folder permissions and the website started working and problem gor resolved.
Thanks
Prashant Deshpande
-
Технические форумы
-
Microsoft
-
Exchange Server
-
Автор темы
Автор темыgasi
-
Дата начала
Дата начала -
-
Теги
Теги -
event id 5011
exchange 2019
was
-
-
-
#1
Всем привет!
Периодически сервера exh выпадают в ошибку — смотрите ниже.
После ошибки в течении пары минут сервера возобнавляют работу.
Конкретного решения для этой проблемы не нашел — как вариант настроить перезапуск проблемного пула раз в день в незагруженное время.
Кто-нибудь сталкивался с подобным?
Нашли рабочее решение?
Exch 2019
Нагрузка на CPU и память в норме.
WAS
Log name System
EventSource Microsoft-Windows-WAS
Date and Time 19.10.2024 12:07:17
Event ID 5011
Task Category 0
Level Warning
User N/A
Computer EXCH12.000.ru
Description A process serving application pool ‘MSExchangeSyncAppPool’ suffered a fatal communication error with the Windows Process Activation Service.
The process id was ‘36656’. The data field contains the error number.
Parameters: MSExchangeSyncAppPool
36656
6D000780
-
-
#2
А что дает Test-ServiceHealth ?
Event 5011 means the Exchange application pools crashed.
The possible cause may be the server was having some performance issues at that time, like high CPU usage.
Do you have some third-party software running on the Exchange server? For example, anti-malware or backup software.
-
-
#3
Test-ServiceHealth ничего особенного не показывает. Все службы работают.
Очереди сообщений нет.
Куда еще копать не знаю (
-
Технические форумы
-
Microsoft
-
Exchange Server
-
На данном сайте используются cookie-файлы, чтобы персонализировать контент и сохранить Ваш вход в систему, если Вы зарегистрируетесь.
Продолжая использовать этот сайт, Вы соглашаетесь на использование наших cookie-файлов.