• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8051
  • Last Modified:

VSS Error in Application Event Log 12293

We have a new server running 2008 Server R2 (64 bit) - we are running Backup Exec 2010.  Everytime a backup runs we are getting two errors in the event log within the first 3 minutes - 8193 and 12293.  Interstingly enough the backup job conitues and does complete but has errors as a result of this and is not backing up every.

Symantec Support spent extensive time looking at the problem and determined with the vssadmin list writers that all were in a stable state until the backup made a call - then they failed and eventually returned to a stable state.  After exhausting their knowledge base they said there was a Microsoft Hotfix specific to error 12293 that should fix the problem.  

They are correct there is a hotfix for this however it is for Vista and 2008 server - it will not install on R2.  I am not sure at this point what to try - any thoughts?

Log Name:      Application
Source:        VSS
Date:          11/9/2010 5:15:08 PM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GMSVR5.goldmedal.local
Description:
Volume Shadow Copy Service error: Unexpected error calling routine Cannot find anymore diff area candidates for volume \\?\Volume{3b8647bb-c5a4-11df-b70c-806e6f6e6963}\ [0].  hr = 0x8000ffff, Catastrophic failure
   
Log Name:      Application
Source:        VSS
Date:          11/9/2010 5:15:08 PM
Event ID:      12293
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GMSVR5.goldmedal.local
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({e1d9fad2-dd06-4086-ae4f-062a59eb4450}) [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
0
magarner
Asked:
magarner
  • 7
  • 6
1 Solution
 
noxchoGlobal Support CoordinatorCommented:
Remove Backup Exec 2010. Then run complete backup of Windows system drive using Windows Backup & Recovery.
Check in Event Log - does it start VSS and close it correctly?
If yes then problem in the way BE2010 calls for VSS admin.
Also I thought that symantec has its own VSS service and that should be used by this product, not Microsoft VSS.
0
 
magarnerAuthor Commented:
Any option besides removing the software - we contracted with our symantec vendor to install and configure the application - I am not willing to throw that away.  What about stopping all the BE services and trying the windows backup - would that suffice?
0
 
noxchoGlobal Support CoordinatorCommented:
Good idea. Try it this way then. But in previous versions of BESR their VSS substituted MS VSS. And there was no way to run MS VSS when BESR or Acronis VSS was stopped.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
magarnerAuthor Commented:
I shut down all the services - ran Windows Backup - tried just backing up the system state - it failed the following error in the application log.  Not sure what this means.


Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          11/11/2010 1:35:06 PM
Event ID:      517
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      GMSVR5.goldmedal.local
Description:
The backup operation that started at '¿2010¿-¿11¿-¿11T18:33:21.959678200Z' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
    <EventID>517</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2010-11-11T18:35:06.732678200Z" />
    <EventRecordID>4608</EventRecordID>
    <Correlation />
    <Execution ProcessID="4284" ThreadID="5844" />
    <Channel>Application</Channel>
    <Computer>GMSVR5.goldmedal.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BackupTime">2010-11-11T18:33:21.959678200Z</Data>
    <Data Name="ErrorCode">2155347997</Data>
    <Data Name="ErrorMessage">%%2155347997</Data>
  </EventData>
</Event>
0
 
noxchoGlobal Support CoordinatorCommented:
Execute in command line under admin the following command: vssadmin list writers
Does it show any writer?
0
 
magarnerAuthor Commented:
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: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {aa41971d-923b-4980-9ab4-1c68da501a2d}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {d635e96c-dc57-48bc-9102-da30fe0a183d}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {fe3b8289-ff47-4617-bec9-b73309b239a6}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {6b25d097-031f-4ae5-8109-e0ca45fff365}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {d39ea6f0-2e2d-4a4a-a982-f850ac8c94ff}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {770171d4-c298-4843-9c5b-b9cb49184e26}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {03767e6c-997f-4e57-9211-63147b935451}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {06cbed94-bccc-41e0-9e2b-2a09e145b41b}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {8844975e-3092-4bbb-9ab1-7344174bd538}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {2dbc0383-3276-4300-8488-c75d3c32b42d}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {7b671672-e8f9-47c6-a08c-b38576073a21}
   State: [1] Stable
   Last error: No error
0
 
noxchoGlobal Support CoordinatorCommented:
Try this: http://www.seasideit.com/2009/11/re-register-vss-writers.html
Then try again to take backup with Windows Backup & Recovery.
If this does not help I would deinstall BESR.
0
 
magarnerAuthor Commented:
That did not fix the problem.  Why would I uninstall Backup Exec when the windows backup also fails?
0
 
noxchoGlobal Support CoordinatorCommented:
As I said - their VSS provider substitutes Windows standard provider. And you cannot tell for sure that Windows own one is not working.
0
 
magarnerAuthor Commented:
OK - I forgot you mentioned that - removing the application is not an option at this time - I am getting a backup just getting these errors.  I will have to contact our Vendor to assist with removal and reinstall.  I assume all that removal is going to prove is that it is a symantec problem vs. a Microsoft problem.
0
 
noxchoGlobal Support CoordinatorCommented:
Yes, exactly. At the moment you cannot address Symantec because they will say - it is MS problem.
And you cannot contact MS cause they will easily point to Symantec.
If you run Backup & Recovery on bare Windows (without other VSS providers installed) then MS has not space to circle its tale.
0
 
magarnerAuthor Commented:
Well - I must apologize after further research the re-registering of the DLL's did get rid of VSS errors in the event log - I am still having problems - but that did take care of the specific problem I asked about - thank you.
0
 
noxchoGlobal Support CoordinatorCommented:
Thank you for feedback.
Noxcho
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now