Solved

Backup Exec fails to access System State

Posted on 2008-06-25
4
3,076 Views
Last Modified: 2013-12-01
Upgrade to Backup Exec v12 from v11d and am now getting errors on 2 servers.  I have 20 other servers that back up just fine after the upgrade.  

The attached errorm message is received when viewing the Selections list and choosing the System State to be backed up.

The job log has this info in it:  

-------------------------------------------------------------------------------------
Backup- \\TRACKER\D: Unable to attach to \\TRACKER\System?State.

V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------

The server is online as as all other items on that server get backed up just fine.
SysStateError.JPG
0
Comment
Question by:XUPH18DXK
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 28

Accepted Solution

by:
honmapog earned 125 total points
ID: 21902024
Does this apply? http://seer.entsupport.symantec.com/docs/290108.htm
Otherwise, try to apply http://support.microsoft.com/kb/940349 on the two servers.

What is the result of "vssadmin list writers" on those 2 servers?
0
 

Author Closing Comment

by:XUPH18DXK
ID: 31470653
Applying SP1 fixed one of the servers.  The other one, this did not.  For the second one, I needed to re-register the VSS dlls.
0
 

Expert Comment

by:markodenev
ID: 22150193
I get the same error when i do a vssadmin list writers nothing is returned
0
 

Author Comment

by:XUPH18DXK
ID: 22165206
You'll need to re-register the DLLs that handle the VSS.

Here is a list of what to do:

1. Open a command prompt and change directories to \WINDOWS\system32
2. net stop vss
3. regsvr32 ole32.dll
4. regsvr32 vss_ps.dll
5. Vssvc /Register
6. regsvr32 /i swprv.dll
7. regsvr32 /i eventcls.dll
8. regsvr32 es.dll
9. regsvr32 stdprov.dll
10. regsvr32 vssui.dll
11. regsvr32 msxml.dll
12. regsvr32 msxml3.dll
13. regsvr32 msxml4.dll
14. Start the Volume Shadow Copy service by running "net start vss"


Run the "vssadmin list writers" again.  This time, it should provide some output, and your problem fixed.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Replication has always been one of those technologies that people run scared from. The main reason is usually cost. When you think of replication, your mind drifts to solutions that replicate from one disk frame to another using block level technolo…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question