Unable to Start Symantec VSS writer service in services.msc

[Symanticus]

Hi All,

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

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

[sksujeet]

You should have the Backup VSS writer installed on the ws 2008 machines as Backup Exec automatically uses vss provided by MS. From 12.5 onwards you can't install AOFO on the ws 2003 or later server unless and until it is a upgrade or it is xp or ws 2000 server. On ws 2008 it is not recommended to have the symantec vss and you need to uninstall it. The best way is to uninstall the remote agent completely and install it again without AOFO.

If that still doesn't remove it then try below steps. Reboot the server once before doing it and reboot it again once done.

Following is the command to uninstall the AOFO
setup.exe /AOFO: -s -u, and press <Enter>

Manually remove the Backup Exec VSS provider registry key

(1) Find the correct GUID value for the Backup Exec VSS provider by running the VSSADMIN LIST PROVIDERS from within a command prompt window.

(2) Run regedit and go to the following key location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\

(3) Delete the registry key with the coresponding VSS GUID value

(4) Reinstall the remote agent without AOFO option.

[RahulG]

I beleive rebooting the server should fix this issue ...Also incase if you have MAcafee check if McAfee EPO restricted the SYSTEM account to start Symantec provider Service

[Symanticus]

and i also found this on the event viewer:

Log Name:      Application

Source:        Application Error

Date:          16/09/2010 12:40:53 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      MOSSDEV01.domain.com

Description:

Faulting application vssvc.exe, version 6.0.6002.18005, time stamp 0x49e02c5c, faulting module vssvc.exe, version 6.0.6002.18005, time stamp 0x49e02c5c, exception code 0xc0000005, fault offset 0x000000000005ced2, process id 0x1de4, application start time 0x01cb5548534106a4.

[RahulG]

refer the following document http://support.veritas.com/docs/282180 it applies to the veritas storage foundation but you can follow the steps to the unregister the VxVSSProvider