Device Error 58053
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 "robotic library hardware error" Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 tech24414 한국어 Português Español USA Site: Veritas Veritas PartnerNet Event ID 58053: "Robotic library hardware error. The robotic library has veritas reported a general hardware error condition..." Article:000024967 Publish: Article URL:http://www.veritas.com/docs/000024967 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 Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Event ID 58053: "Robotic library hardware error. The robotic library has reported a general hardware error condition. Manual intervention, calibration, etc. may be required. This may be a device related hardware problem, or it may be some other hardware problem (i.e. SCSI card/bus etc.). The library and drive states have been set to offline." Error Message Event ID: 58053Source: Backup ExecType: ErrorDescription: Backup Exec Alert: Device Error (Server: "%server%") Robotic library hardware error.The robotic library has reported a general hardware error condition. Manual intervention, calibration, etc., may be required. or Event ID: 58053Source: Backup ExecType: ErrorDescription: Backup Exec Alert: Device Error (Server: "%server%") The robotic library hardware is offline! Error in Job log : - " V-79-40960-33045 - Physical Volume Library Drive or Robot Paused, Offline, or Disabled " Cause 1) The alert was reported in the Event Viewer Application Log because a hardware error occurred with the robotic library. 2) It may also happen if the medium changer is not recognised by the O.S. Solution 1) The alert was reported because a robotic library previously detected by Backup Exec (tm) is no longer detected. Verify the same robotic library previously detected by Backup Exec is properly cabled to the computer and the power to the robotic library is on. 2) Once the hardware error has been cor
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 Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Event ID 58053: "Library Expansion Option Violation!" is reported when starting Backup Exec Article:000024977 Publish: Article URL:http://www.veritas.com/docs/000024977 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account https://www.veritas.com/support/en_US/article.TECH23176 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 Event ID 58053: "Library Expansion Option Violation!" is reported when starting Backup Exec. Error Message Following Error is displayed in the Alerts https://www.veritas.com/support/en_US/article.TECH23196 tab of Backup Exec : The following Windows event indicates there are not enough Backup Exec (tm) Library Expansion Option (LEO) licenses for the number of drives in the computer's robotic library.Event Type: ErrorEvent Source: Backup ExecEvent Category: NoneEvent ID: 58053Date:Time:User: N/AComputer: BE-SERVERDescription:Backup Exec Alert: Device Error(Server: "BE-SERVER") Library Expansion Option Violation.This server is licensed to support 0 tape drives in robotic libraries. However, the number of tape drives currently in use exceeds the license. You must purchase additional Library Expansion Options, or disable 1 tape drive. Please refer to product documentation for more information. UMI: v-275-441 Cause Cause 1: Support for a single robotic library drive is included with Backup Exec for Windows Servers, one license each is required for all additional drives. If the license is not added, a Library expansion option violation is displayed. Cause 2: Backup Exec installed on a server connected to a SAN through more than one HBA and two SCSI path configured in the switches (Microsoft Multipath I/O (MPIO)) and not configured correctly. Solution Solution 1: According to the Backup Exec Admi
116715 Followers Follow Symantec 258485 Followers Follow Dell Symantec Backup Exec Join the Community! Creating your account only takes a few minutes. Join Now Hi, We are running BE 2010 on https://community.spiceworks.com/topic/336722-backup-exec-2010-tape-drive-hardware-is-offline windows 2003 server with Dell PV TL2000 tape library. When running a first job on BE 2010 everything seems to be working fine. But whenever we tried to run a second job, tape drive suddenly goes offline and the tape got stuck on the tape drive. And the only thing we can bring it back online and get the tape back on its slot was restarting the BE services. We don’t device error have bar codes placed on tapes, would it affect the behavior of tape library if we won’t be using bar codes? Thanks, Reply Subscribe RELATED TOPICS: Backup Exec 2010 tape drive tuning Backup Exec 2010 fails when finding bad tape. Backup Exec 2010 Tape Autoloaders and Licenses   16 Replies Anaheim OP Dave Collins May 15, 2013 at 3:58 UTC Tape drives require the drivers to be Symantec's own device error 58053 drivers for the relevant device. If you're using vendor provided drivers it will have weird side effects. You set this by configuring the tape device from within the BackupExec server, on the devices tab 1 Sonora OP jac3land May 15, 2013 at 7:45 UTC Thanks Dave for the reply. Yes, we are using symantec drivers for tape drive and the medium changer was set to unknown medium changer. Removable Storage has been disabled as well. We used tapeinst.exe on the BE 2010 to configure this. Is this where we should configure the tape drive? Thanks, 0 Anaheim OP Dave Collins May 16, 2013 at 8:48 UTC Yeah that's the one. Once in device manager as a tape device you can configure the device from within the media server itself, ensuring that the tape library is on the same driver release as the media server. 1 Jalapeno OP Donald (Symantec) May 16, 2013 at 1:29 UTC Hey jac3land, When you say you encounter issue when you kick off your second job are you talking about a job following the first or concurrent jobs ? If were talking concurrent and you have two tape drives have you acquired and input