Hello,
I have made upgrade from Licences 9.5b to 11a Community Edition without any Problem, but by upgrading to Version 12 Community Edition it gives me this: “[Error] Private fixes detected. Please contact our Customer Support to remove the following private fixes that are not supported by the new product version: TFS000100”
There is no thread about TFS000100. In Registry there are no “Private fixes” found. Any idea?
Best answer by Kralik
Hi, if you’re doing a clean install then you could purge the DB and go straight to v12.1. Your issue is that the final 2024 build of v11 doesn’t yet have an upgrade path to v12.1, this will change soon but until then, those on that final path can’t move to v12. Your options are to restore a 9.5 backup and upgrade to an older v11 build then to v12, or just fresh install of v12.1 and import your backups and recreate jobs etc.
I personally would just take screenshots of your existing backup jobs, do a fresh v12.1 install and recreate them after backup imports, otherwise I would build a new v12.1 server and just recreate your jobs by looking at your old server
Hope this helps.
I have done clean uninstall of Veeam 11a and installed Version 12 + all Backup Task renewed.
Upgrade to Version 12 is possible only from version 11 (NOT a), that I have also tested last week.
+20Do you recall any “fixes” Support has helped you with in the past? Best bet is to contact Veeam Support to see what this is/was, so you can remove it.
+21There was another thread about this as it had to do with the database, but you are going to need to contact Support more than like.
I think that is the only way to solve this.
+20I did find a Veeam KB about this error, with potential workarounds:
+5+21I did find a Veeam KB about this error:
This should help with the cumulative patch piece towards the end.
+20+21Check out this KB as it appears you might have to wait for 12.1.2 instead of 12.1 version - KB4245: Release Information for Veeam Backup & Replication 11a Cumulative Patches
+20Great Thanks to everybody, I haven´t expected so quick reactions. You are the best. Tomorrow I will reinstall. I will let you know, if it helped.
+23Hi, if you’re doing a clean install then you could purge the DB and go straight to v12.1. Your issue is that the final 2024 build of v11 doesn’t yet have an upgrade path to v12.1, this will change soon but until then, those on that final path can’t move to v12. Your options are to restore a 9.5 backup and upgrade to an older v11 build then to v12, or just fresh install of v12.1 and import your backups and recreate jobs etc.
I personally would just take screenshots of your existing backup jobs, do a fresh v12.1 install and recreate them after backup imports, otherwise I would build a new v12.1 server and just recreate your jobs by looking at your old server
Hope this helps.
+21Great Thanks to everybody, I haven´t expected so quick reactions. You are the best. Tomorrow I will reinstall. I will let you know, if it helped.
Keep us posted but as noted by Michael think about 12.1 directly.
Hi, if you’re doing a clean install then you could purge the DB and go straight to v12.1. Your issue is that the final 2024 build of v11 doesn’t yet have an upgrade path to v12.1, this will change soon but until then, those on that final path can’t move to v12. Your options are to restore a 9.5 backup and upgrade to an older v11 build then to v12, or just fresh install of v12.1 and import your backups and recreate jobs etc.
I personally would just take screenshots of your existing backup jobs, do a fresh v12.1 install and recreate them after backup imports, otherwise I would build a new v12.1 server and just recreate your jobs by looking at your old server
Hope this helps.
Seems like better idea. For example today I have made upgrade another Server with Veeam Version 11 (not version 11a) to 12 and it has been working just fine.
+21Hi, if you’re doing a clean install then you could purge the DB and go straight to v12.1. Your issue is that the final 2024 build of v11 doesn’t yet have an upgrade path to v12.1, this will change soon but until then, those on that final path can’t move to v12. Your options are to restore a 9.5 backup and upgrade to an older v11 build then to v12, or just fresh install of v12.1 and import your backups and recreate jobs etc.
I personally would just take screenshots of your existing backup jobs, do a fresh v12.1 install and recreate them after backup imports, otherwise I would build a new v12.1 server and just recreate your jobs by looking at your old server
Hope this helps.
Seems like better idea. For example today I have made upgrade another Server with Veeam Version 11 (not version 11a) to 12 and it has been working just fine.
I think the upgrade issue is dependent on the current version installed like the latest patch for 11a being an issue.
Hi, if you’re doing a clean install then you could purge the DB and go straight to v12.1. Your issue is that the final 2024 build of v11 doesn’t yet have an upgrade path to v12.1, this will change soon but until then, those on that final path can’t move to v12. Your options are to restore a 9.5 backup and upgrade to an older v11 build then to v12, or just fresh install of v12.1 and import your backups and recreate jobs etc.
I personally would just take screenshots of your existing backup jobs, do a fresh v12.1 install and recreate them after backup imports, otherwise I would build a new v12.1 server and just recreate your jobs by looking at your old server
Hope this helps.
I have done clean uninstall of Veeam 11a and installed Version 12 + all Backup Task renewed.
Upgrade to Version 12 is possible only from version 11 (NOT a), that I have also tested last week.
+21Glad to hear you were able to resolve the issue with a clean install of v12. Be sure to mark the best answer for your question that helped you solve your issue - the one that helped the most.
+20Nice! Glad doing so took care of your issue.
Nice! Glad doing so took care of your issue.
Thank you, I will be back with another Issue :-)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
