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:
Details: License acquisition failure details. hr=0x8004FE33
Event ID: 5139
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
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).