Home > Unexpected Error > Unexpected Error Calling Routine Regsavekeyexw

Unexpected Error Calling Routine Regsavekeyexw

The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Follow this article to find the pre-requisites/services/vss-providers, and other related configuration areas that need to be checked on affected systems.3. ' Unexpected error calling routine RegSaveKeyExW' : Seems to be a If not, why not? The backup application stops responding when you perform a backup that uses a volume snapshot in Windows Server 2003 with SP1 http://support.microsoft.com/kb/923628 A Volume Shadow Copy Service (VSS) update package is check over here

if it is, take the following steps to troubleshoot your issue: Would you please view and request hotfixs that is mentioned in the following Microsoft KB article and apply on the Retain evidence of this with email archiving to protect your employees. See MSW2KDB for more details. If they start to work, then they usually work all the time.But then I have a couple of VADP backup clients, that just doesn't seem to work.

Labels: 2010 Backing Up Backup and Recovery Backup Exec 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Sign Up Now! Join Now For immediate help use Live now!

  • Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Volume Shadow Copy Service error: Unexpected error calling
  • dfroelicher posted Jul 28, 2016 Recovery errors 1002 and 1005,...
  • BackupExec "Guillaume Tamisier" wrote: > But if I turn off Shadow Copy, the backup of opened files will fail.
  • Another workaround is to install vmware tools without VSS support, but I don't want to do that.
  • Details: Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.'.* :guest/client.*FULL* 80405:nsrvadp_save: Could not create Snapshot for
  • Marked as answer by Jeff RenModerator Friday, September 30, 2011 9:05 AM Edited by Jeff RenModerator Friday, September 30, 2011 9:06 AM Wednesday, September 28, 2011 9:52 AM Reply | Quote
  • If I backup the system without saving the system state, it works without any problem.
  • Log onto the Backup Exec Central Administration Server.
  • But the EventID in the original post may be coincidental.

On Windows 2008 R2, you may see hresult 0x80070005 (access is denied), again when writing to the registry. If this is the case, you'll need to identify which user the VSS service is running as, and grant it permissions to the Services\VSS\Diag registry key. From a newsgroup post: "It appears that the COM+ subsystem is not correctly installed on your machine. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry."This seems to appear right before Backup Exec has

hr = 0x800703f8. >> >> Event Type: Error >> Event Source: VSS >> Event ID: 5013 >> Description: >> Volume Shadow Copy Service error: Shadow Copy writer EventLogs called >> routine Unfortunately I did not get any further details at the time but I'm trying again to see if I can get more info on exactly what the VSS issue was, symptoms, vssadmin version: 5.2.3790.3959 please take a look. http://www.winvistatips.com/threads/volume-shadow-copy-error-with-ntbackup.544203/ I found the answer was to restart the services attached to these writers.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Volume Shadow Copy Service error: Unexpected error... Could it be a Citrix issue? If I backup >> the >> system without saving the system state, it works without any problem. >> >> Any idea ? >> >> Thanks. >> -- >> Guillaume Tamisier >> Re: Failing VADP Backups (7.6sp2(.1)) tonyk Aug 12, 2011 5:20 AM (in response to AllanW) (AllanW)Actually this is not a fix at least for the second problem.

Basically, it is under the following section of the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000} The values for OwnerSID and TypeLib are probably wrong. https://vox.veritas.com/t5/Backup-Exec/Backup-says-unable-to-query-writer-status-but-all-writers-on/td-p/478650 Please do not disable the COM+ Event System or Volume Shadow Copy Service; this will not fix the real problem". Join & Ask a Question Need Help in Real-Time? Re: Failing VADP Backups (7.6sp2(.1)) tonyk Oct 5, 2011 3:48 AM (in response to tonyk) Removing the vmware-tools VSS component did help!

However, sometimes user accidentally erased their important data from the Storage devices. http://centralpedia.com/unexpected-error/unexpected-error-calling-routine-multi-interface-event-control.html Best Regards, Jeff Ren 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 Re: Failing VADP Backups (7.6sp2(.1)) tonyk Sep 28, 2011 11:21 PM (in response to ddunn) Interesting reading and it has been updated since I last read it. A reboot will fix it until the next incremental backup.

