5139 Error
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows event id 5139 was exchange 2010 Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs
A Listener Channel For Protocol 'http' In Worker Process
Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise
The Module Dll C:\windows\system32\rpcproxy\rpcproxy.dll Failed To Load. The Data Is The Error.
See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses
Iis-w3svc-wp 2280
Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet event id 2280 Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. IIS Windows Process Activation Service (WAS) IIS Protocol Adapter IIS Protocol Adapter Availability IIS Protocol Adapter Availability Event ID 5139 Event ID 5139 Event ID 5139 Event ID 5136 Event ID 5137 Event ID 5138 Event ID 5139 Event ID 5140 Event ID 5142 Event ID 5147 Event ID 5148 Event ID 5158 Event ID 5159 Event ID 5175 Event ID 7001 Event ID 7002 Event ID 7003 Event ID 7004 Event ID 7005 Event ID 7006 TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Event ID 5139 — IIS Protocol Adapter Availability Updated: January 20, 2010Applies To: Windows Server 2008 An Internet Information Services (IIS) Web server responds to requests on a given protocol by using a listener adapter. The protocol-specific listener adapter communicates with the Windows Process Activation Service (WAS) by
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums IIS 7 and Above c1000780 Troubleshooting HELP Please DefaultAppPool won't stay running. HELP Please DefaultAppPool won't stay event id 5139 was exchange 2013 running. [Answered]RSS 8 replies Last post Oct 15, 2012 11:29 AM by lexus9999 ‹ Previous Thread|Next Thread iis error 5002 › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply hevnbnd 29 Posts HELP Please DefaultAppPool won't stay running. Jan 18, 2010 https://technet.microsoft.com/en-us/library/cc735207(v=ws.10).aspx 12:15 PM|hevnbnd|LINK Ever-time I go to our website or http://localhost/ i get error 503 Service unavailable. The DefaultAppPool crashes with the following error. "A listener channel for protocol 'http' in worker process '7316' serving application pool 'DefaultAppPool' repareted a listener channel failure. The data field contains the error number." Event ID 5139, WAS I followed these http://forums.iis.net/t/1164227.aspx?HELP+Please+DefaultAppPool+won+t+stay+running+ steps listed on technets site http://technet.microsoft.com/en-us/library/dd349294%28WS.10%29.aspx and that did not do anything to fix the problem. A little background. This is a server 2008 R2 that was recently upgraded to Exchange 2010. I do not believe the website has worked since the 2010 upgrade. Any help would be greatly appreciated. Reply ma_khan 862 Posts MVPModerator Re: HELP Please DefaultAppPool won't stay running. Jan 18, 2010 01:13 PM|ma_khan|LINK Can you check if moving your default web site content into another application pool works? Create a new app pool and assign applications to that app pool. restart the IIS service and then check... Reply hevnbnd 29 Posts Re: HELP Please DefaultAppPool won't stay running. Jan 18, 2010 01:39 PM|hevnbnd|LINK Ok, Getting closer. I can now open my website. I moved apps to a new pool and my site opens however when I click on one of the links going to another application in the new pool i get an error 500 message Module IsapiModule Notification ExecuteRequestHandler Handler IS
to Microsoft : Cause : This event is logged when a listener channel for protocol in worker process serving application pool reported a listener channel failure. Resolution : Stop and restart the application pool Application pools occasionally need to be restarted in order to return http://kb.eventtracker.com/evtpass/evtPages/EventId_5139_Microsoft-Windows-WAS_64841.asp to normal operation. Because application pools depend on the Windows Process Activation Service (WAS), you may have to restart WAS. If you restart WAS, you may also have to restart the World Wide Web Publishing Service (W3SVC), which http://h264.code-shop.com/trac/discussion/topic/239?discussion_action=quote; depends on WAS. To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority. Stop and start the application pool To stop and start the application pool: 1.Click event id Start , click Control Panel , and then click Administrative Tools . 2.Right-click Internet Information Services (IIS) Manager and select Run as administrator . 3.In the Connections pane, expand the server node and select Application Pools . 4. In Features View , select the application pool you want to start or stop. 5.In the Actions pane, do one of the following: 6.Click Stop to stop the application pool. 7.Click Start to start the application event id 5139 pool. Stop or restart WAS To stop or restart WAS: 1.Click Start , right-click Computer , and then select Manage . 2.In Server Manager , expand Configuration . 3.Click Services and locate Windows Process Activation Service in the list of services. 4.To stop WAS, right-click Windows Process Activation Service and select Stop .5.To start WAS, right-click Windows Process Activation Service and select Start . Start the W3SVC To start the W3SVC: 1.Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator . 2.At the command prompt, type net start w3svc . Verify : You can use an Internet browser to verify that a protocol adapter is functional by following these steps: 1.Select a Web site or application that is configured to respond to the protocol you want to verify. 2.In the address bar of your browser, type a protocol-specific request to the Web site or applications that you chose in step 1. 3.If the protocol adapter is working, your browser client should display the expected output page. Note : If the protocol adapter is from a third party, refer to the documentation for the adapter. The documentation may have specific steps that explain how to verify the state of the service or process that hos
locked I successfully installed/configured the plugin on a Windows Server 2008 R2 machine running IIS7, and it seemed to be functional. A critical error occurred overnight however, and it resulted in IIS disabling the application pool associated with the site: Log Name: System Source: Microsoft-Windows-WAS Date: 5/27/2011 3:59:31 AM Event ID: 5002 Task Category: None Level: Error Keywords: Classic User: N/A Computer: _removed_ Description: Application pool '_removed_' is being automatically disabled due to a series of failures in the process(es) serving that application pool. Event Xml: