none
Fallas que bloquean cuentas. RRS feed

  • Pregunta

  • aplicamos este proceso sin éxito.

    Log Name:      Application

    Source:        Microsoft-SharePoint Products-SharePoint Server

    Date:          24/05/2016 12:07:15

    Log Name:      Application

    Source:        Microsoft-SharePoint Products-SharePoint Server

    Date:          24/05/2016 12:07:15

    Event ID:      6482

    Task Category: Shared Services

    Level:         Error

    Keywords:     

    User:          dom1\uhp

    Computer:      HF.dom1.ad

    Description:

    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ad3dc401-2394-468b-8fd0-259cc2e73910).

    Reason: The device is not ready. 

    Technical Support Details:

    System.IO.FileNotFoundException: The device is not ready. 

       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-SharePoint Products-SharePoint Server" Guid="{C33B4F2A-64E9-4B39-BD72-F0C2F27A619A}" />

        <EventID>6482</EventID>

        <Version>15</Version>

        <Level>2</Level>

        <Task>3</Task>

        <Opcode>0</Opcode>

        <Keywords>0x4000000000000000</Keywords>

        <TimeCreated SystemTime="2016-05-24T15:07:15.004385100Z" />

        <EventRecordID>1471199</EventRecordID>

        <Correlation ActivityID="{B0577F9D-BDB9-F02F-7F0B-32F9AEEE1CDD}" />

        <Execution ProcessID="8040" ThreadID="4984" />

        <Channel>Application</Channel>

        <Computer>HF.dom1.ad</Computer>

        <Security UserID="S-1-5-21-1615391633-1184903989-954415197-4300" />

      </System>

      <EventData>

        <Data Name="string0">Microsoft.Office.Server.Search.Administration.SearchServiceInstance</Data>

        <Data Name="string1">ad3dc401-2394-468b-8fd0-259cc2e73910</Data>

        <Data Name="string2">The device is not ready.  </Data>

        <Data Name="string3">System.IO.FileNotFoundException: The device is not ready. 

       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)</Data>

      </EventData>

    </Event>

    1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
    2. Navigate to the cache folder  In Windows Server 2008, the configuration cache is in the following location:  Drive:\ProgramData\Microsoft\SharePoint\Config  In Windows Server 2003, the configuration cache is in the following location:  Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config  Locate the folder that has the file “Cache.ini”  (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
    3. Back up the Cache.ini file.
    4. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
    5. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
    6. Double-click the Cache.ini file.
    7. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
    8. Start the Windows SharePoint Services Timer service
    9. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

    10.  Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

    Regards,

    Event ID:      6482

    Task Category: Shared Services

    Level:         Error

    Keywords:     

    User:          dom1\uhp

    Computer:      HF.dom1.ad

    Description:

    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ad3dc401-2394-468b-8fd0-259cc2e73910).

    Reason: The device is not ready. 

    Technical Support Details:

    System.IO.FileNotFoundException: The device is not ready. 

       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-SharePoint Products-SharePoint Server" Guid="{C33B4F2A-64E9-4B39-BD72-F0C2F27A619A}" />

        <EventID>6482</EventID>

        <Version>15</Version>

        <Level>2</Level>

        <Task>3</Task>

        <Opcode>0</Opcode>

        <Keywords>0x4000000000000000</Keywords>

        <TimeCreated SystemTime="2016-05-24T15:07:15.004385100Z" />

        <EventRecordID>1471199</EventRecordID>

        <Correlation ActivityID="{B0577F9D-BDB9-F02F-7F0B-32F9AEEE1CDD}" />

        <Execution ProcessID="8040" ThreadID="4984" />

        <Channel>Application</Channel>

        <Computer>HF.dom1.ad</Computer>

        <Security UserID="S-1-5-21-1615391633-1184903989-954415197-4300" />

      </System>

      <EventData>

        <Data Name="string0">Microsoft.Office.Server.Search.Administration.SearchServiceInstance</Data>

        <Data Name="string1">ad3dc401-2394-468b-8fd0-259cc2e73910</Data>

        <Data Name="string2">The device is not ready.  </Data>

        <Data Name="string3">System.IO.FileNotFoundException: The device is not ready. 

       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)</Data>

      </EventData>

    </Event>

    1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
    2. Navigate to the cache folder  In Windows Server 2008, the configuration cache is in the following location:  Drive:\ProgramData\Microsoft\SharePoint\Config  In Windows Server 2003, the configuration cache is in the following location:  Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config  Locate the folder that has the file “Cache.ini”  (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
    3. Back up the Cache.ini file.
    4. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
    5. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
    6. Double-click the Cache.ini file.
    7. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
    8. Start the Windows SharePoint Services Timer service
    9. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

    10.  Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

    Regards,


    Alejandro | Especialista en Infraestructura Microsoft y Fortinet|

    miércoles, 25 de mayo de 2016 20:19

Todas las respuestas

  • Hola Alejandro, 

    De casualidad no has cambiado nada a nivel de la aplicación de servicio de búsqueda? 

    Te recomiendo revisar la(s) cuentas que tengas ligadas a este servicio. 

    También te recomiendo revisar los permisos a las bases de datos del servicio en mención (Búsqueda).


    Gabriel Edo. Sibaja | Comunidad SharePoint Costa Rica - http://www.sharepointcostarica.com | Twitter: @Gabs_Sibaja | Blog: http://gabsibaja.blogspot.com

    domingo, 5 de junio de 2016 23:34