Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SBS2011 V-79-57344-33932 - Unable to attach to a resource

Created: 17 Jul 2013 • Updated: 17 Jul 2013 | 7 comments

I'm struggling to resolve the below issue backing up an SBS2011 server, can anyone point me in the right direction?

 

Backup Exec 2012 \v 14.0 Rev. 1798 (64bit)

Full System backup fails at the end with this log. All services are started. Its an admin account.

Errors
Click an error below to locate it in the job log
Backup- SBS2011.domainname.localUnable to attach to SBS2011.domainname.local\SHAREPOINT.

V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Unable to attach to SBS2011.domainname.local\SBSMONITORING.

V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Unable to attach to SBS2011.domainname.local\MICROSOFT##SSEE.

V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Unable to attach to SBS2011.domainname.local\BKUPEXEC.

V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Backup - Snapshot Technology: Initialization failure on: "\\SBS2011.domainname.local\System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11226 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology selected returned: "Unexpected provider error". Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.

 

Operating Systems:

Comments 7 CommentsJump to latest comment

SuperBrain's picture

http://www.symantec.com/docs/TECH71780

Have you already attempted to follow instructions on that technote? It looks extensive, but might have a solution for you in it. Let us know if you have any difficulties with that article.

RodneyC's picture

I've checked pretty much all that but that artical isn't for Backup Exec 2012.

All the credentials have been checked, re-entered, all services working, no remote server involved, its a fresh install of SBS2011 (was a migration) and Symantec and no antivirus on yet.

 
 

 

Lothar Müller's picture

Please check if your account has rights in the database instances.
This ist not automaticaly done if you use a another account than "Domain\Administrator"

To check if it is the problem you can grant dbo-Rights to the account in the instance.
You can grant this right over the SQL Management Studio.

If this helped you to solve your problem, please mark this post as solution for this case.

lmosla's picture

Hello  

Run vssadmin list providers and post the results. 

also do you have any Windows Event Viewer errors?

Make sure you have installed all the Live updates.

RodneyC's picture

Some of the VSS writers have failed and its not service packed so going to run a load of updates and reboot and try again.

RodneyC's picture

Not really getting anywhere with this. :(

C:\Users\administrator.DIAMONDEX>vssadmin list writers
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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8ed4bb20-0b08-4e03-92ea-2ba543d8cde7}
   State: [7] Failed
   Last error: Timed out

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {33d45031-b11f-4ce7-8e5c-f0338006c480}
   State: [7] Failed
   Last error: Timed out

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {65fa2bcb-9d38-48d8-92f3-040f299d925d}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
   Writer Instance Id: {999d2fd7-818b-4b9c-aef6-7a48db734d33}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {df857f74-8189-4fa8-a077-527a2b85042a}
   State: [7] Failed
   Last error: Timed out

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {211c8aed-d620-4b6a-86ab-33ee691d4afd}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {78b07421-56ef-47bf-90f9-f29933ec1b6a}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {e2de4d63-c6a3-454b-80c0-a724094336ac}
   State: [7] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {43e6ea85-d023-4564-996f-449703a9dbb0}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {342efdff-1780-4d98-a5bc-5026295a7010}
   State: [7] Failed
   Last error: Timed out

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {0010ea27-775a-49ec-98ef-830455952417}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {60976194-132c-401e-b28f-7b6d1a9c8905}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {156aeb9c-8308-454c-9666-6c78c1ee7f95}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {f341a82d-1de5-4b62-85ef-f4b0a08bcba8}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {1635c1d7-fb2c-4bd3-abe5-a87eebf29d40}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {06b7255f-4c15-4a97-962a-e486210dfc93}
   State: [7] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {6aab8c9d-341f-4bb6-ac7f-b8353e03706a}
   State: [7] Failed
   Last error: Timed out

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {c8b1b5b4-aafe-42df-9c67-00d72338e036}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {fcb157e3-afa6-42f1-a394-51167f465a1b}
   State: [7] Failed
   Last error: Timed out

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {7cfa0585-365b-4974-acc9-2378e6f257ac}
   State: [7] Failed
   Last error: Timed out

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {279a3908-930a-40bf-bd75-2a0678c6b7bf}
   State: [7] Failed
   Last error: Timed out

C:\Users\administrator.domain>

MusSeth's picture

Most of the writers are showing in failed state.please reboot the server once to get the writers in stable state and than run a backup....this should get the system state and vss issue resolved...for sql related errors I.e unable to attach to the resource..open sql management studio and and the account to following groups
Dbowner
Dbcreator
Sysadmin