Error upgrading from 5.0 to 5.0.1 - 1327.Invalid Drive

[virtualwatts]

Greetings (of the seasonal kind),

I have downloaded and am trying to upgrade our Veeam 5.0 to Veeam 5.0.1 and am receiving the following error:

"ERROR 1327.Invalid Drive: I:\ "

The upgrade fails and closes. And no, there is not an "I:\" drive on the Veeam vm guest.
I did have failed jobs but removed them and retried - same error.

I have opened a ticket with Veeam but no response as yet - hoping someone out there has already had this error and resolved it.

Regards
Rick

[Alexey D.]

Hello Rick,

We've never seen this issue before. Please continue working with our support, we need more information.
By the way, what is the number of your ticket? I will check its status.

[virtualwatts]

Alexey -

Support # is 545209.

Searching through the Registry of the Veeam VM guest I find references from the Veeam software for i:\ drive references. I have forwarded those to support.

One group of reg entries is the Veeam NFS application data directories and another group is the dynamic drive references (hot add?) used during Veeam backup. e.g. i:\[data store name].vbk new\[data store name].vbk

We don't use NFS.

[Alexey D.]

Rick,

In the ticket status I see that support team has answered to you, have you tried to apply their recommendations?

[virtualwatts]

Hi Alexey - yes, that was a kb from Microsoft, it was a non-starter, there were no drives designated with i:\

[virtualwatts]

The registry references were for NFS mounts in Veeam - my guess, not fact.
All of the references to the incorrect drive letter were related to Veeam software though.

I was able to get a successful upgrade from 5.0.185 to 5.0.1 update after:

Removing the references listed below in the registry.
[images deleted]
Removing the fileshare attached to the C:\vbrcatalog\ directory.

So, on to testing for bug fixes.

Rick

[Alexey D.]

Rick, glad you have solved this.

Actually, reference to "I:\" is strange, looks like a removable device such as flash disk. Did you run original installation from it, by any chance?
Anyway, if you have any other issues, feel free to contact our support for faster resolution. Thanks!

[phollmann]

Hi,

I´ve the same error while upgrading from v7 to v8. The picture regarding the registry entries has been removed, could someone give me the keys which have to be deleted?

Thanks!

[foggy]

Philip, please contact technical support directly with this.