Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 868404" data-attributes="member: 18896">Very early on in the log file (with your restored backup from a month ago), the following line shows:&nbsp;18-May-2012 19:21:19 Error [&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; DBField]: Error writing to DBCriteria`1.Value Property: Se produjo una excepción en el destino de la invocación.So you have corruption already in that database.&nbsp;It has no usage to read the rest then, so can you repeat the test with an older backup?&nbsp;If not, then try to repeat the test you did, but take those 3 movies out that 'hung' the import. It is very well possible that one of them is corrupted at AVI/MKV/etc header level which causes MediaInfo to crash. Preferably you then supply the MediaInfo developers with that file, so they can fix their program to prevent this 'crash' from happening in the future.&nbsp;To actually fix the problem for yourself, it sounds like you might have to start from scratch by deleting the movingpictures.db3 file (or rename it), and preferably re-import blocks of movies, say 10 or 50 at a time if you have a large collection. That way you can constantly make backups and it will be less of a painful experience if you still have corrupted media files that cause the import process to damage things and you have to start over.</blockquote>

[QUOTE="RoChess, post: 868404, member: 18896"] Very early on in the log file (with your restored backup from a month ago), the following line shows: [INDENT=1]18-May-2012 19:21:19 Error [ DBField]: Error writing to DBCriteria`1.Value Property: Se produjo una excepción en el destino de la invocación.[/INDENT] So you have corruption already in that database. It has no usage to read the rest then, so can you repeat the test with an older backup? If not, then try to repeat the test you did, but take those 3 movies out that 'hung' the import. It is very well possible that one of them is corrupted at AVI/MKV/etc header level which causes MediaInfo to crash. Preferably you then supply the MediaInfo developers with that file, so they can fix their program to prevent this 'crash' from happening in the future. To actually fix the problem for yourself, it sounds like you might have to start from scratch by deleting the movingpictures.db3 file (or rename it), and preferably re-import blocks of movies, say 10 or 50 at a time if you have a large collection. That way you can constantly make backups and it will be less of a painful experience if you still have corrupted media files that cause the import process to damage things and you have to start over. [/QUOTE]

Verification