Perfil de BradSharePoint BlogFotosBlogListas Herramientas Ayuda

Blog


    05 agosto

    "Error: Class not registered" when trying to start WSS Search

    Had a puzzling error recently where I was trying to set up a new farm. Single WFE, Separate SQL Server, simple config.

    So I installed MOSS 2007, then SP 2 for WSS and MOSS. Everything went fine until I started to run through my configuration process – Every time I tried to start the WSS Search Service on the Windows 2003 R2 server I was installing onto, it would come up and say

    Error: Class Not Registered

    Like most of the alerts that appear in MOSS, this too was incredibly helpful and told me exactly what I needed. So… here's what I tried:

    Check the ULS logs – Nothing in there saying that "Driver nnnnn is not registered" or something that would have been useful, just garbage

    0 Unassigned Initialize New Project: Search called  - File:d:\office\source\search\search\gather\server\gatherobj.cxx Line:653
    0 Unassigned Initialize New Project, Remove: Search - File:d:\office\source\search\search\gather\server\gatherobj.cxx Line:739
    0 Monitorable CContentSourceCollection::Init in m_pScheduler.CoCreateInstance, Error is 0x80040154 - File:d:\office\source\search\search\gather\server\contentsource.cxx Line:1287
    0 Monitorable <Exception><HR>0x80040154</HR><eip>00000000601BE7B0</eip><module>d:\office\source\search\search\gather\server\contentsource.cxx</module><line>1288</line></Exception>
    0 Monitorable <Exception><HR>0x80040154</HR><eip>00000000601E29D3</eip><module>d:\office\source\search\search\gather\server\gatherobj.cxx</module><line>837</line></Exception>
    0 Unassigned Leaving Initialize New Project: Search ; hr=0x80040154  - File:d:\office\source\search\search\gather\server\gatherobj.cxx Line:954
    0 Monitorable <Exception><HR>0x80040154</HR><eip>0000000060107B50</eip><module>d:\office\source\search\search\gather\gthrsvc\cgatherprj.cxx</module><line>690</line></Exception>
    0 Monitorable CGatherPrjCollection::AddRecoverOptional: Failed in :pProject->InitializeNew, Error is 0x80040154 - File:d:\office\source\search\search\gather\gthrsvc\cgatherprj.cxx Line:3712
    8u6i High     Application '544760de-b60e-4da7-aea3-b02d6881ae9b': Class not registered  . Failed while configuring the gatherer application with an exception. Attempting to clean up... - System.Runtime.InteropServices.COMException (0x80040154): Class not registered       at
    0 Monitorable <Exception><HR>0x80070002</HR><eip>0000000000A9369B</eip><module>d:\office\source\search\ytrip\tripoli\query\isreg.cxx</module><line>825</line></Exception>
    8wsw High     Now terminating ULS (mssearch.exe, onetnative.dll)
    8wsv High     ULS Init Completed (mssearch.exe, onetnative.dll)
    8dw7 High     The call to SPSearchServiceInstance.Provision (server 'AUMLC52DIA46') failed. Setting back to previous status 'Disabled'. System.Runtime.InteropServices.COMException (0x80040154): Class not registered       at Microsoft.SharePoint.Search.Administration.MSSITLB
    8dw7 High     ...PSearchServiceInstance.Synchronize(Boolean installGathererApplication)     at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()     at Microsoft.SharePoint.Search.Internal.UI.SPSearchServiceInstanceSettings.BtnSubmit_Click(Objec
    8xqz Medium   Updating SPPersistedObject SPSearchServiceInstance Parent=SPServer Name=AUMLC52DIA46. Version: 3105 Ensure: 0, HashCode: 66070359, Id: 53538cac-1888-446d-88ce-38a2106549e1, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.Update()     at Micr
    8xqz Medium   ...ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
    8xqz Medium   ...t context, AsyncCallback cb, Object extraData)     at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)     at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)     at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr
    8inc Medium   In SSOService::Synch(), sso database conn string:
    8u3j High     Registry key value {SearchThrottled} was not found under registry hive {Software\Microsoft\Office Server\12.0}. Assuming search sku is not throttled.
    0 Medium   Entering MRU trim routine.
    0 Medium   Initial table size: 27232355 in 136 entries
    0 Medium   Final table size: 27232355 in 136 entries
    0 Medium   Exiting MRU trim routine.

    So, maybe the installation didn't go well? I decided to discount that as an option after the third attempt with no change.

    Maybe it was because I was setting the Search Index to be on D drive prior to enabling search (and MS had hard-coded the default search index path in there as part of the deployment script)? Tried fixing that too, nothing changed.

    Maybe I'd found a new bug in SP2 (I was applying SP2 before configuring the farm)? It turned out that I was not correct there either.

    Google had lots of hits, most of which related to MS CMS or .NET Framework development.

    Then I thought… What if this search service account does not have enough disk access rights based on local privileges? Sure enough, as soon as I added the account to the local Admin group it all went fine. So I tried to refine my search on Google and came up with this little beauty - http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/0cca4e8b-eac0-4c27-9bc2-0e574c8094ad – the response from Microsoft was: Give the Search account more rights. Not what to, or why, or what level of rights… just "More". Sweet!

    Now I know what it is, I can use this information about the mandatory security required to narrow down the issue – MOSS http://technet.microsoft.com/en-us/library/cc721637.aspx – WSS 3 http://technet.microsoft.com/en-us/library/cc721631.aspx.

    What's that Roger? Oh, it's a development environment? Well, at least I've got a starting point the next time this issue comes up :)

    B

    Comentarios

    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

    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!576.trak
    Weblogs que hacen referencia a esta entrada
    • Ninguno