Error Id 33152 Backup Exec
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support backup exec 33152 adamm mover error Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT event id 33152 backup exec 2014 About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us
Adamm Mover Error Deviceio Backup Exec
English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device & Media Service fails to
Event Id 33152 Backup Exec 15
start and reports the following error message: 0xe0008144 Article:000013727 Publish: Article URL:http://www.veritas.com/docs/000013727 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 to Subscribe Please sign in to set up e_pvl_db_lost_connection your subscription. 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 to start and reports the following error message: 0xe0008144 The the Backup Exec SQL instance service is running (MSSQL&BKUPEXEC) A quick test connection to the Backup Exec SQL instance is working fineFor more information see (www.symantec.com/docs/TECH24708) A different connection test to the Backup Exec instance is:- Go to Start, Administrative Tools, Data Source (ODBC)- Go to the System DSN tab- Select Add- Select SQL Server- Click Finish This test failed with the following error:Specified driver could not be loaded due to system error 126 (SQL Server) Error Message Following Event is seen in the Event Viewer: Event Type: ErrorEvent Source: Backup ExecEvent Category: (65535)Even
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 https://www.veritas.com/support/en_US/article.000013727 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 on any of the servers. read more... Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error Description:Adamm Database Error:
? Ask a question, help others, and get answers from the community Discussions Start a thread and discuss today's topics with top experts Blogs Read the latest tech blogs written by http://itknowledgeexchange.techtarget.com/itanswers/adamm-error-with-backupexec-11d/ experienced community members ADAMM error with BackupExec 11d Lonewolfbw 525 pts. Tags: Thanks! https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 We'll email youwhen relevant content isadded and updated. Following Follow Backup Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Backup Exec Thanks! We'll email youwhen relevant content isadded and updated. Following Follow Symantec Backup Exec 11D Good morning, I have just taken over the position of backup backup exec operator in my department, so please forgive any seemingly obvious questions. I have received several puzzling errors in the past few days, and hope I can get some answers as to what is causing them. First, this is the setup I am using: We have a Dell PowerEdge 2950 as our backup server, using BackupExec 11d (Media Server version 11.0, Rev. 7170) - installed id 33152 backup updates Service Pack 4, Hot Fixes 62, 63, 64, 65. Our current configuration is to run a full backup of our main disk array/fileserver on Friday, at 11:00PM. Then, a differential backup will run on M, T, W, Th at 11:00PM. I first noticed a problem when I came in on Saturday and found the following error after the full backup job had 'finished': Job ended: Saturday, August 01, 2009 at 12:28:00 PM Completed status: Failed Final error: 0xe00084ec - A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues. Final error category: Backup Media Errors For additional information regarding this error refer to link V-79-57344-34028 Backup- \192.168.0.152M: LRDCVOLStorage device "Drive 1" reported an error on a request to write data to media. Error reported: A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape dri
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 33152 (Error) Source: Backup Exec How important is this event? (3 votes) 1 2 3 4 5 not important very important Description Adamm Database Error: Error = Server = "" Active Node = "" Instance = "BkupExec" Database = "" Adamm Database Error: Error = Server = "" Active Node = "" Instance = "BkupExec" Database = "" Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages message string data: Adamm Mover Error: DeviceIo: 00:00:08:00 - Retry Logic: Original settings restored on device: QUANTUM ULTRIUM 4
Jan 15, 2010 Adamm Mover Error: Write Failure! Error = ERROR_CRC Drive = "HP Ultrium" {7820F5AA-1854-49B6-A0A8-D88F3031876C} Media = "000010L3" {AD17CD33-B409-48A9-ADDA-E15C76A597E1} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(1), ScsiPass(1) Dec 29, 2010 Adamm Mover Error: GetDriveInfo Failure! 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! Error = ERROR_DATABASE_DOES_NOT_EXIST Server = "ESTER" Active Node = "" Instance = "BKUPEXEC" Database = "BEDB" May 15, 2013 Comments Pure Capsaicin May 26, 2011 peter Non Profit, 101-250 Employees all help greatly appreciated Pimiento Jul 18, 2011 Craig1286 Manufacturing We have found with this that power cycling the tape drive resolves this issue. Probably indicating that there is a loss of comms with the SCSI device Add your comments on this Windows Event! Join the IT Network or Login. Stats Reported 7 years ago 2 Comments 7,515 Views Others from Backup Exec