Movie Collector v23.3.5 has stopped working - Access Violations

My Movie Collector v23.3.5 has stopped working. I have uninstalled it, restarted the computer, and reinstalled it. Deleted everything in the registry pertaining to Movie Collector. Nothing changes. There are several error messages that come up. The first one is this…

Cannot create file
“C:\Users\pkread\AppData\Local\Collectorz.com\Movie Collector\backups.xml.” The process cannot access the file because it is being used by another program.

The second one is…

Access violation at address 0000000003064319 in module ‘MovieCollector.exe’. Read of address 000000000000000.

Then the program boots up, but everything is blank and nothing works. After the program is closed, there are two error messages.

Range check error.

And

Access violation at address 00000000032ED5AC in module ‘MovieCollector.exe’. Read of address 000000000000030.

What is the problem? How can I load it so it works normally again???

My first suggestion would be: please forget about the legacy desktop software and switch to the Movie Connect web-based software.

Problems like the above are EXACTLY why desktop software is dead. Windows is making it impossible to run desktop software without periodic stupid permission problems.

But to resolve this: please reinstall the program with Admin Rights.

Here’s what to do:

Download your Collectorz software again from your CLZ Account page.

  • Login here: https://my.clz.com/

  • Click the download button for your platform and download the version you’re entitled to, save it to your computer (do not run the installer).

Right click on the downloaded installer, and select ‘Run as Administrator’.

This will install the program with Administrative rights.

Now launch the program and see if the problem has been resolved.

I have te same issue. Running/installing with admin rights doesn’t make a difference. I need to be able to use the application when not connected to the internet so a web based solution is no use.

Please follow the steps below to try and resolve this issue, this process will affect some local settings in your software such as the width of columns, but your database will not be affected.

Here’s what to do:

  1. Click the Windows start icon and type ‘regedit’ into the search box, then press ENTER.

  2. Locate the following key:
    HKEY_CURRENT_USER > Software > Collectorz.com > Movie

  3. Select that “Movie” folder entry there and delete it!

  4. Download and install Movie Collector from your My CLZ page:
    https://my.clz.com

  5. After installing, you will have to unlock the software. Fill in your username/password to unlock the software.

  6. Before actually opening your database, try adding one movie to this empty database, just to check if it all works fine!

  7. Now, reopen your database: Click File > Open then locate the database file in order to get things working again.

This didn’t work. It still throws the error, even before getting to the point of unlocking the software.

Can you explain what happens exactly?

Here are the sequence of errors
Click on the shortcut, the splash screen appears then this error:
CLZ error 1
Click OK and get this error:
CLZ error 2
Click OK and the app opens:


With the app the active window, I do a screen capture (Ctrl-Shift-PrtScn) and this error appears:

The above error does not appear if the collector app is not the active window
A similar error appears when trying functions in the app but with different addresses and actions (read, write, etc.)
Click the X to close the app and the following two errors appear (in this order):
CLZ error 6
CLZ error 7
Click OK on the address violation and then on the range check and the app is closed.

UPDATE
I deleted backups.xml and started the app. The app created the file and then the error appeared. It ran a few seconds longer before the error appeared. Clicked OK and the app came up and looked a little different with the number of movies in the DB and my subscription expiration date. Clicked the X to close and only received the range check error and not the access violation.