[Bug]: We had an unknown problem opening <file> - Error applying sql #2357

New Issue

GiteaMirror · 2026-02-28T20:11:45-06:00

GiteaMirror commented

2026-02-28 20:11:45 -06:00

Originally created by @dbene on GitHub (Aug 5, 2025).

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

When i try to open a budget file in my browser i get an error message that reads We had an unknown problem opening <file> (in German).

My browsers console log shows following output:

Got meta for documents-Actual-My-Finances-xxxxx-db.sqlite: Object { size: 3706880 }

Error applying sql: BEGIN TRANSACTION;

ALTER TABLE custom_reports RENAME COLUMN sort_by TO sort_by_old;
ALTER TABLE custom_reports ADD COLUMN sort_by TEXT DEFAULT 'desc';

UPDATE custom_reports SET sort_by = 'desc' where sort_by_old = 'Descending';
UPDATE custom_reports SET sort_by = 'asc' where sort_by_old = 'Ascending';
UPDATE custom_reports SET sort_by = 'budget' where sort_by_old = 'Budget';
UPDATE custom_reports SET sort_by = 'name' where sort_by_old = 'Name';

ALTER TABLE custom_reports DROP COLUMN sort_by_old;

COMMIT;

My last version was 25.4.0 (i think) and i already tried updating to 25.8.0 but it did not help.

In my server logs there are no errors shown. I would guess this is a client side issue.

How can we reproduce the issue?

using v25.8.0
try to open a local or synced file

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 11

Originally created by @dbene on GitHub (Aug 5, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When i try to open a budget file in my browser i get an error message that reads `We had an unknown problem opening <file>` (in German). My browsers console log shows following output: ```plain Got meta for documents-Actual-My-Finances-xxxxx-db.sqlite: Object { size: 3706880 } Error applying sql: BEGIN TRANSACTION; ALTER TABLE custom_reports RENAME COLUMN sort_by TO sort_by_old; ALTER TABLE custom_reports ADD COLUMN sort_by TEXT DEFAULT 'desc'; UPDATE custom_reports SET sort_by = 'desc' where sort_by_old = 'Descending'; UPDATE custom_reports SET sort_by = 'asc' where sort_by_old = 'Ascending'; UPDATE custom_reports SET sort_by = 'budget' where sort_by_old = 'Budget'; UPDATE custom_reports SET sort_by = 'name' where sort_by_old = 'Name'; ALTER TABLE custom_reports DROP COLUMN sort_by_old; COMMIT; ``` My last version was 25.4.0 (i think) and i already tried updating to 25.8.0 but it did not help. In my server logs there are no errors shown. I would guess this is a client side issue. ### How can we reproduce the issue? - using v25.8.0 - try to open a local or synced file ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 11

GiteaMirror added the bug label 2026-02-28 20:11:45 -06:00

GiteaMirror closed this issue

2026-02-28 20:11:46 -06:00

GiteaMirror commented

2026-02-28 20:11:46 -06:00

@youngcw commented on GitHub (Aug 5, 2025):

If you open that file in an incognito window does it give the same error? You can also try not skipping versions in the upgrade and go one at a time.

@youngcw commented on GitHub (Aug 5, 2025): If you open that file in an incognito window does it give the same error? You can also try not skipping versions in the upgrade and go one at a time.

GiteaMirror commented

2026-02-28 20:11:47 -06:00

@dbene commented on GitHub (Aug 5, 2025):

The bug also happens in following cases:

Incognito Window (Firefox)
Chromium base browser (Edge)
With ssh port forwarding to my local machine

You can also try not skipping versions in the upgrade and go one at a time.

I am currently trying that.

@dbene commented on GitHub (Aug 5, 2025): The bug also happens in following cases: - Incognito Window (Firefox) - Chromium base browser (Edge) - With ssh port forwarding to my local machine > You can also try not skipping versions in the upgrade and go one at a time. I am currently trying that.

GiteaMirror commented

2026-02-28 20:11:47 -06:00

@dbene commented on GitHub (Aug 5, 2025):

In 25.2.0 i get "Please update Actual!" and starting 25.2.1 i get the sql error from above.

@dbene commented on GitHub (Aug 5, 2025): In 25.2.0 i get "Please update Actual!" and starting 25.2.1 i get the sql error from above.

GiteaMirror commented

2026-02-28 20:11:47 -06:00

@dbene commented on GitHub (Aug 6, 2025):

updating Error: error in view v_transactions_internal: no such column: _.raw_synced_data

This is an error further down in the console log.

Is there a ways to extract the sqlite file and apply the correct patches manually?

@dbene commented on GitHub (Aug 6, 2025): > updating Error: error in view v_transactions_internal: no such column: _.raw_synced_data This is an error further down in the console log. Is there a ways to extract the sqlite file and apply the correct patches manually?

GiteaMirror commented

2026-02-28 20:11:48 -06:00

@joel-jeremy commented on GitHub (Sep 11, 2025):

updating Error: error in view v_transactions_internal: no such column: _.raw_synced_data

This is an error further down in the console log.

Is there a ways to extract the sqlite file and apply the correct patches manually?

@dbene You may have encountered a migration error on a prior upgrade. You should be able to get the sqlite file from the data directory inside Docker and check the __migrations__ table what last migration was successfully applied to the database

@joel-jeremy commented on GitHub (Sep 11, 2025): > > updating Error: error in view v_transactions_internal: no such column: _.raw_synced_data > > This is an error further down in the console log. > > Is there a ways to extract the sqlite file and apply the correct patches manually? @dbene You may have encountered a migration error on a prior upgrade. You should be able to get the sqlite file from the data directory inside Docker and check the `__migrations__` table what last migration was successfully applied to the database

GiteaMirror commented

2026-02-28 20:11:48 -06:00

@matt-fidd commented on GitHub (Sep 24, 2025):

This issue has been closed because there have been no comments after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.

@matt-fidd commented on GitHub (Sep 24, 2025): This issue has been closed because there have been no comments after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.

GiteaMirror commented

2026-02-28 20:11:48 -06:00

@dbene commented on GitHub (Oct 8, 2025):

In none of the two sqlite files was a __migrations__ table (user-files or server-files dirs).

But anyway i could solve my problem, but i am not sure why this did not work before.
I used my backup from april with v24.12.0 and i could open my budget again.
I updated minor version by minor version until 25.10.0 and migrated to the local app.

@dbene commented on GitHub (Oct 8, 2025): In none of the two sqlite files was a `__migrations__` table (user-files or server-files dirs). But anyway i could solve my problem, but i am not sure why this did not work before. I used my backup from april with v24.12.0 and i could open my budget again. I updated minor version by minor version until 25.10.0 and migrated to the local app.