Video Screencast Help

VSS / DCOM Error on Image Creation /w BESR 8 german v.

Created: 03 Jun 2008 • Updated: 21 May 2010 | 5 comments
Hello everybody,
I cannot find anything useful on these. As soon as I install BESR8 on a machine, I get errors (any machine affected) :
DCOM - Error 10016 : User NT-Authority not allowed to activate COM - Serverapp /w CLSID

{ 790F2886-9889-4C99-8EF5-531ADD05D044}

This can be changed via Component Service Administration.
Simultaneously, VSS Error (12292) occurs , announcing an error /w creation of COM Class { 790F2886-9889-4C99-8EF5-531ADD05D044} .
There is no Component /w this ID . Does anyone know how to fix it ? 8.0.2 does not ..
Many thanks in advance
A. Neugebauer

Comments 5 CommentsJump to latest comment

SteinDirk's picture


i have the same problem with the same language version!
The error appears, when an Image Jobs starts.
The Image will successful  ended with no errors.

I have also one event in the  software log.

Ereignistyp:    Fehler
Ereignisquelle:    VSS
Ereigniskategorie:    Keine
Ereigniskennung:    11
Volumeschattenkopie-Dienstinformationen: Der COM-Server mit CLSID "{790f2886-9889-4c99-8ef5-531add05d044}" namens "SW_PROV" kann nicht gestartet werden. [0x80070005]

BESR8's picture
Hello, I have the same problem with BESR 8 spanish language. The O.S. is Windows 2003 Standard with SP2 and SQL Server 2005 with SP2. The problem apparence with the creation on the image, Errors VSS 11, 12292
and DCOM 10016. The BESR V8 is also updated
Bundesministerium der Justiz's picture
We were able to solve the issue thanks to Symantec Support Hotline. Particular thing there is nothing to be found in documentation. Yet, the issue seems to be known to the vendor.
The solution works as follows:
Set DCOM Security :  Administrative Tools - Component Security - Component Services - Computers - My Computer - Properties - COM Security - Access Permissions - Edit Default - System - Allow Remote Access
This Setting is hidden in Registry Key :

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole] "DefaultAccessPermission"=hex:01,00,04,80,44,00,00,00,54,00,00,00,00,00,00,00,\14,00,00,00,02,00,30,00,02,00,00,00,00,00,14,00,07,00,00,00,01,01,00,00,00,\00,00,05,0a,00,00,00,00,00,14,00,07,00,00,00,01,01,00,00,00,00,00,05,12,00,\00,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,\05,20,00,00,00,20,02,00,00


Furthermore, on CLI goto C:\program files\Symantec\BESR\Shared\Drivers.

start /w VssProviderInstall.exe -unregister Symantec Symsnap VSS Provider start /w VssProviderInstall.exe -register Symantec Symsnap VSS Providerstart /w VssProviderInstall.exe -register Symantec Symsnap VSS Provider VSS_2003.dll


Afterwards, restart the BESR service.
This way, things can easily be done via batch file execution. Didn't test remote execution /w psexec, though ..
Andre Neugebauer , GIb mbH
MickMarch's picture

After executing the step you indicate, when I type a VSSADMIN LIST PROVIDERS, I do not see anymore the Symantec VSS entry.


Do you have some advice ?




David F's picture

Just ot be sure these are the following steps once again: 


For windows 2003



1. Open DOS window on machine
2. Navigate to the Program Files\Symantec\Backup Exec System Recovery\Shared\Drivers folder
3. Type vssproviderinstall.exe -register VSS_2003.dll "Symantec SymSnap VSS Provider" "Symantec SymSnap VSS Provider"
4. Press Enter
5. Go to Services to make sure that service now appears and is set to automatic and started.

***If the OS is XP, use the VSS_XP.dll file to register the service. There is also a 64 bit version of this dll file available on 64 bit installations of BESR


Secondly, check DCOM | Computers | My computer | Com + Applications if Symantec SymSnap VSS Provider is listed, if not likley you are not going to see the BESr provider in VSSADMIN LIST PROVIDERS.