Hi,
likely that's no critical error but "unexpected" therefore on-topic in this board:
On my fresh IMatch install on a new PC with new database I observe that a file IMATCH6_LOG_MIGRATE.TXT is created on every startup of IMatch even before a database is loaded.
It seems to be unexpected according to this posting:
Quote from: Mario on April 04, 2019, 09:48:00 PM
The migrate log is created when IMatch migrates a database. It's probably old? How often do you clean the temp folder ;)
jch2103 also found this file being freshly created:
Quote from: jch2103 on April 04, 2019, 09:34:39 PM
Also, what is 'IMATCH6_LOG_MIGRATE.TXT'? I don't recall seeing it in %temp% before.
Maybe this snippet from my log helps:
04.05 14:18:59+ 0 [1D00] 00 M> > 2 CIMMigrator::CheckMigration 'g:\v\develop\imatch5\src\imatchng\immigrator.cpp(126)'
04.05 14:18:59+ 0 [1D00] 02 I> MIR: CheckMigration for: 2019.2.4 to 2019.2.4
04.05 14:18:59+ 0 [1D00] 00 M> > 3 CIMMigrator::Migrate_to_2018 'g:\v\develop\imatch5\src\imatchng\immigrator.cpp(506)'
04.05 14:18:59+ 0 [1D00] 02 I> Migrating IMatch to generation 2018.
04.05 14:18:59+ 0 [1D00] 00 M> < 3 CIMMigrator::Migrate_to_2018
Especially "CheckMigration for: 2019.2.4 to 2019.2.4"
Oliver
That's normal.
The log will contain other data for later versions, depending on if and what is to migrate, the starting IMatch version, the IMatch version that has created the database.
It#s part of the database boot process. I have forgotten about that but of course this is righteous and correct.
Not all users upgrade each version, many skip updates for months. Or upgrade from IMatch 5 to IMatch 2019. Or from IMatch 2017 or 2018. IMatch handles all that automatically during a migration and check phase, and writes this log in case something goes wrong. Then the user will see a message and can send me the migration log file.
The log is not automatically deleted but overwritten on every start.
This is a small file in your TEMP folder. Windows will clean your temp folder automatically. No need to worry.
Thanks for the clarification.
I don't worry about the file, it was just your posting making me double check that everything is as expected.