(You didn't install MAPADOC on the target system too?  Typically the source module / enhancement list has to match the destination.)

KB 98722 and 56083 might be worth a look.

We did NOT install MAPADOC yet.  They instructed us to not install it until after the data was migrated.  Sage had mentioned KB 98722.  We are going to try the rebuild of all the system files and then try to migrate again.  I'll let you know the outcome.

We did rebuild all the System files as Sage requested.  There were a few errors in there which is a little scary, but what we did notice was that there was an error on the sy_odbcsecurity.m4t file.  It states "cannot lock Error #0: Record/file busy"  This is odd to me because we had all users out of the system, the Service was turned off and we checked to be sure that there were no pvxwin32.exe's running phantom.  Thoughts?

Because of the file lock, we have not attempted the migration again yet.

Possible a user was connected via ODBC to 100 with Excel?

The ODBC driver is a wrapped PVKIO library not like COM which is a ProvideX session.

Was able to work with a Great tech at Sage and he ran Process monitoring on the system while it was migrating.  It failed on the sy_griddefinition.m4t file.  Made a copy of the file and ran UFAR on the file, it did have several errors.  Started the migration again and it finally Finished!!  YEAH!  

Thanks all.

Sue