Announcement

Collapse
No announcement yet.

Unable to start VSS writer from services.msc ?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unable to start VSS writer from services.msc ?

    Hi All,

    I'm having problem in starting the Symantec VSS writer from the services console, see the following diagnosis log:

    Code:
    Log Name:      System
    Source:        Service Control Manager
    Date:          15/09/2010 4:41:48 PM
    Event ID:      7023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MOSSDEV01.domain.com
    Description:
    The Backup Exec VSS Provider service terminated with the following error: The class is configured to run as a security id different from the caller
    ####################################################################################################
    Here's the pop up message content when i tried to start the service manually from the services.msc:
    Windows could not start the Backup Exec VSS Provider service on Local Computer.
    Error 0x80004015: The class is configured to run as a security id different from the caller
    ####################################################################################################
    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.
    
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {34de22c6-4a77-4af6-9ae6-1b4eee4d629b}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {c6074e09-4962-4290-9639-d8cc7d08f644}
       State: [8] Failed
       Last error: Non-retryable error
    
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {b7312b38-21e6-4256-a6a4-22b7d092a631}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {f9a08539-b34b-43f0-9f4e-e063721c801d}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {f66756d6-4aab-487d-a9c8-47fe2cc8e8d6}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {0af9df28-119b-4177-9ea1-7f84eeadbdb8}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {9ba3b2c3-4947-4cb9-894b-d084464aef29}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'SPSearch VSS Writer'
       Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
       Writer Instance Id: {9f4ab399-ff20-4dae-9063-7b737d52edd3}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'OSearch VSS Writer'
       Writer Id: {8d5f38cd-fb7a-49ca-ae1b-21d1f017d8f9}
       Writer Instance Id: {b87cc4be-935b-4479-ac5d-618a41767a0f}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {76d8b78a-0c87-464f-b538-4fee7c515f42}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {b18c717e-2d37-4987-b84b-87bebd77a629}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {9f5a29f8-93f8-48a6-8330-605423ad951b}
       State: [9] Failed
       Last error: Timed out
    
    C:\Windows\system32>
    ############################################################################################
    Can anyone share their experience in resolving this issue please ?

    This happens on Windows Server 2008 Standard x64 which has SQL Server 2008 SP1 and SharePoint 2007 SP2

    Thanks,

    AWT

  • #2
    Re: Unable to start VSS writer from services.msc ?

    Does this help at all???

    http://seer.entsupport.symantec.com/docs/280381.htm

    Comment

    Working...
    X