Error Id 5139
Contents |
The servers hosted several websites and they all ran in 32-bit mode. Several days later I noticed the System log was event id 5139 was exchange 2010 full of the following errors for one of the websites that I a listener channel for protocol 'http' in worker process didn't update. Troubleshooting IIS Event ID 5139 Log Name: System Source: Microsoft-Windows-WAS Date: 5/9/2014 8:11:57 AM Event
The Module Dll C:\windows\system32\rpcproxy\rpcproxy.dll Failed To Load. The Data Is The Error.
ID: 5139 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: Description: A listener channel for protocol 'http' in worker process '%' serving application pool '%' reported a listener
Event Id 2280
channel failure. The data field contains the error number. I did some searching on the error and did not find much help. TechNet contains the following article for troubleshooting IIS Event ID 5139. But the solution proposed (restarting IIS and WAS) is not very helpful. My Application log showed the following errors that seem to coincide with the WAS errors event id 2280 source iis-w3svc-wp in the System log. CompDyn.dll is the Dynamic Compression Native Module Log Name: Application Source: Microsoft-Windows-IIS-W3SVC-WP Date: 5/9/2014 8:12:08 AM Event ID: 2280 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Description: The Module DLL C:\Windows\System32\inetsrv\compdyn.dll failed to load. The data is the error. Root Cause The error seems to be caused by the Dynamic Compression module, but why? The primary change I had made, was changing the other website's application pool to 64-bit. When I stopped the 64-bit application pool, the other application pool was able to load compdyn.dll. As soon as I started the 64-bit application pool, the 32-bit pool started failing. Alternatively, when I set the 64-bit application pool back to 32-bit, there error's cleared. What I'm suspecting is happening is that when the Dynamic Compression module gets loaded into a 64-bit application pool it's unable to load in a 32-bit application pool. Process Explorer shows that the DLL is loaded by each w3wp.exe process, which should mean that there's isolation between them. But there's obviously some kind of impact between the
2003 and before Discussions on Event ID 5139 Ask a question about this event 5139: A directory service object was moved On this page Description of this event Field
Event Id 5139 Was Exchange 2013
level details Examples Discuss this event Mini-seminars on this event This event documents c1000780 the move ofan AD objects from one OU to another, identifying the object moved anduser whomoved it and its event id 5141 old and new location. Of course this eventwill only beloggedwhen the object's parent's audit policy has auditing enabled formoves of the object classinvolvedand for the user performing the action or a group http://byronpate.com/2014/05/troubleshooting-iis-event-id-5139/ to which the user belongs. Free Security Log Quick Reference Chart Description Fields in 5139 Subject: The user and logon session that moved the object. Security ID: The SID of the account. Account Name: The account logon name. Account Domain: The domain or - in the case of local accounts - computer name. Logon ID is a semi-unique (unique between reboots) number that identifies https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventID=5139 the logon session. Logon ID allows you to correlate backwards to the logon event (4624) as well as with other events logged during the same logon session. Directory Service: Name: DNS name of the domain of the object Type: "Active Directory Domain Services" or possibly other directory service if appropriate. Maybe different value for ADAM or Lightweight Directory Services? Object: This is the object just deleted. Old DN: the old X.400 distinguished name of the object reflecting its old location prior to the move NewDN: thenew X.400 distinguished name of the object reflecting itsnew locationafter to the move GUID: while "GUID" would indicate this should be the globally unique identifier of the object, as of Win2008 RC1 this field appears to just be the new DN repeated Class: the objectClass of the object as defined in the AD schema Operation: Correlation ID: Multiple modifications are often executed as one operation via LDAP. This value allows you to correlate all the modification events that comprise the operation. Just look for other events with the same Correlation ID. Application Correlation ID: Always "-"? Unknown. Start a discussion below if you have informati
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 http://kb.eventtracker.com/evtpass/evtPages/EventId_5139_Microsoft-Windows-WAS_64841.asp to be restarted in order to return to normal operation. Because application pools https://kb4sp.wordpress.com/2009/10/28/listener-channel-failures-process-activation-errors-licence-acquisition-failure-its-all-happening-today/ 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 depends on WAS. To perform these procedures, you must have membership in Administrators , or you must have been delegated the event id appropriate authority. Stop and start the application pool To stop and start the application pool: 1.Click 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 event id 5139 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 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 w
from a web site automagically saves as azip → Listener Channel Failures, Process Activation errors, Licence Acquisition failure. It's all happeningtoday… Posted on October 28, 2009 by Brad Saide Just had an interesting error crop up at a client site. One of the team (Hi Daniel!) was building a SharePoint server and was halfway through configuring it, when it suddenly stopped working. 503 errors on all web sites on the server, and some very strange errors in the event log:
Event ID: 8200 Source: Security-Licensing-SLC Log: Application Level: Error Details: License acquisition failure details. hr=0x8004FE33 Event ID: 5139 Source: WAS Log: System Level: Warning Details: A listener channel for protocol ‘http' in worker process # serving application pool ‘SharePoint Central Administration v3' reported a listener channel failure. The data field contains the error number. Event ID: 5002 Source: WAS Log: System Level: Error Details: Application pool ‘SharePoint Central Administration v3' is being automatically disabled due to a series of failures in the process(es) serving that application pool. WAS is the Windows Process Activation Service (you'll need to know that shortly). I'm not sure what the root cause of this error is, but someone somewhere in Microsoft does. Essentially, if you are using IPv6 and have nominated a Dedicated Crawl Server, the SharePoint application writes some bogus entries to the Windows Host file, causing WAS to fail. The solution is to either: Set up the SharePoint crawl service so it uses all WFE servers to crawl content (as Central Admin is FUBAR'd, you'd need to use STSADM to change this property), or Remove IPv6 from the Server NIC's and restart the Windows process Activation service. This then writes nice entries to the Hosts file and the problems evapourate like morning dew on a hot day. This is the site that we found the solution on - http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx (we used Workaround 2). Cheers!Brad Share this post:Click to email (Opens in new window)Click to print (Opens in new window)Click to share on Twitter (Opens in new window)Share on Facebook (Opens in new window)Click to share on LinkedIn (Opens in new window)MoreClick to share on Google+ (Opens in new window)Click to share on Reddit (Opens in new window)Like this:Like Loading... Related About Brad Saide I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my wa