Antivirus blocked access to the file

[Phantom54]

After cataloguing some shows on or about 22nd December, I received a warning message- 'ABORTING, please try again'. See jpg file attached.

This happened on all of my stations when they accessed the same file via the LAN, including the host station.

When I changed to a backup data base, Coollector worked as expected. The newest (but faulty) DB is using 673KB. The most recent backup (which works) is 644KB. I guess the difference in size is because one or more files in the now faulty DB has caused the problem.

Suggestions?

Cheers
John

Attachments

2022-12-23Antivirus blocked access to file.jpg (32.84 KiB) Viewed 22184 times

[(cool) Hector]

I received a warning message- 'ABORTING, please try again'.

This message is displayed when something prevents the app from reading the file. It assumes that it's your antivirus that blocks the access, but there's no certainty at all.

This happened on all of my stations when they accessed the same file via the LAN, including the host station.

Yep, something had locked the file. Maybe a simple restart of your NAS would have helped.

When I changed to a backup data base, Coollector worked as expected.

Cool!

The newest (but faulty) DB is using 673KB.

I don't think it's faulty, probably you could try again with it. This locking was mysterious and probably temporary.

The most recent backup (which works) is 644KB. I guess the difference in size is because one or more files in the now faulty DB has caused the problem.

Your backup is only missing the changes you made in your last session. Did you make a lot?

The size isn't a good indication. As you make changes to the database, it grows fat, i.e. bigger than necessary. When the app creates a backup, the app makes an operation to remove the excess fat and give the file its optimal size. The difference in size seems important, but it's because the backup had been optimized and not the newest database.

Suggestions?

Personally I've stopped using my NAS a long time ago because I found it annoying to have some files arbitrarily locked from time to time (it was a D-LINK DNS 323).

[Phantom54]

Thank you for your replies.

I am not using a NAS but simply a Workgroup with three stations.

The problem occurs even when I am using the db locally. Changing to a backup fixes all of the remote stations as well.

While I am not sure which addition caused the virus warning, I will try to find out.

Are you able to say where the warning came from? Is it from Coollector? Is it from my antimalware (Trendmicro)? Is it from whatever file I catalogued?

All of the videos play directly from VLC just fine.

Cheers
John

[(cool) Hector]

The problem occurs even when I am using the db locally.

Please send me the file so I can look at it. My email is: hector at coollector dot com

While I am not sure which addition caused the virus warning, I will try to find out.

Do not bother, if there's really a problem with the file (which I still doubt), I'll be able to understand the issue.

Are you able to say where the warning came from? Is it from Coollector?

It's definitively from Coollector. Something prevents it from accessing a file, it complains about the antivirus because it's the most likely but it has zero certainty.

[Phantom54]

I believe that all shows that were catalogued with the problem folder were also saved in the backup file I am now using. I copied the problem file to another PC and tried running it and am still getting the virus warning.

Please find attached the file in question.

Cheers
John

Attachments

MyCoollectionOLD.cool

(673.98 KiB) Downloaded 749 times

[(cool) Hector]

I get the same message on my computer, which is great!

I will look into it tomorrow.

[(cool) Hector]

Ok, the file is indeed corrupted and completely unreadable.

You had no other choice but to use your best backup

[Phantom54]

Thank you for that. The PC that hosts the file is old, greater than 10 years. Lately, it has been freezing in that whatever is running, say VLC freezes. I can still right click and call up Task Manager but no action occurs beyond that. The only thing I can do is a hard reset and all is well. Perhaps one of the freezes occurred when Coollector was archiving the DB.

Thank goodness for a well designed program that does frequent backups.

Cheers
John

[(cool) Hector]

Perhaps one of the freezes occurred when Coollector was archiving the DB.

Perhaps... File corruption is still a mystery to me

Thank goodness for a well designed program that does frequent backups.

Thank you very much! I've implemented it because file corruption sometimes happens. It's very rare but sometimes it happens, like planes crashing or trains derailing. That reminds me of a TV series about such catastrophes, where they said that it's always the conjunction of several unlucky events.