Recreate/rereading Metadata in Database

[RainerG]

After a crash (bluescreen - probably not from IM5) during IM5 updating metadata, the IM5 DB lost all the Metadata/Exif from this pics. When i looking with ExifToolGUI the Metadata all available. Also i think IM5 lost the metadata.

Is there are a way to recreate/rereading the metadata?

[Mario]

When IMatch ingests metadata or files it does so in batches of maybe 20 to 100 files. This is a transactional unit, and the changes done to the database during such a transactional unit are either written completely or not written at all.

If a Blue Screen or power failure happens during a transaction, these changes will never reach the database. IMatch will roll back the pending changes the next time the database is opened. So you can loose the metadata of the files currently being processed, but not all metadata in your database. Your post reads as if suddenly all metadata in the database is gone - this cannot happen.

Did you run a database diagnosis to check the physical integrity of your database?

[Richard]

If the database diagnosis gives a clean bill of health, wouldn't a rescan of the images involved bring the metadata into IMatch?

[Mario]

Yes. To re-read the metadata for all selected files, a <Ctrl>+<Shift>+<F5> and then choosing Reload Metadata in the dialog will do the trick.

But the error description is so strange and I wonder if the database was damaged by the blue screen.

[RainerG]

After the crash i start IM5 and IM says there are errors in the DB. Then i start the diagnostic.

That is the diagnostic (last lines with the errors):

Not all the metadata is damaged. Only the data that do IM updating. The rest looks good.

Log file data removed and added as an attachment by Mario. Please don't just copy/paste this amount of data in a post. This not only makes the post unreadable but also is poison for the board search engine. Just ZIP and attach the diagnosis log, this is better.


[attachment deleted by admin]

[Mario]

This database has been destroyed real bad. The database is gone for good.
I've never seen this amount of damage to a database file.

Whatever your Blue Screen was, it had a real bad effect on the physical database file on disk, and maybe other files as well. Did you run check disk on your hard disk afterwards to ensure the file system is OK?

[RainerG]

It was a very heavy bluescreen. At next start win7 goes in the repairmodus befor starting. I think win make at this moment a chkdisk. I think thats the new 8gb mem. its my third or fourth blue screeen after buying. one blue screen per month i think.

[Mario]

Bad RAM can have this kind of effect.
Make sure the RAM sites really tight in the slots.

The Windows Event log should contain additional information about problems encountered when accessing RAM.