Windows LiveWindows Live™
 
 
Perfil de BradSharePoint BlogFotosBlogListas Herramientas Ayuda

Blog
    28 octubre

    Listener Channel Failures, Process Activation errors, Licence Acquisition failure. It's all happening today...

    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

    15:46 | Agregar al blog

    Comentarios (1)

    Espera...
    El comentario que has escrito es demasiado largo. Acórtalo.
    No has escrito nada. Vuelve a intentarlo.
    No se puede agregar tu comentario en este momento. Vuelve a intentarlo más tarde.
    Para agregar un comentario, necesitas permiso de tus padres. Pedir permiso
    Tus padres han desactivado los comentarios.
    No se puede eliminar tu comentario en este momento. Vuelve a intentarlo más tarde.
    Has superado el número máximo de comentarios que se puede dejar en un día. Vuelve a intentarlo en 24 horas.
    Se ha deshabilitado la capacidad de tu cuenta de dejar comentarios porque nuestros sistemas indican que podrías estar enviando correo no solicitado a otros usuarios. Si crees que tu cuenta se ha deshabilitado por error, ponte en contacto con el servicio de soporte técnico de Windows Live.
    Para terminar de dejar tu comentario, realiza la siguiente comprobación de seguridad.
    Los caracteres que escribas en la comprobación de seguridad deben coincidir con los de la imagen o el audio.

    Para agregar un comentario, inicia sesión con tu cuenta de Windows Live ID (si utilizas Hotmail, Messenger o Xbox LIVE, ya tienes una cuenta de Windows Live ID). Iniciar sesión


    ¿No tienes una cuenta de Windows Live ID? Regístrate
    Sin nombreescribió:
    Hey Brad, Can you please post exact STSADM command to change crawl service to use WFE. I am having same issue. Central admin is not working. Thanks
    Hace 5 días

    Vínculos de referencia

    La dirección URL del vínculo de referencia de esta entrada es:
    http://sharepointblog.spaces.live.com/blog/cns!74C8FB1191265567!615.trak
    Weblogs que hacen referencia a esta entrada
    • Ninguno