Backup to Tape Job to the HPE LTO tape drives fails with "Tape error: '1117'" after upgrade to Veeam Backup & Replication 9.5 Update 4b

KB ID: 2983
Published: 2019-07-31
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Backup (and other operations) to HPE LTO tape drives may constantly fail after installation of Veeam Backup & Replication 9.5 Update 4b (9.5.4.2866).

Veeam fails to connect to the tape drive and returns the following errors:
 
[18.07.2019 15:49:24] <01> Warning TapeDrive alert: The tape drive has a problem with the application client interface
...
[18.07.2019 15:49:58] <01> Error Tape error: '1117' (The request could not be performed because of an I/O device error) (Veeam.Backup.Common.CCppComponentException)
[18.07.2019 15:49:58] <01> Error in c++: TapeHandle failed to get tape drive parameters.
[18.07.2019 15:49:58] <01> Error in c++: Tape initialization FAILED.

However, the tape drive is recognized correctly in the device manager and no hardware related errors are reported in the Windows System log.

Cause

When Veeam is configuring the hardware encryption, it sends an incorrect command to the tape drive.
This brings the tape drive into the faulty state.

Solution

To solve the issue, apply the hotfix:
    1. Download the hotfix.
    2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866.
    3. Make sure that no jobs are running, close the console, and stop all Veeam services.
    4. Right-click on the installation file and click "Run as administrator"
    5. Go through the wizard to install private fix.
    6. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.
    7. Disconnect the tape drive from the power for a couple of minutes.
    IMPORTANT: Mere reboot of the tape server does not solve the issue.


    UPDATE: It was discovered that in distinguishably rare situations this issue may affect other hardware Vendors, please open a support case if you encountered this one.

    More information

    DOWNLOAD PRIVATE FIX


    MD5 for kb2983.zip: 567db99e79fb6bd95251deb769d90238
    SHA-1 for kb2983.zip: 0c8ad6b3c0841402c8da1e05e1acbb7e0bfcadf8
    Send Article Feedback
    To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

    Spelling error in text

    This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
    Thank you!

    Thank you!

    Your feedback has been received and will be reviewed.

    Oops! Something went wrong.

    Please try again later.

    KB Feedback/Suggestion

    This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

    By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
    This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
    Verify your email to continue your product download
    We've sent a verification code to:
    • Incorrect verification code. Please try again.
    An email with a verification code was just sent to
    Didn't receive the code? Click to resend in sec
    Didn't receive the code? Click to resend
    Thank you!

    Thank you!

    Your feedback has been received and will be reviewed.

    error icon

    Oops! Something went wrong.

    Please try again later.