Task Scheduler - Migration problem with Vault project. Local works.

[anandax]

Hi,

we have migrated from 2012 to 2015 Basic (SP1). Now we want to migrate our assemblies, but the Task Scheduler have problems with the Vaultfiles.

Error happens when we try to migrate with our Vault-Project (IPJ). In the Logfile there many missing files.
When we checkout with Vault Basic 2015 and migrate the files local in Task Scheduler, there are no errors. How can this be?

The own difference between the project-files ist is local or Vault.

[Neil_Cross]

My first thoughts is that a file reference update might be required within Vault (Actions > Update File Reference).  As a test, run that command against a sample assembly and then see if that assembly appears as an error when you try the task scheduler migration.

=========

Just as a side note, doing a mass file migration to the latest CAD version in Vault isn't necessary and in many cases is not recommended.  I'll explain why as some folk might question that statement.

Vault will happily work with all files regardless of what version they are at.  Vault doesn't care if a part in an assembly is from Inventor 2012 but your Vault is at 2015, it doesn't matter and won't cause any problems at all.  Especially not in Vault basic where you're not using any advanced features of Vault.  You'll not have any limited functionality or performance decrease by keeping the files as they are.

In fact doing a mass migration can cause serious problems.  For example:

Not including old versions, my Vault here currently has 240,000 files.  My filestore is 450GB in total.  Migrating a file will create a new file version in the filestore.  After full migrate I will end up with ~240,000 additional files in my Vault as it creates a new version for each file.  If I do that every year for every new CAD upgrade, you can see how fast this will become out of control.  In a couple of years I'd end up with millions of files in the filestore, and my server capacity would need to be reviewed and increased regularly.  Also, it's highly likely that I wouldn't even be able to mass migrate that many files in one operation.  And furthermore, what would be the benefit in migrating the entire Vault when the majority of that will be legacy project data?

My advice would be to not mass migrate, let Inventor/AutoCAD auto-migrate the files passively as you work on and save them.  That way you'll help keep your Vault at a manageable size and only migrate the files you need to work on.  If you do ever need to use those legacy files, they'll still open in any future version of Inventor without any issue and migrate when you save them.

Apologies if you're dead set on a migration and need to do it anyway for whatever reason, but that's my advice and of course you're free to take it or leave it 

[anandax]

File references are updated, but same problem. The task scheduler (with Vault-IPJ) has found files which were already renamed or moved. Local no problems.

I've testet it again. With Task Scheduler my iam-file is smaller than the file from Vault-Explorer, but in the iproperties both files have the same version.

See attachment.

>>Just as a side note, doing a mass file migration to the latest CAD version in Vault isn't necessary and in many cases is not recommended.

You are right, but we have migrated since 2006 our databases and files. The advantage of migration is, that you can find errors in assemblies.

>> In a couple of years I'd end up with millions of files in the filestore

We clear up the files.

>> If I do that every year for every new CAD upgrade

We wait for 2 or 3 years and then migrate.

[mercerc]

Would it be possible for you to post the log file of migration using the vault project file with the small assembly? It may be helpful in explaining the reason.

Thanks,

[anandax]

Hi mercerc,

we have opened a case with id 10560318. Our database was 10GB. In the last weeks I've shrinked it to 120MB.

Can you access the ID?