Error Event 33152
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer backup exec 33152 adamm mover error Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate
Backup Exec Event Id 33152 Adamm Database
Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français adamm mover error deviceio backup exec Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device and Media Service fails to start with error 0xe0008144 and Event event id 33152 backup exec 2014 ID 33152 is logged in Event Viewer showing Adamm Database Event: Open Database Connection Failed Article:000007179 Publish: Article URL:http://www.veritas.com/docs/000007179 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
Event Id 33152 Backup Exec 15
sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Device and Media Service fails to start with error 0xe0008144 and Event ID 33152 is logged in Event Viewer showing Adamm Database Event: Open Database Connection Failed!. Error Message Error 0xe0008144 : 0xe0008144 Attempt to start Device and Media Service fails with the above mentioned error. Following Event is seen in the Event Viewer: Source : Backup exec Type : ErrorEvent ID : 33152Description :Adamm Database Event: Open Database Connection Failed!Error = ERROR DATABASE_DOES_NOT_EXISTServer = "LOCAL"Active Node = ""Instance = "BACKUPEXEC"Database = "BEDB"Connection String = "DRIVER=SQL Server:SERVER=LOCAL\BACKUPEXEC:DATABASE=BEDB:App=BEWS PVL"The Backup Exec Device and Media Service could not connect to the specified database. Ensure that the specified database is running. Solution 1. Go To Registry hive HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec Fo
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange adamm mover error: deviceio: ndmpsendrequest->connection error to Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano e_pvl_db_lost_connection 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device & Media Service fails to 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 https://www.veritas.com/support/en_US/article.TECH129977 Your Profile Logout Sign in to Subscribe Please sign in to set up 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 https://www.veritas.com/support/en_US/article.000013727 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)Event ID: 33152Computer: Server Name Description:Adamm Database Event: Open Database Connection Failed!Error = ERROR_DATABASE_DOES_NOT_EXISTServer = "Server Name"Active Node = ""Instance = "BkupExec"Database = "BEDB"Connection String = "DRIVER=SQL Server;SERVER=Server Name\BkupExec;DATABASE=BEDB;App=BEWS PVL" The Backup Exec Device and Media Service could not connect to the specified database. Ensure that the specified database is running, and then try starting the service again. If this is a remote database, also ensure that the firewall is properly configured. Event Type: InformationEvent Source: Backup ExecEvent Category: (65535)Event ID: 33152Computer: Server Name Description:Adamm Database Event: Open Database Connection ...Error = S_OKServer = "Server Name"Active Node = ""Instance = "BkupExec"
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for https://www.experts-exchange.com/questions/22644923/Backup-Exec-stuck-in-Loading-Media-state-error-33152-in-Windows-Event-Viewer.html Help Receive Real-Time Help Create a Freelance Project Hire for http://itknowledgeexchange.techtarget.com/itanswers/adamm-error-with-backupexec-11d/ a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Backup Exec stuck in Loading Media state, error 33152 in backup exec Windows Event Viewer Want to Advertise Here? Solved Backup Exec stuck in Loading Media state, error 33152 in Windows Event Viewer Posted on 2007-06-19 Storage Software 2 Verified Solutions 5 Comments 10,417 Views Last Modified: 2013-12-01 I'm using Backup Exec 9.1 on a Windows 2003 Server. I have a HP DAT72x6 autoloader which I've adamm mover error just installed on the server. Backup, cleaning and restore jobs won't run. Unlock and inventory jobs run OK. When trying to run the other jobs, Backup Exec sits in a "Loading Media" state. In the Windows event log, I get a set of three messages every few minutes. These are: Message 1: -------------- Event Type: Warning Event Source: Backup Exec Event Category: Devices Event ID: 33152 Date: 20/6/07 Time: 11:09:02 User: N/A Computer: BNEFILES1 Description: Adamm Mover Error: Unload Status Retry! Error = ERROR_NOT_READY Drive = "D51 Drive" {2FF4F000-7C59-4E09-A09F-F
? 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 experienced community members ADAMM error with BackupExec 11d Lonewolfbw 525 pts. Tags: Thanks! 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 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 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 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. V-79-57344-34028 - A tape read/write