Error 33152
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 backup exec 33152 adamm mover error 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 Italiano 日本語 한국어 Português adamm mover error deviceio backup exec Español USA Site: Veritas Veritas PartnerNet Backup Exec Device and Media Service fails to start with error 0xe0008144 and Event ID 33152 is logged in event id 33152 backup exec 2014 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 sign in to set up your subscription. Close
Event Id 33152 Backup Exec 15
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 For Windows\BEDatabase Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properl
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 adamm mover error: deviceio: ndmpsendrequest->connection error to up with quite a few of them. If ten years ago it e_pvl_db_lost_connection 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 https://www.veritas.com/support/en_US/article.TECH129977 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 Description:Adamm Database Error:
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event https://community.spiceworks.com/windows_event/show/90-backup-exec-33152 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 backup exec 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 adamm mover error 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,506 Views Others from Backup Exec 34113 57755 33808 33919 58068 57476 57860 34114 See More IT's easier with help Join mill