Some very old files fail to migrate

[gchampoux]

I just did my first full Intralink 3.4 to 9.1 migration test, including the files (PreCopy method).

Out of 400,000 files, 500 failed to migrate.
In each case, the message was:
"Unable to move this file. Reasons may be- file does not exist or dont have proper permissions to move into PDMLink filevault".
The above message is untrue. The files all exist, and the permissions were identical for all files.
However, I did notice that all of the failed files had the following in common:

1. They were all migrated from Pro/PDM to Intralink 3.2 (back in 1997).


2. They had not been modified since that migration.


3. The file names (within the vaults) are of this form: C#, where # is a 2-6 digit number.
   None of these failed files have a file extension. (.prt , .asm , etc.)

In Intralink 3.4, these files still work fine. I can check them out and open them in Pro/E.

Anyone else run into this during their migration?

Gerry

[gchampoux]

I am migrating from 3.4 M030 to 91. M060.

[cadjett]

I would assume that the WinDU might show why these files wont migrate.

The Data Migration guide explaiins what options to use with in the windu app.

You can send the windu output to ptc & they will provide healing scripts.

But make sure the scripts are only run on your cloned machine, till you clean your data &/or know why they wont migrate.

I think also running the 500 objectsagain might sometimes resolve the issue with some, but I cant recall which area of the migration this works for.

L Jett