x 46 EventID.Net Re-registering the Shadow Copy dlls may help - see EV100108 ("Volume Shadow Copy Service and DLLs"). The first step is to acquire the necessary licen… Storage Software Windows Server 2008 VMware Disaster Recovery Setting the Media and Overwrite Protection Levels in Backup Exec 2012 Video by: Rodney Backup Exec errors... this content Edited by Jeff RenModerator Friday, September 30, 2011 2:14 AM Thursday, September 29, 2011 3:56 AM Reply | Quote Moderator 0 Sign in to vote server after reboot, error gone until

Similar Threads ntbackup / wsus? Details: 'An error occurred for task 'CreateSnapshot_Task'. Secondly, if the problem continues , I want to know the info as bellows: What kinds of OS of your server?windows2003?

So I think that the problem is not here...

I reboot the server and the problem goes away for a random about of days.I also get another error message in the eventlog every minute or so until the server is hr = 0x80070422", then your VSS service is disabled, and you almost certainly have event ID 39 telling you this. Adding the Backup Exec service account to the local Administrators group resolved the issues. I have a Windows 2003 Server SP1 with veritas 10 as the backup system.

What I find confusing is that when I run vssadmin list writers on the two servers everything comes up as Stable with no errors. Ensure to click Custom Install.Deselect VSS.If this differs from what you did, can you please post back?Debbie Report Abuse Like Show 0 Likes (0) 1 2 Previous Next Go to original I hope this helps ! 0 Message Author Comment by:admoortown2007-05-11 Rebooted the server and it seems to have fixed it - although i tried that already. have a peek at these guys Go to Solution Backup says unable to query writer status but all writers on target system are stable CharAznable0079 Level 4 ‎04-04-2012 10:13 AM Options Mark as New Bookmark Subscribe Subscribe

If it happens to run a full backup before the next incremental backup, it will appear to have resolved itself completely. I found CharAznable0079 Level 4 ‎04-13-2012 07:33 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content These didn't work. Thanks. All rights reserved.PrivacyLegalContactUnited StatesProductsSolutionsShopSupportServicesPartnersCompanyMy AccountLog InBROWSE PRODUCTSStorageServersConverged InfrastructureData ProtectionSecurityNetworkingContent ManagementDell Products for WorkSearch Products by NameProducts A-ZShop EMC ProductsProduct CommunitySoftware DownloadsLive ChatContact SalesCall 1-866-438-3622Call 1-866-438-3622Storage CategoriesOverviewEnterpriseEntry & MidrangeSoftware DefinedAll-FlashCloudManagement & NetworkingStorage

These didn't work. As I stated I have this problem also on a 2008 R2 server. Final error category: Resource Errors.V-79-57344-65233 - AOFO: Initialization failure on: "System?State". Locate partners—or learn about becoming one.Find EMC PartnersEMC Business Partner ProgramBecome an EMC ResellerPartner CommunityPartner PortalRSA PartnersDell PartnerDirectContact UsPartner with EMC today.Live ChatContact SalesCall 1-866-438-3622Call 1-866-438-3622Company InformationKeep up with the news,

I'm also following up to have the details of the workaround doc'ed in the NetWorker VMWare Integration Guide on Powerlink:The steps below require a reboot of the virtual machine. Thanks. -- Guillaume Tamisier Guillaume Tamisier, Mar 18, 2005 #1 Advertisements TheThaiTech Guest Turn off Shadow Copy before running ntbackup. "Guillaume Tamisier" wrote: > Hi, > > When I try Why would this one be different from all the others, which mainly are named as the dns without FQDN?The name in networker is the same as dns name. x 40 Anonymous I fixed this problem by installing MSXML 3.0 and MSXML 4.0.

Suggested Solutions Title # Comments Views Activity PIng command and its use 9 73 66d Brocade fabric merge at different FOS levels 2 46 42d Client backup and data retention? 3 If you're noticing paged pool leaks from tag MntA on Server 2003, install the hotfix from MS KB940307. Any idea ? Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking

Confirm and manage identities. This problem is unrelated with VSS. This is defined as An I/O operation initiated by the registry failed unrecoverably. Ultimately, prevent IP theft, fraud, and cybercrime.Explore products and solutions from RSA.Visit RSA.comOverviewEnterprise Network HardwareSwitchesRouters and Wireless NetworkingOverviewDocumentumLEAPInfoArchiveOverviewDell LaptopsDell DesktopsDell Thin Clients and VDI ProductsNo results foundNo results foundMODERN DATA CENTERGet