Hi Markus101, I’ve had the same problem a few times now - having to fix it with SQLiteBrowser each time.
Are you able to put some error handeling in for the RelativePath column, such as
if exists rename to RelativePath.old and create a new one.
Thanks for the great app.
@gatehead can’t see how you would have it multiple times, the migration only runs one time (if it was successful). How are you reproducing it?
Over the last few months i have had to do this after auto updates sporatically.
It has worked before in the past, using SQLite Browser to delete the RelativePath column under EpisodeFiles - however this time I’m getting an error about being unable to find EpisodeFiles\ID on boot now after doing so.
Same goes for all of my backups created by the internal schedule, same ID column problem.
I will PM you links to two DB’s, one from today that still contains RelativePath and another from 3 days ago that gets the ID column problem.
I did notice once it gets a DB without RelativePath in it, it seems to delete the entire contents of the DB before complaining it cant find ID as the filesize drops to 1kb almost instantly.
Which branch are you using?
Which NzbDrone version is installed?
What is the actual error you’re getting (from the log files)?
This only became a requirement in the master branch recently, previously it was only in develop.You can’t drop it an expect things to work though.
The “ID” issue one is likely the same issue mentioned in the other thread, which is fixed in 2.0.0.1856 and up, but it requires following the steps I posted. Both DBs you gave me migrated without issue to the latest version of the DB, used for the latest master release.
It would appear I’m on 1855 however i have run the latest nzbdrone.master.exe twice today.
Included is an imgur link that shows the first time I had the problem in July and required me to download the SQLite Browser program to remove the RelativePath column, which did fix the application until today. I have also had it happen on a co-workers install at about the same time but the same db edit fixed it then too.
Here you can see the files were downloaded from the master/latest branch today at 11:54am and 1:31pm.
Is it possible the http://update.nzbdrone.com/v2/master/latest/NzbDrone.master.exe is still 1185 instead of 1186?
Below is a log running the DB backup from the 21st.
14-8-26 14:45:57.0|Info|Bootstrap|Starting NzbDrone - D:\Program Files (x86)\NzbDrone\NzbDrone.Console.exe - Version 2.0.0.1855
14-8-26 14:45:58.5|Info|MigrationLogger|*** Migrating data source=C:\ProgramData\NzbDrone\nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal ***
14-8-26 14:45:58.9|Info|MigrationLogger|*** 54: rename_profiles migrating ***
14-8-26 14:45:59.7|Info|MigrationLogger|*** 55: drop_old_profile_columns migrating ***
14-8-26 14:46:00.0|Info|MigrationLogger|*** 56: add_mediainfo_to_episodefile migrating ***
14-8-26 14:46:00.0|Info|MigrationLogger|*** 57: convert_episode_file_path_to_relative migrating ***
14-8-26 14:46:00.0|Error|MigrationLogger|SQL logic error or missing database
no such column: Id
14-8-26 14:46:00.1|Fatal|ConsoleApp|EPIC FAIL!
System.Data.SQLite.SQLiteException (0x80004005): SQL logic error or missing database
no such column: Id
at System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)
at System.Data.SQLite.SQLiteCommand.BuildNextCommand()
at System.Data.SQLite.SQLiteCommand.GetStatement(Int32 index)
at System.Data.SQLite.SQLiteDataReader.NextResult()
at System.Data.SQLite.SQLiteDataReader…ctor(SQLiteCommand cmd, CommandBehavior behave)
at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
Thanks for spending all this time
The only reason you would have had to drop that column is if you switched to develop, then back to master, since it wasn’t part of master yet. But since there isn’t really any more info and it has no relation to this error there isn’t anything I can do.
No, it would have been updated, 2.0.0.1861 is available for master now and I can confirm it is the correct version.
2.0.0.1855 is broken in some cases, as described in the other thread, you will need to upgrade to 2.0.0.1861 and restore from your backup (drone takes one just before upgrading).
We’re making improvements to the database migrations to help reduce migration issues in the future, but this was an edge case even those changes wouldn’t catch.
Any chance you recently moved the binary location to %programdata%\nzbdrone\bin by default instead of checking for the previous installed location in the installer?
I’ve always had it on my d:\ drive - that would be why its launching as an older version, as the new one is in the program data dir.
The installer always installed it to ProgramData. If you installed via zip install before then that would explain the sudden change. You can uninstall it and grab the latest zip from: http://update.nzbdrone.com/v2/master/latest/