Backup Exec/Server 2008 R2 VSS issues

Can you do one thing? Please Create a Test user on the same server and added it into the Local Administrator group then run Vssadmin list writers

Thank you for the reply. I created the account as you suggested and was able to run the command. The output:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Dear Mandrich,

OUTPUT SHOULD BE LIKE

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {cf3330ef-988b-4fe7-aba1-376245435b35}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {64fe204b-b3d4-446e-a3ff-3deb1f453f16}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {c23ce785-116f-4216-afef-1d1eb67fea13}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {922ba2f5-0df3-4f6a-852e-d66d4424d547}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8ff90be4-1c56-45a1-82fc-bcdcf33a6d38}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {7d575e7f-a68d-451b-a905-444434ef8882}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {7f10f184-f78e-43e8-bb3b-22d2113b5574}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e725e201-b319-46d8-84a2-6344e82ccd63}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {a7584395-1d60-4026-b2fa-4de50874cc43}
   State: [1] Stable
   Last error: No error

If you dont' get above output then you need to re-register VSS .dll

Process is below
=============>
Click Start, click Run, type cmd, and then click OK.
Type the following commands at a command prompt. Press ENTER after you type each command (Yes, do the same thing twice ;)).

 

cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll

Do the same and run the same command i suggested above and try to run the backup

If above solution doesn't solve your problem then try this Microsoft KB

http://support.microsoft.com/kb/940184

Awesome. I will give those a try and report back. Many thanks for the assistance!

Pleasure Mandr1ch.. i wish it would solve your issue.

Please be careful when doing any VSS registration steps with Windows 2008 or newer.
 
Microsoft have released information stating it can break your server, and because of this we have pulled TECH70486
 
As per Microsoft KB http://support.microsoft.com/kb/940184
Important This article is not for use with Windows Vista, with Windows Server 2008, or with later Windows operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest-based. Trying to manually register specific components, as described in the following steps, can have unexpected results that may require you to reinstall Windows to resolve.
New Symantec document here http://www.symantec.com/docs/TECH173983

Mandr1ch,

What is the Status of your problem?
Are you able to resolve your issue?

Its also nice Article on Windows 2003 & 2008 for VSS Re-Registration

http://kb.acronis.com/content/45776

http://careexchange.in/how-to-re-register-vss-volume-shadow-copy-service-in-windows-server-2008-r2/

Thanks for the replies. Finally back onsite and reading through the various info posted here. I did try to do the regsvr32, but all attempts came back with:

"The module "xxxxx.dll" was loaded but the call to DllRegisterServer failed with error code 0x8007005."

This is from an elevated prompt. Also tried elevating via "run as" to be sure. I'll read through the provided info and let you know what works. Thanks!

After reading through the info, I decided to go ahead and try reregistering. With the added switches from that last article, I was able to run down the list without error. However, after doing so I still get the same output for vssadmin list providers.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Thats right there must be 2 prividers.
what about VSSADMIN LIST WRITERS command output

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {d0edee11-7913-43dc-bfb8-057f0751d271}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {d9f88cc9-c2e2-46c9-9283-3e2b7da67807}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {76e32d74-b182-49d1-9929-e45f98c112ca}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {f6f4362c-def5-4c0d-a2e7-56e8ab044022}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {cd5d74d1-cdd1-4527-85c1-1865032df48c}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {576c36ef-4996-4e5c-8632-e1ddf4b56741}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {507b7014-345e-4d83-b859-30c10a1b5d37}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {da364ff2-6277-42f9-8c13-838913e13888}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {941a8980-fd96-41de-9aca-062c2e6cedc7}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {a7aa3cf9-7e9d-4202-ac10-fc2d514debe5}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {32ce2203-824a-4b49-8109-2dd344e308f7}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {4639a33c-97d9-479a-b6d2-24a3b87e2518}
   State: [1] Stable
   Last error: No error

Seems All good. Can you please try to take backup now using test user you created...
If you have any error please let me know

Will do. Thanks.

Finally back onsite. Backups are still failing with the same error. This is after configuring the services with the new admin account that could run the vssadmin commands without permission issues.

You may want to check this post http://www.eventid.net/display.asp?eventid=8230&eventno=10589&source=VSS&phase=1

Not pursuing issue any farther.