Home > Backup Exec > Backup Exec Error 33152

Backup Exec Error 33152

Contents

You may also refer to the English Version of this knowledge base article for up-to-date information. I've had this issue before, but at the time there were a bunch of Error 9s in the System log. Register Hereor login if you are already a member E-mail User Name Password Forgot Password? read more... Check This Out

Check with this registry values. 6.  If issues persists and media server is Windows 2003, then repair the Microsoft Data Access Components (MDAC) per the following technote: www.symantec.com/docs/TECH53595   Terms Now open up the SQL Server Configuration Manager and restart the instance of SQL Server hosting your Backup Exec database. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml EventID 34113 Backup Exec Alert: Job Failed (Server: "Server1") (Job: "Daily Backup") Daily Backup -- The job failed with the following error: The

Event 33152 Backup Exec

There was an error processing your information. Error = ERROR_NOT_READY Drive = "Drive 1" {A2B872F4-4681-4D45-B6BB-4FDE132C962E} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) I ran a second cleaning job on the same autoloader, at LEARN MORE Suggested Solutions Title # Comments Views Activity disable flow control on VMkernel interfaces tagged for Virtual SAN traffic 4 49 73d Run test on Flash Drive 2 TB 5

  1. By submitting you agree to receive email from TechTarget and its partners.
  2. As Craig suggested earlier, please follow http://www.symantec.com/docs/TECH24414 as that will lead you through a likely solution. 0 Kudos Reply I am having the same issue, pdg0306 Level 2 ‎05-20-2013 08:19 AM
  3. Following Share this item with your network: Event Id33152Event SourceBackup ExecDescriptionAdamm Database Error: Error = Server = "" Active Node = "" Instance = "BkupExec" Database = "Event InformationCAUSE: This error
  4. Theme is Kirumo Home Contact Me
Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses!
  • I checked to make sure SQL Server which hosted the BE database was running, and it was.
  • Leave them as they are for now. 6) Open the Removable Storage Manager to verify that the library and drives are there.
  • Trying running the backup job... 0 LVL 9 Overall: Level 9 Storage Software 3 Message Accepted Solution by:iCoreKC2007-06-19 Here is what I do in these cases.
  • Privacy Follow Thanks!
  • Is the corresponding Event in the Event Viewer Event ID 33152 by chance??
  • Then stop all the backup exec svcs. We'll send you an e-mail containing your password. Error reported: A tape read/write error has occurred. Adamm Mover Error Deviceio Backup Exec Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem After a successful Backup Exec installation the Backup Exec Device & Media Service fails

    Connect with top rated Experts 9 Experts available now in Live! Backup Exec Error 57665 Power up the tape device. Comments: Anonymous This helped me: EV100273 (Tape Drive Configuration Settings available in Backup Exec). By comparison, I have had successfull differential and full backups run (even one last night) and this error does not occur.

    I've tried using OEM and Veritas drivers. Event Id 33152 Backup Exec 2014 Which, didn't resolve the problem. Great care should be taken when making changes to a Windows registry. It is possible that updates have been made to the original version after this document was translated and published.

    Backup Exec Error 57665

    You may also need to check for problems with cables, termination, or other hardware issues. Three identical errors appeared again in Event Viewer. Event 33152 Backup Exec Clean the tape drive, and then try the job again. Backup Exec 33152 Adamm Mover Error Sysprep is a utility developed by Microsoft to facilitate the ma… Storage Software How do I manage my private encryption key with Carbonite Server Backup?

    Error = ERROR_NOT_READY Drive = "Drive 1" {A2B872F4-4681-4D45-B6BB-4FDE132C962E} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) Error #3) Date: 8/1/2009 Time: 1:17:28PM Type: Error User: N/A Computer: his comment is here See example of private comment Links: Veritas TechNote ID: 264273, Veritas Support Document ID: 280508, Veritas Support Document ID: 270568 Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue When I arrived at work Monday morning, BackupExec told me that the cleaning job ran normally and completed. Thanks. [Reply] Reply October 1, 2010 at 8:12 pm aparadekto says: Hey, I can't view your site properly within Opera, I actually hope you look into fixing this. [Reply]John Reply:November 5th, Backup Exec Event Id 33152 Adamm Database

    It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.  2. Unlock and inventory jobs run OK. We'll let you know when a new response is added. this contact form Error = ERROR_IO_DEVICE Drive = "Dell DLT" {7A0C1DBD-D245-4FA1-A01D-D9E4B3EB67DD} Media = "" {00000000-0000-0000-0000-000000000000} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1)

    Nov 21, 2011 Adamm Database Error: Driver Connect Failure!

    Thanks. Event Id 33152 Backup Exec 15 Privacy Improve This Answer Improve This Answer Processing your response...

    Discuss This Question:   There was an error processing your information. Please try again later.

    x 5 EventID.Net Event details: Adamm Mover Error: GetDriveInfo Failure!

    VERITAS Software is committed to product quality and satisfied customers. This is because the media server was installed with CASO/MMS option and later it was not removed from CASO/MMS completely. Power down the tape library. Adamm Mover Error: Deviceio: Ndmpsendrequest->connection Error To After rebooting the PowerVault first and thereafter the server, the error was gone.

    I'm switching to Bacula. x 11 Private comment: Subscribers only. Please try again later. http://onlinetvsoftware.net/backup-exec/backup-exec-2012-error-33152.php Using the IBM DLT-DDS tape drive diagnostics v5.8.3, the user narrowed down the problem to a damaged tape.

    Covered by US Patent. If this doesn't work you need to check your SCSI cable and make sure you don't have a bent pin in the connector. Browse by Topic AS/400 Business Intelligence Career Development Channel Cloud Computing Compliance Consumerization Content Management CRM Data Management Database DataCenter Desktop Management Development Email Administration Hardware IT Strategy Linux Lotus Domino Event ID: 33152.  Thankfully the fix for this error is quite simple.

    Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. I have a HP DAT72x6 autoloader which I've just installed on the server. Clean the tape drive, and then try the job again. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten.

    Privacy Reply Processing your reply... I've shut down per the sequence above and now I can at least start the backup job. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We This just started happening the end of March 2013. 0 Kudos Reply please follow Larry_Fine Level 6 ‎05-20-2013 11:32 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight

    No Yes Did this article save you the trouble of contacting technical support? The pay support line will just tell you to replace all of the hardware until the problem is resolved. Check if "Database Server Name", "Database Instance Name" and " ODBC Driver Connection" Key Values are correctly set.  They should be set to: "Database Instance Name"="BKUPEXEC" (Which is the instance of Promoted by Recorded Future Enhance your security with threat intelligence from the web.

    If so, there is a known issue with certain tape libraries with Version 9.1 that an upgrade to 10d will correct. 0 Message Author Comment by:bevco72007-06-19 Hmmm... Make sure you have the latest firmware installed. Concepts to understand: What is Adamm? Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

    In addition, the problem seems to have tapered off as of mid-December. Afterwards, the errors didn't reoccur anymore. No Yes Did this article save you the trouble of contacting technical support?