Backup Exec 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 Licensing Process ABOUT About Corporate Profile Corporate Leadership event 33152 backup exec Newsroom Research Exchange Investor Relations Careers Legal Contact Us English ä¸æ–‡(简体) English backup exec error 57665 Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device and Media Service backup exec 33152 adamm mover error fails to start 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
Backup Exec Event Id 33152 Adamm Database
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 Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Device and Media Service fails adamm mover error deviceio backup exec 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 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
Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via event id 33152 backup exec 2014 the Splunk Universal Forwarder. read more... Event ID: 33152 Source: Backup Exec Source: Backup
Event Id 33152 Backup Exec 15
Exec Type: Error Description:Adamm Database Error:
Adamm Mover Error: Deviceio: Ndmpsendrequest->connection Error To
Database = "
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 https://community.spiceworks.com/windows_event/show/90-backup-exec-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: backup exec 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 33152 backup exec 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,483 Views Others from Backup Exec 34113 57755 33808 33919 58068 57476 57860 34114 See More IT's easier with help Join millions of IT pros working smarter and faster togeth