1325.VBRcatalog is not a valid short file name

[zymran09]

Hello everybody,

i wanted to update B&R from V9 to the actual V10 and the installer wont go through with this error:

1325.VBRcatalog is not a valid short file name

Ive tried to uninstall the whole version 9. It uninstalls all components, execpt the VBR-Catalog. If i want to uninstall this, it gets the same error message. Anybody can get a thing with that?

[foggy]

Hi Thomas, it is always better to contact technical support with issues like that. Please don't forget to share the case ID here for reference. Thanks!

[zymran09]

Ok, the Case-Nr.04277253

[sophearom]

I have the same issued, is there any solution?

Best Regards,
Sophearom

[nielsengelen]

@sophearom as mentioned in this thread, please contact support and post the case ID here.

[Natalia Lupacheva]

Hi @sophearom,

just a suggestion (after you open a support case) - you can check the registry key:
- Open Regedit
- Navigate to HKLM\SOFTWARE\Veeam\Veeam Backup Catalog
- Find the REG_SZ entry named "CatalogPath"
Change the Value data to match the actual VBR catalog location. Sometimes this location has changed over time since the last upgrade, the path may not exist anymore.

That's not a panacea but I see people have faced this issue several times.

Thanks!

[czj624]

I had to modify permissions on that registry key to see the "Veeam Backup Catalog" sub-key, then I was able to make the change and uninstall successfully.

[Natalia Lupacheva]

Hi Jesse,

thank you for sharing your solution!
Glad the registry key worked for you after permissions modification.

[Kav]

hi all,

Im running the community version in my home lab and after changing the backup disk attached I started getting this error as well.

I logged Case #04857150, however it was auto resolved due to high support volumes.

Im happy to just uninstall the app, but I get the same error when trying to uninstall! I tried the reg solution above and repointed to the new disk, the folder is there now and has been repopulated with data, but still this error persists.

Any ideas, or do you have instructions for manually removing all traces of the software?

[Natalia Lupacheva]

Hi Kav,

We have only the standard guide how to uninstall Backup&Replication, but as far as I see that's not your case.
If none of the suggested solutions help, I would recommend to open the Support case again later, they could help.

Thanks!

[marko.cepe]

Hello.
I followed this article but it did not resolve my issue. My values were set correctly. I was upgrading from 10 to 11 and got this error. What I did was:
- when the message popped out I opened CatalogSetup.log located in C:\ProgramData\Veeam\Setup\Temp and searched for VBRCatalog.
- I found an entry "CatalogPath is set to E:\VBRCatalog" but my VBRCatalog folder is on drive X:
- I opened Regedit and searched through the whole registry for "E:\VBRCatalog"
- I renamed/changed every Key and Value from E:\ to X:\
- After the changes, I reran the Upgrade and it was completed successfully.

Obviously when Veeam was installed someone set to install VBRCatalog to drive E. But then someone moved it to drive X:\. Veeam Upgrade process somehow ignores the values mentioned in this article but takes the values from HKLM\SOFTWARE\Microsoft\Windows\CurrenVersion\Installer\UserData\S-1-5-18\Componentes\548FDDBB83EB487478FBC0FD5AC7CDCB and HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders (this were the keys for me, maybe your's will be different)

[Mildur]

Hi Marko

Thanks for the additional keys.

Thanks
Fabian

[Nosegear]

I found the solution might be much simpler . . Ran into this issue as well when upgrading from v11 to v12. Turns out that the upgrade has to be performed from the same drive as the initial installation. I mounted the .iso as drive H: and got into issues, but then reassigned drive D: to it (the server's CD ROM station, moving the CD ROM station to another letter temporarily). Installation then went flawlessly.

[skincaid]

I even experienced this doing the V11 to V12 upgrade.

Had to edit this entry: HKLM\SOFTWARE\Microsoft\Windows\CurrenVersion\Installer\UserData\S-1-5-18\Componentes\548FDDBB83EB487478FBC0FD5AC7CDCB

[pk23]

I found the solution might be much simpler . . Ran into this issue as well when upgrading from v11 to v12. Turns out that the upgrade has to be performed from the same drive as the initial installation. I mounted the .iso as drive H: and got into issues, but then reassigned drive D: to it (the server's CD ROM station, moving the CD ROM station to another letter temporarily). Installation then went flawlessly.

Hi. I registered just to be able to write back to your post. Your suggested solution solved my problem. When I changed the letter of the virtual DVD drive from G: to F: the installer stopped showing the error and completed the installation correctly!

THANK YOU VERY MUCH!