After upgrading to 2020, I began testing the new face annotation feature. After working on that for a bit, I scanned for new image folders that I added, and left the computer to finish. When I came back to it, the program had closed. Unfortunately, I did not do a backup with 2020 version.
Then whenever I try to open IMatch, the program closes after beginning the initialization. The log file indicated that "The last IMatch session did apparently not complete normally".
I tired to reinstall IMatch to see if that would help, but now when I try to open it, I get an error saying Duplicate application ID detected.
How can I get this to work again?
Dale Wagler
Have you used Pack & Go to restore your database?
This looks like the app folder contains a mix of old and new apps, and probably other resources too...
Yes, but the results say file contains 1954 packets. 1953 skipped. 0.00 KB restored.
That doesn't sound good.
Dale
Older Pack & Go packages are not compatible with IMatch 2020.
Pack and Go is designed to transfer databases and settings between computers. Restoring an old package on top of IMatch 2020 will damage the installation.
This has been explicitly mentioned and explained on the page
Upgrading to IMatch 2020 (https://www.photools.com/help/imatch/#migrate_imatch2020.htm?dl=h-2)
which is a mandatory read. IMatch 2020 opens this page automatically when it starts for the first time.
How to fix your damaged installation, see this thread from today for the same issue:
https://www.photools.com/community/index.php?topic=9883.msg69851#msg69851
read from the bottom up.
Thank you Mario.
This info helped solve my problem.
Dale Wagler
Very good. Have fun with IMatch 2020.
I'm not sure what I'm doing wrong, the the issue has happened again. I have used IMatch successfully for several sessions, but then one day when I closed and used the pack and go backup at the end of the session, pack and go crashed and now IMatch won't open again. It gets part way through the initialization, then opens a box saying it didn't close down properly last time. If I click continue, the program closes.
Uninstalling and reinstalling doesn't seem to work this time.
Dale
I doubt that Pack & Go has anything to do with this.
As always, it helps to provide at least a minium of information, like the log file (https://www.photools.com/help/imatch/#im_logfile.htm)
sorry, i meant to attach that.
I see many warnings like
'attempt to write a readonly database'
did you make the database read-only in the file system?
Or did you enable the option to open databases in read-only mode in the Database menu?
IMatch reports that the database was opened in read-only mode or that it is stored on a read-only media.
I did try read only to see if it would open then, but only because all else failed.
So this was not a real test.
I would need a log file from a session where "IMatch does not open" as you said in your first post.
IMatch will still write a log file (probably a short one). This may show us what the problem is.
Does this attachment have what you need?
Dale
That's just the log file created when IMatch migrated the database.
The real log file is named IMATCH6_LOG.TXT and overwritten every time you start IMatch. But when IMatch fails to launch, it will contain important info about why IMatch fails to launch.
That file is attached, although it is the one with all the references to readonly.
Dale
But if IMatch does not start, why not create a new log file from that session?
This log file (except for the database being read-only) looks perfectly normal. IMatch was starting OK. Or is this from a session where IMatch did not start?
What happens if you start IMatch without a database? Hold down <Ctrl> while starting IMatch until you see Advanced Startup Options (Recovery) (https://www.photools.com/help/imatch/#ref_startup.htm?dl=h-2) then chose "Start without Database".
Yes, this is what I get after it won't start.
If I choose Continue normally with last loaded database, the program immediately closes.
I did uninstall and reinstalled this morning, so this is from a fresh install.
Dale
Have you configured IMatch and the database folder as an exception in your anti-virus?
Does the same happen if you don't open the database in read-only mode?
Does IMatch produce a Debug Dump File (https://www.photools.com/help/imatch/#im_dumpfile.htm?dl=h-2)?
What happens if you create a new database? Does this also fail?
Have you configured IMatch and the database folder as an exception in your anti-virus?
- I have not changed anything with regard to anti-virus.
Does the same happen if you don't open the database in read-only mode?
- This problem originally started in standard mode - I only tried read-only to see if it would make a difference.
Does IMatch produce a Debug Dump File?
- I have not seen a dump file created.
What happens if you create a new database? Does this also fail?
- I just tried to create a new database and it closed as well.
I have attached the log file from the attempt to start a new database.
Dale
No error reported in the log file. It just ends.
Do you get any kind of message when IMatch closes that way?
Because if no DUMP file is generated, the crash happens outside IMatch (driver, 3rd party component, runtime component) and Windows should display a message with information why it is closing IMatch. IMatch does not get any notice of this.
This looks like a typical anti-virus problem where the virus-checker does a false positive and shuts down an app immediately (IMatch in this case).
You may want to look into the Windows Event Monitor for problem reports or similar. Maybe Windows has noticed something.
I cannot see anything in the log. A DUMP file is not produced. Impossible to analyze further from this end.
I did discover an error "your file history drive was disconnected for too long". Could this be the problem? If so, how do I fix it.
As far as I know all drives are connected. The drive that was referred to seems to work for copying and reading other files, but I did try setting a different drive for the file history, but nothing has changed.
I have no idea what this means. This is no IMatch message so I cannot help you there, I'm afraid. Did you try Google?
I did check Google and it seems to have something to do with a file history backup in windows, but doesn't help me get IMatch to work. If I can't get it working, is it possible to refund my recent upgrade to 2020? It has been since that upgrade that I have been having problems.
Dale
Please start by configuring IMatch as an exception in your virus-checker.
The log files you attach just end normally. No sign of IMatch not running or having problems with anything. No DUMP file generated (which IMatch does when it crashes). No error message from Windows.
If IMatch does not run, the anti-virus on your system is the most likely cause.
Quote from: dwags on April 07, 2020, 02:35:26 PM
Have you configured IMatch and the database folder as an exception in your anti-virus?
- I have not changed anything with regard to anti-virus.
If you didn't update your antivirus exception settings, this is likely an issue: The name of the IMatch executable is different in IMatch2020 (IMatch2020x64.exe) than it was in IMatch2019.
I have added the new executable to my anti-virus exceptions and tried to run IMatch again. This time it still closed unexpectedly, but did create a dump file. I am unable to attach it though as it is too large.
Dale
Just upload it to your cloud space (Dropbox, Google Drive, OneDrive, ...) and send me a link to support email address (https://www.photools.com/support/).
If adding the IMatch executable to your AV changed something, make sure you add the entire folder containing IMatch (IMatch consists of several executables) and also the folder containing your database.