Syncovery Support Forum

More logs on the various DB issues if that might help:

25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:03: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:03: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
25-12-22 19:00:04: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:04: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:10: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:10: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:10: Trying to close and re-open the database.
12/25/22 19:00:10: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:11: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:11: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:11: Trying to close and re-open the database.
12/25/22 19:00:11: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/2022 19:00:11: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/2022 19:00:11: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/2022 19:00:11: Trying to close and re-open the database.
12/25/2022 19:00:11: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:12: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:12: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:12: Retrying the failed operation ReadString, AttemptCounter=1
12/25/2022 19:00:12: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/2022 19:00:12: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/2022 19:00:12: Retrying the failed operation ReadString, AttemptCounter=1
12/25/22 19:00:12: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:12: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:12: Trying to close and re-open the database.
12/25/22 19:00:12: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:15: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:15: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:15: Trying to close and re-open the database.
12/25/22 19:00:15: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:15: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:15: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:15: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:15: Retrying the failed operation ReadString, AttemptCounter=1
12/25/22 19:00:15: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:15: Retrying the failed operation ReadString, AttemptCounter=1
12/25/22 19:00:15: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:15: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:15: Retrying the failed operation ReadString, AttemptCounter=1
12/25/22 19:00:20: TTGSQLIniFile.WriteString Exception: SQL Error: database is locked: bad parameter or other API misuse (UPDATE DATA SET "VALUE"=? WHERE NAME=? AND "VALUE"=? AND ID=? AND SECTIONID=?)
12/25/22 19:00:20: Database exception (WriteString): SQL Error: database is locked: bad parameter or other API misuse (UPDATE DATA SET "VALUE"=? WHERE NAME=? AND "VALUE"=? AND ID=? AND SECTIONID=?), AttemptCounter=1
12/25/22 19:00:20: Trying to close and re-open the database.
12/25/22 19:00:20: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:20: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:20: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:20: Retrying the failed operation WriteString, AttemptCounter=1
12/25/22 19:00:24: TTGSQLIniFile.WriteString Exception: 0 record(s) updated. Only one record should have been updated. (UPDATE DATA SET "VALUE"=? WHERE NAME=? AND "VALUE"=? AND ID=? AND SECTIONID=?)
12/25/22 19:00:24: Database exception (WriteString): 0 record(s) updated. Only one record should have been updated. (UPDATE DATA SET "VALUE"=? WHERE NAME=? AND "VALUE"=? AND ID=? AND SECTIONID=?), AttemptCounter=1
12/25/22 19:00:24: Trying to close and re-open the database.
12/25/22 19:00:24: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:24: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:24: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:24: Retrying the failed operation WriteString, AttemptCounter=1
12/25/2022 19:00:31: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/2022 19:00:31: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/2022 19:00:31: Trying to close and re-open the database.
12/25/22 19:00:31: TTGSQLIniFile.GetSectionID Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:31: Database exception (qrySectionByName.Open/First): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:31: Trying to close and re-open the database.
12/25/22 19:00:31: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/2022 19:00:31: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:31: TTGSQLIniFile.GetSectionID Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:31: Database exception (qrySectionByName.Open/First): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:31: Trying to close and re-open the database.
12/25/22 19:00:31: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:31: TTGSQLIniFile.GetSectionID Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:31: Database exception (qrySectionByName.Open/First): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:31: Trying to close and re-open the database.
12/25/22 19:00:31: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:32: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:32: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:32: Retrying the failed operation qrySectionByName.Open/First, AttemptCounter=1
12/25/22 19:00:34: TTGSQLIniFile.ReadString Exception: SQL Error: database is locked: bad parameter or other API misuse
12/25/22 19:00:34: Database exception (ReadString): SQL Error: database is locked: bad parameter or other API misuse, AttemptCounter=1
12/25/22 19:00:34: Trying to close and re-open the database.
12/25/22 19:00:34: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
12/25/22 19:00:35: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:35: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:35: Retrying the failed operation qrySectionByName.Open/First, AttemptCounter=1
12/25/2022 19:00:35: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/2022 19:00:35: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/2022 19:00:35: Retrying the failed operation ReadString, AttemptCounter=1
12/25/22 19:00:36: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:36: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:36: Retrying the failed operation ReadString, AttemptCounter=1
12/25/22 19:00:36: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
12/25/22 19:00:36: /volume1/@appdata/Syncovery/Syncovery.cfg entry count in section Profiles: 18
12/25/22 19:00:36: Retrying the failed operation qrySectionByName.Open/First, AttemptCounter=1

