'Da Vinci Resolve failed to save project'

Hi,

I'm getting this error message whilst editing and it's happening at least once a day. When it does happen, I'm able save a copy of my database, but I'm not able to save the project itself. This is a problem because I am working on a collaborative project with 3 editors. We've got livesave turned on but when quitting out of the project we're losing about half an hour of work at a time.

I can't exactly tell what is causing the problem. We are all working from iMacs, and our media and database are on a shared QNAP NAS storage system connected with Thunderbolt 2 cables.

Anyone had a similar experience or know a reason why this might be happening?

Thanks!

This can typicaly happen if you loose network connection with your central shared postgresql database (i hope and assume you dont use disk databases for sharing). So you have to investigate these.

Generate diagnostics and have a look in the logs yourselve. Maybe you see some hints

Edit : only other time i had this was aftr a database migration / restore. After vacuuming and fully reindexing the db it was gone.

[Dwaine Maggart]

You can't share a Disk database.

Thanks for your thoughts. It is a postgres database running on a QNAP NAS.

The 'failed to save project' error just happened again and we got this from the log in the database server, that coincided with that message in Resolve:

Code: Select all

ERROR:  duplicate key value violates unique constraint "ListMgt::LmVersionTable_pkey"
DETAIL:  Key ("ListMgt::LmVersionTable_id")=(7bd28091-71c9-42b2-b42c-b59d1ad76efb) already exists.
STATEMENT:  INSERT INTO "ListMgt::LmVersionTable" ("Sm2TiItem_id", "ListMgt::LmVersionTable_id", "DbType", "FieldsBlob", "VerType", "pRemoteTable", "pActive", "LockSysId", "DbSavedTime", "LinkedGroup") VALUES ('1bfbd32c-ca52-44f0-ab5e-6a3c74a59f2b', '7bd28091-71c9-42b2-b42c-b59d1ad76efb', 'ListMgt::LmVersionTable', NULL, '0', '99cdcb23-89e3-493d-a0f2-04a9d6ac5731', '379aa4ba-38b1-442a-8ade-7ec139543809', '', 77392, NULL)

This is a key violation, we can't imagine any way we'd alter the database to make this not happen.

Any thoughts?

Auch, that is not good. BM to the rescue i would say.

[Dwaine Maggart]

The PostgreSQL database itself is running on the QNAP?

What version is it?

Curious how you got it configured to work with Resolve?

[Rohit Singhal]

Ruby, are you seeing this issue on 15b6 as well? Can you please post the logs?