#1 Global Leader in Data Resilience

Upgrading/Uninstalling Veeam Backup & Replication fails with
"Error 1327. Invalid Drive: [a-z]:\" or "Warning 1327. Invalid Drive [a-z]:\"

KB ID: 4166
Product: Veeam Backup & Replication | 9.5 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3
Published: 2021-05-18
Last Modified: 2021-11-12
mailbox
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

While upgrading or uninstalling Veeam Backup & Replication, the installer stops and displays either of the following messages:
Warning 1327. Invalid Drive: F:\
Error 1327. Invalid Drive: F:\
Note: The drive letter in the message may be any drive letter.
A screenshot of the warning showing the text "Warning 1327 . Invalid Drive: F:\"
A screenshot of the error showing the text "Error 1327 . Invalid Drive: F:\"

Cause

The settings in the registry for one or both of the following services are targeting a drive location that no longer exists:

  • Veeam Guest Catalog Service (VeeamCatalogSvc)
  • Veeam vPower NFS Service (VeeamNFSSvc)

The invalid registry entries often occur because during the initial installation of Veeam Backup & Replication a drive with a larger amount of free space than the C:\ drive was present. This is because the installer will detect which drive has the greatest free space and uses that for the above services. If that driver is later removed, the settings in the registry will still point to that drive. During the future upgrade process, when the upgrade installer attempts to check the existing configuration, it finds that it cannot access that drive location.

Solution

Check the following registry locations and values. Make sure the path in the registry targets a location that is available.

  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Veeam\Veeam NFS
    Value Name: RootFolder
    Default Path: C:\ProgramData\Veeam\Backup\IRCache\
  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup Catalog
    Value Name: CatalogPath
    Default Path: C:\VBRCatalog

The above "Default" paths shown are what would have been selected if there was no other drive on the Veeam server during the initial install.

Expand the section below which matches the message seen:
[Warning 1327. Invalid Drive:] during "Installing Veeam Backup Catalog..."

 

The message "Warning 1327. Invalid Drive" occurs during the upgrade process when the installer is on the stage of "Installing Veeam Backup Catalog..."

Check the registry value named CatalogPath found in the key HLM\SOFTWARE\Veeam\Veeam Backup Catalog

The value's data should be a path to an existing drive letter. If the drive letter shown does not exist, edit the entry and change only the drive letter.

Attempt the upgrade again. During the upgrade, the installer will automatically create the folder in the newly specified location and recreate the missing VBRCatalog share.

Shown is the Veeam Backup & Replication installer showing that it is on the stage where it is "Installing Veeam Backup Catalog..." and a pop-up can be seen displaying the error "Warning 1327. Invalid Drive: F:\"

Log example:

C:\ProgramData\Veeam\Setup\Temp\CatalogSetup.log

***Veeam***  Reading 'CatalogPath' from register.
***Veeam*** 'CatalogPath' is found. Its value is 'F:\VBRCatalog'.
[Error 1327. Invalid Drive:] during "Installing Veeam Backup & Replication Server..."

 

The message "Error 1327. Invalid Drive" occurs during the upgrade process when the installer is on the stage of "Installing Veeam Backup & Replication Server..."

Check the registry value named RootFolder found in the key HLM\SOFTWARE\WOW6432Node\Veeam\Veeam NFS

The value's data should be a path to an existing drive letter. If the drive letter shown does not exist, edit the entry and change only the drive letter.

Attempt the upgrade again.

The images shows the installer on the "Installing Veeam Backup & Replication Server" stage and a pop-up can be seen displaying the "Error 1327. Invalid Drive" message.

Log example:

C:\ProgramData\Veeam\Setup\Temp\BackupSrvLog.log

***Veeam***  NFSRootFolder='F:\ProgramData\Veeam\Backup\IRCache\'.
***Veeam*** Expanded NFSRootFolder='F:\ProgramData\Veeam\Backup\IRCache\'.
Contact Veeam Support
If the above troubleshooting steps do not resolve the upgrade issue, please create a case with Veeam Technical Support. https://www.veeam.com/kb1771

More Information

How to move the VBRCatalog: https://www.veeam.com/kb1453

The IRCache location is controlled within Veeam Backup & Replication by the mount server setting within a repository using the Veeam server as the Mount server.  

To submit feedback regarding this article, please click this link: 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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.