This may also explain quite a few things.
I looked in the /volume1/@appdata/Syncovery/Database folder and I only see two databases in there, even though I created 18 profiles. That leads me to a theory on the database issue.

I have two "flavors" of profiles on this NAS. Let's call them A and B.

For flavor A I have 9 profiles. They all behave the same other than the folders they process.

For flavor B I have 9 profiles. They all behave the same other than the folders they process.

I created the first A profile from scratch, and then to create the second A profile I edited the first, changed the name, changed the folders, and saved it. I repeated the process for the remaining 7 A profiles.

I created the first B profile from scratch, and then to create the second B profile I edited the first, changed the name, changed the folders, and saved it. I repeated the process for the remaining 7 B profiles.

In the Database folder I have two databases named:
A.syncsq3db
B.syncsq3db

I am pretty sure that is where my database conflicts are coming from, and possibly the rest of the weirdness I have going on. So I went into those two profiles that mantched the database names and clicked on Special / Database / Delete Database, and now they are both gone. Then I went into the first profile at the top of the grid, into Special / Database, and typed in the name of the profile into the "Database Name To Use" field, then saved the profile. No database was created and when editing the profile the "Database Name To Use" field was still empty, so I tried a random name, repeat, still empty, no database created. Still no joy.

Restarted the Syncovery app on NAS Package Center to see if I could get back editing control (because that has sometimes worked for me before). Repeated the database name procedure above using the name of the profile. NO database was created but the "Database Name To Use" field did retain the name of the profile. Random database name also did not create a database but the "Database Name To Use" field did retain the random name.

Hmmm.

Created an entirely new profile from scratch. Did not create a database, which I truly expected it would. The profile seemed to be created ok so, I guess, I'm at a loss with this current line of thinking on how a database gets created ?

I also found the .old.old.old. pattern for /volume1/@appdata/Syncovery/CfgBackups/Syncovery.empty - see SyncoveryEmpty.jpg attachment.

Maybe that's normal and you'll tell me so. It just looks supsicious to me, especially on a 256 character boundary like that.

No databases in /volume1/@appdata/Syncovery/.Syncovery/Database either.
Pardon the rapid fire posts. Didn't see this one before.

------------------------------

So to summarize, the questions I have are:

Are those really long ".old.old.old.old." filenames normal?

Where should I expect to find databases for profiles? Here? Somewhere else?

/volume1/@appdata/Syncovery/Database
/volume1/@appdata/Syncovery/.Syncovery/Database

I presume
/volume1/@appdata/Syncovery/Database
since that is what the path is set to in Program Settings

How do I create a database for each profile? The Special / Database / "Database Name to Use" field doesn't seem to work for me, or if that should work and I should start over again and this time not use the "edit/save of existing profile creates new profile" shortcut, that's fine but make every profile from scratch. Or would the "edit/save of existing profile creates new profile" shortcut work as long as before I save it I type in an actual database name.

More insight.

On Exact Mirror profiles I understand now that the database only gets created when I have:
"Comparison / More / Remember Results"
checked, even though "Binary comparison of Existing files when building the File List" to the left is not checked. I thought those two were related since they were on the same line but apparently not.

I had left "Remember Results" checked on only two profiles (my oversight) which is why I ended up with only databases for those two profiles and not the other profiles, so that was a self-inflicted rabbit hole I fell into with my previous theory.

I have started everything from scratch for another test run and created 5 exact mirror profiles, all the same except for the source and target folders, all running at 45 minutes past the hour. "Remember Results" not checked.
First run went fine. No databases created, as expected. Second run also went fine.

I created a second set of 5 exact mirror profiles for a different set of folders. Those all seem to be running fine as well. although one will take 1.5 hours to complete tso it will still be running when the scheduler tries to fire the job off again. I'll see if anything strange happens then.

Still no sign of the ".old.old.old." pattern anywhere but I think that will only manifest when you have those database locked conditions, which I've eliminated by simply not having databases. Perhaps finding those may be useful to you anyway if it ends up being a bug.

Will post more results in a bit.