Home > Backup Exec > Backup Exec 2010 Snapshot Provider Error

Backup Exec 2010 Snapshot Provider Error

Contents

Tuesday, October 11, 2011 9:42 PM Reply | Quote Answers 0 Sign in to vote Hi, From your description, you said that "I'm using Backup exec and the server that Thank you. See you at www.exchangemaster.ch Last Updated ( Jun 03, 2016 at 02:47 PM ) Exchangemaster GmbH has moved! Although I am happy if someone has an alternative because backing up individual mailbox stores is a bit messy when you have a few of them 0 Message Expert Comment Source

To install the necessary roles, go to Server Manager, and select Add Roles and Featu… Windows Server 2012 Storage Software Storage Advertise Here 846 members asked questions and received personalized solutions Example Windows 2008 and 2008 R2 are not the same and will fail with the error above.Both the servers must have the selected Microsoft Volume Shadow Copy Services (VSS) hardware or So backup exec would try and start the service again when its still in the process of still shutting down. Check the Windows Event Viewer for details.

Backup Exec 2010 Error 1603

Both gave the same issues. Article:000036063 Publish: Article URL:http://www.veritas.com/docs/000036063 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in It is possible that updates have been made to the original version after this document was translated and published. When a data protection operation of Shadow Copy Components is performed, the status of the involved VSS Application Writers must be queried to determine its status during the backup or restore.

  1. You may also refer to the English Version of this knowledge base article for up-to-date information.
  2. Reboot the server.
  3. Then, click the drop-down box next to "Snapshot provider" and set it to "System - Use Microsoft Software Shadow Copy Provider".
  4. Type VSSADMIN LIST PROVIDERS Find the Provider ID for the Backup Exec VSS Provider (see screenshot below - this only shows the Microsoft VSS Provider).
  5. Marked as answer by Jeff RenModerator Tuesday, October 18, 2011 2:52 AM Monday, October 17, 2011 4:58 AM Reply | Quote Moderator All replies 0 Sign in to vote Hi,
  6. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES
  7. To fix such issues, free up some space on the C: drive and retry backups.       Terms of use for this information are found in Legal Notices.

    Related
  8. Create/Manage Case QUESTIONS?

Most probably Symantec Backup Exec is not able to interact properly with the writes and bringing them to a failed state. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. No Yes Did this article save you the trouble of contacting technical support? Backup Exec 2010 R3 Sp2 FAQ 000137 - How to get a count of items per folder in a specific mailbox using PowerShell User Rating:/2 Written by Dejan Foro Jun 05, 2015 at 08:05 AM

What does the Windows Event Viewer say? Backup Exec 2010 Download Join our community for more solutions or to ask questions. If so, a reboot normally clears up most VSS errors. Do any of the writers show errors or show as unstable?

Unless they persist. Upgrade Backup Exec 2010 To 2012 Symantec said it is a problem with VSS writer issue. The first was the Microsoft Software Shadow Copy Provider which I wanted to use. Open a command prompt.Type "vssadmin list providers"If nothing is returned, then there is most likely an issue with VSS that will most likely need assistance from Microsoft to resolve You can also

Backup Exec 2010 Download

This seemed to work for me but not might be the case for others. Secondly, in case the issue is unresolved and the Writer continues to show failed status, please refer to this article to re-register VSS writer. Backup Exec 2010 Error 1603 Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Backup Exec 2010 End Of Life This can be beneficial to other community members reading the thread.

User Rating:/0 Written by Dejan Foro Oct 29, 2015 at 06:49 PM We are growing! this contact form I hope this helps 0 LVL 13 Overall: Level 13 Message Expert Comment by:Kini Pradeep2009-11-25 I am seeing a similar issue. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).  Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. I'm grabbing one of our Tech Support Green Guys to help you.  Stay tuned... 1 Chipotle OP LMosla (Symantec) May 15, 2014 at 3:01 UTC Brand Representative for Backup Exec 2010 Administrator's Guide

It can almost always be resolved with a reboot of the exchange server.  If you cannot reboot start and stop the backup exec services on the exchange box and the box Sorry, we couldn't post your feedback right now, please try again later. So I did a little searching and thought I'd share the manual removal process for the Symantec Provider (and ultimately what was the fix for my error). http://sovidi.com/backup-exec/backup-exec-snapshot-provider-error-0xe000fed1.php Thus creating the backup exec writer status error.

Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc. Backup Exec 2010 System Requirements In order to check whether the provider service is starting in time, do we have any debug logging to be enabled ? Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Featured Post IT, Stop Being Called Into Every Meeting Promoted by Highfive Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able OR   Final error: 0xe000fed1 - A failure occurred querying the Writer status. Backup Exec 2010 Server Paused Reader InteractionsComments Srijith says June 23, 2015 at 3:09 pm Hi Gareth, I have a situation here.

V-79-57344-65233 - AOFO: Initialization failure on: "\\"Server"\System?State". This is the only way I was able to bypass this issue. You may also want to do a reegistering of dlls. http://sovidi.com/backup-exec/backup-exec-snapshot-provider-error-the-device-cannot-be-found.php About Gareth GudgerGareth is a Microsoft MVP specializing in Exchange and Office 365.

not so much. V-79-57344-34110 - AOFO: Initialization failure on: "\\MAGDC01\System?State". When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. Thank You!

However, when I uninstalled the Remote Agent and rebooted the provider remained. Join Now For immediate help use Live now! Amazing book! Join the community Back I agree Powerful tools you need, all for free.

Log onto the source computer that is reporting the error. Veritas does not guarantee the accuracy regarding the completeness of the translation. Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Open the Registry Editor.

Have you seen the following articles and solutions?   http://www.symantec.com/docs/TECH64330  http://www.symantec.com/docs/TECH27875 1 Jalapeno OP DAMS14 May 15, 2014 at 3:04 UTC Server 2008 R2 Enterprise, no I havent Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.Check the Windows Event Viewer for details. http://www.symantec.com/connect/forums/snapshot-provider-error-0xe000fed1-failure-occurred-querying-... 1 Jalapeno OP DAMS14 May 15, 2014 at 12:41 UTC No luck, still have the same errors after a service restart on exchange and a reboot of Reinstall the Backup Exec Remote Agent (do not check Advanced Open File Option).

Sorry, we couldn't post your feedback right now, please try again later. The content on this website will not be update any more and the existing FAQ articles will be gradually moved to the new one. Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview I have also tried to re register the vss writer last night and it still will fail even after the re registering.

AOFO used: Microsoft VSS.