Audacity 3.0.0 Win 10.0.19041 "Failed to open the project's database"

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
jademan
Forum Crew
Posts: 1415
Joined: Fri Jul 17, 2009 10:11 pm
Operating System: Windows 10

Re: Audacity 3.0.0 Win 10.0.19041 "Failed to open the project's database"

Post by jademan » Sun Apr 11, 2021 6:08 pm

Magimix98 wrote:
Sun Apr 11, 2021 4:36 pm
Seems like you guys are on the right track for a permanent fix so that's great nice work.
Thanks for the report. I forwarded you note along to the developers. :D

McCoyCORE
Posts: 2
Joined: Sun Apr 11, 2021 8:34 pm
Operating System: Windows 10

Re: Audacity 3.0.0 Win 10.0.19041 "Failed to open the project's database"

Post by McCoyCORE » Mon Apr 12, 2021 12:23 am

Running macros and I constantly get the "Failed to open the project's database" error. I'm running a batch of about 100 files, but it doesn't happen at the same spot. Sometimes it crashes at file #2 and sometimes file #35, etc. Random. Basically my macros are useless because I can't batch run anything.

jademan
Forum Crew
Posts: 1415
Joined: Fri Jul 17, 2009 10:11 pm
Operating System: Windows 10

Re: Audacity 3.0.0 Win 10.0.19041 "Failed to open the project's database"

Post by jademan » Mon Apr 12, 2021 1:27 am

McCoyCORE wrote:
Mon Apr 12, 2021 12:23 am
Running macros and I constantly get the "Failed to open the project's database" error. I'm running a batch of about 100 files, but it doesn't happen at the same spot. Sometimes it crashes at file #2 and sometimes file #35, etc. Random. Basically my macros are useless because I can't batch run anything.
So there seems to be a bug in 3.0.0 that causes this problem. It should be corrected in 3.0.2. As I told Magimix98,
jademan wrote:
Sun Apr 11, 2021 2:04 pm
If you would like you may test the new 3.0.2 (3.0.1 was skipped) Release Candidate here.

Please do not do production work on any release candidate.

Post Reply