Home > An Error > Event Id 33808 Backup Exec 2012

Event Id 33808 Backup Exec 2012


Error=5 backup samba cifs backupexec share|improve this question edited Jun 4 '11 at 22:54 KCotreau 2,64431223 asked Dec 30 '10 at 20:26 ewwhite 150k47294573 check this out to see Changer: CreatePath() CreateDirectory1 failed (\\storage1\vol1_backup\). Review the event logs for more information.Final error category: Backup Device ErrorsFor additional information regarding this error refer to link V-79-57344-34030 Backup- device "Removable Backup-to-Disk Folder 1" reported an error Links Technical Support Symantec Training Symantec.com Home Symantec BU Exec 2014 - Event ID 33808 - Cannot create B2D by Bad_Ass_B-o-B on Aug 17, 2014 at 4:28 UTC | Data Backup have a peek at this web-site

I can browse to the share just fine from within Windows, but Backup Exec fails to create the B2D folder with different variants of a Unable to create new backup folder. If updates are available, click the Install Updates button. x 51 EventID.Net See "Veritas Support Document ID: 268991" for information regarding this event. No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities

Event Id 33808 Backup Exec 2012

Pure Capsaicin Feb 13, 2016 peter Non Profit, 101-250 Employees cheers Add your comments on this Windows Event! This error may be caused by a failure of your computer hardware or network connection. Error reported: The specified network name is no longer available.An error occurred while processing a B2D command. The below procedure will recreate the B2D on the same location creating new folder.cfg and changer.cfg files and all the content (.bkf) will be re-inventorized.

x 12 Aram Iskenderian See Veritas TechNote ID: 236295 to solve this problem. Direct Support Forums Technical Hardware QNAP issues as a B2D Device? + Post New Thread Results 1 to 6 of 6 Hardware Thread, QNAP issues as a B2D Device? Click on the Backup Exec-associated entry. How To Run B2d Test Backup Exec Error=5 For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml Add link Text to display: Where should this link go?

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? How to deal with a very weak student Change a list of matrix elements Describe that someone’s explanation matches your knowledge level Is this bad OOP design for a simulation involving Yes, of course I'm an adult! https://www.veritas.com/support/en_US/article.TECH136971 However, if not sure, then avoid deleting anything and contact BE technical support team.     Terms of use for this information are found in Legal Notices.

Related Articles Article

Follow the steps in the Wizard to choose a restore point. Changer: Movemedium() Attempt To Lock Slot Failed Deleting the backup to disk folder from Backup Exec does not delete the backed up data (.bkf files), the data is untouched on the actual location on the drive where the backup Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating system. Event ID 33808 Description: An error occurred while processing a B2D command.


To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to Error 5 (eg. https://community.spiceworks.com/topic/562783-symantec-bu-exec-2014-event-id-33808-cannot-create-b2d There should be an hotfix for this issue by now but didn't saw any messages jet. Event Id 33808 Backup Exec 2012 The file is then saved with a .reg file extension. Changer: Createpath() Createdirectory1 Failed (\\?). Error=123 more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

User canceled a Physical Volume Library operation Event ID 33808 is logged by Backup Exec when a Backup-to-Disk (B2D) command fails. http://dukesoftwaresolutions.com/an-error/v-379-33808.html In the results, click System Restore. How is the Gold Competency Level Attained? We do not claim any responsibility for the results of the actions taken from the content linked below - complete these tasks at your own risk. An Error Occurred While Processing A B2d Command Error 13

SEO by vBSEO ©2011, Crawlability, Inc. Step 4: Update Your PC Device Drivers 5 errors can be related to corrupt or outdated device drivers. Email Address (Optional) Your feedback has been submitted successfully! Source Disk Cleanup will begin calculating how much occupied disk space you can reclaim.

Installing the wrong driver, or simply an incompatible version of the right driver, can make your problems even worse. B2dtest Follow the on-screen directions to complete the uninstallation of your Error 5-associated program. Use Registry Editor at your own risk.

Step 9: Perform a Clean Installation of Windows Caution: We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve Error 5 problems.

Drive: ReadFMTable() SFMB Not Found (\\qnapbox\be\core\B2D007038.bkf). On the Nexenta system, I needed to create an Active Directory ID mapping of [email protected] == root (or any other local Nexenta user), then create an ACL for that user for The best part is that repairing registry errors can also dramatically improve system speed and performance. 33808 Zip Code He couldn't help me at all.

DriverDoc's proprietary One-Click Update™ technology not only ensures that you have correct driver versions for your hardware, but it also creates a backup of your current drivers before making any changes. Type "sfc /scannow" and hit ENTER. LinkBack LinkBack URL About LinkBacks Bookmark & Share Digg this Thread!Add Thread to del.icio.usBookmark in TechnoratiTweet this threadShare on Facebook!Reddit! have a peek here Send PM SHARE: + Post New Thread Similar Threads Set USB audio as default sound device By Zoom7000 in forum Promethean Direct Support Replies: 10 Last Post: 12th January 2012,

To fix this problem first make sure that the drives are offline. Uninstall both drivers. 3. Type "command" in the search box... It is possible that updates have been made to the original version after this document was translated and published.