Blackmagic Forum

I upgraded to the stable release of Resolve Studio 17 (Build 39) I also performed a completely clean instal of the OS on my machine before doing so. I'm running Windows 10 Pro (Build 19042).

My database, Power Grades and LUTs are all backed up, so nothing's lost, however I cannot restore my V16 database.

The restore process says it's successful however I get a critical exception warning immediately after with the following statement:

BtException: Driver not loaded Driver not loaded

00007FF6E54D1804
00007FF6E560E4BB
00007FF6E5612C89
00007FF6E56134C8
00007FF6E563BD41
00007FF6E5636C1B
00007FF6E400EA1F
00007FF6E3EAB678
000000005A7A0EFA
000000005ADDE1D3
000000005AB99E4E
000000005AB99C56
000000005AB9AA88
000000005AAEF94A
000000005AAC7504
000000005AAC5414
00007FF6E308B767
000000005A781118
000000005AAC8945
000000005AB16F63
000000005AB15627
000000005AAC7504
000000005AAC5E89
00007FF6E308B767
000000005A781118
00007FF995F67508
00007FF995F54408
000000005A7C4B08
00007FF9E87EE858
00007FF9E87EE299
000000005A7C440D
00007FF993C638F2
0000000000000005
0000000000000024


I tried restoring the v16 database on my m1 Mac with the 17.1 (Build 21) Studio version, and it does not work either, the difference is that on the Mac Resolve just crashes after confirming the database was imported. When opening resolve after the crash the database is not there.

The version 16 database is not compatible with 17, or vice versa. Make a backup of the 16 database then do the upgrade of it when prompted in 17. The backup means that if you wish to go back to 16, you can.

I have the same problem,
I've done back-up of the database before upgrading to DR 17,
but when I try to restore the old database, I've same error messages as you

I can not restore either, getting the same error.

Clean Install of Big Sur & DaVinci Resolve Studio 17.1

When I try to restore my (DR Studio 16) Database Backup, I get the error message "Critical Exception" and Resolve crashes.
This happens at the end of the restore-process, after the message "you have restored your database successfully".

The same happens if I try to connect to a copy of the same (DR Studio 16) database.

I have also made tests with a database created new in Resolve Studio 16 (with a few copies of projects in it).
Its backup crashes too at the attempt to restore it. The same happens with connecting as well.

I can trigger this on my Mac Pro & my Macbook Pro.

The first stage is to get resolve running correctly before you deal with DB upgrades and im not even sure from your posts thats the case.

Unfortunately it seems you didn't use resolve to back up the DB and then restore it to test the backup. Please conform thats the case?

please also detail are you using disk or postgres databases?

Thank you for your fast replay.

Peter Chamberlain wrote:The first stage is to get resolve running correctly before you deal with DB upgrades and im not even sure from your posts thats the case.

It does, I have made several tests with new & imported projects.

Peter Chamberlain wrote:Unfortunately it seems you didn't use resolve to back up the DB and then restore it to test the backup. Please conform thats the case?

I have tried this right how. I made a backup from the database and restored it in Resolve 16, which worked.
From this I made a backup again, which I tried to restore in Resolve 17, that resulted in the error again.

Peter Chamberlain wrote:please also detail are you using disk or postgres databases?

Disk.

I wonder if maybe you can't Restore an incompatible database. One created in 16 can't be "Restored" to version 17. I'm thinking maybe a different approach.

Once you update to 17, you should have the databases still available, no need to Restore them.

Update those.

@Jim Simon

Good thought, I wanted to do this as the last resort.
Installing Big Sur & Resolve 16 on a separate drive, restoring my old database backup,
and updating Resolve to Version 17 ...
(and from there copy the database folder or restore a backup to my actual drive).

I took it for granted that, if I restore a DR16 database in DR 17, it would be converted in this process or I would get at least a message, if it was not compatible.

I mean, it is not that unusual, to start with a new clean OS (especially if one updates the OS as well). So there should be an easy way to do a fresh install of DR 17 without having to do such a workaround.

However, I am just glad, if this works ...

This is obviously a bug, which is clear to me now, after checking this with other members of the FB-Group „Davinci Resolve for professional users“.
I wished, this just would have been considered by the support as well, instead of pointing on to what I could have done wrong and then not replaying any more.

Maybe this helps others in the same situation, so that they don‘t have to do tests for hours until they have to find out, that this is a bug and needs the workaround described above ...

Jim Simon wrote:I wonder if maybe you can't Restore an incompatible database. One created in 16 can't be "Restored" to version 17. I'm thinking maybe a different approach.

Once you update to 17, you should have the databases still available, no need to Restore them.

Update those.

You can use Resolve 15 to restore a database created in 12.5, don't see why this should be any different.