Backup Exec 33152 Error
Contents |
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 backup exec event id 33152 adamm database Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch
Adamm Mover Error Deviceio Backup Exec
Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device and Media Service fails to start
Event Id 33152 Backup Exec 2014
with error 0xe0008144 and Event 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
Event Id 33152 Backup Exec 15
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 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 adamm mover error: deviceio: ndmpsendrequest->connection error to 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 For Windows\BEDatabase Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes. 2. Check if "Database Server Name", "Database Instance Name" and " ODBC Driv
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 e_pvl_db_lost_connection 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 https://www.veritas.com/support/en_US/article.TECH129977 on these servers is a tedious, time-consuming process. 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 on any of the servers. read more... Event ID: 33152 Source: Backup Exec Source: Backup Exec Type: Error http://www.eventid.net/display-eventid-33152-source-Backup%20Exec-eventno-3488-phase-1.htm Description:Adamm Database Error:
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for https://www.experts-exchange.com/questions/22644923/Backup-Exec-stuck-in-Loading-Media-state-error-33152-in-Windows-Event-Viewer.html 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 Windows Event Viewer Want to Advertise Here? Solved Backup Exec stuck in Loading Media state, error 33152 in Windows Event Viewer backup exec Posted on 2007-06-19 Storage Software 2 Verified Solutions 5 Comments 10,400 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 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 event id 33152 "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