Knowledgebase: Local
Error upgrading from 2.x to 3.x or later
Posted by Mont Rothstein on 20 December 2011 04:58 AM

Error upgrading from 2.x to 3.x or later

When upgrading a local repository from 2.x to 3.x or later an error occurs. The user visible error may be similar to:
DB Transaction Failed.
Command = UPDATE configuration SET value = '' WHERE key = 'ldap_user_name'
The error in the event log may be similar to:
12/19/2011 2:15:36 PM - Foray Configure Adams 3.6.11.4
DB Transaction Failed.
Command = UPDATE configuration SET value = '' WHERE key = 'ldap_user_name'

Inner Exception
DB Transaction Failed.
Command = UPDATE configuration SET value = '' WHERE key = 'ldap_user_name'

 at Foray.Adams.DatabaseManager.WriteCommandsToDatabase(List`1 commands, Int32 timeout) in C:\Code\Adams3.6\Foray.Adams\Managers\DatabaseManager.cs:line 1367

Inner Exception
Unable to open the database file
unable to open database file

 at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
 at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
 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.ExecuteNonQuery()
 at Foray.Adams.DatabaseManager.WriteCommandsToDatabase(List`1 commands, Int32 timeout) in C:\Code\Adams3.6\Foray.Adams\Managers\DatabaseManager.cs:line 1364
In the above instance the error occurred while performing the Default Data portion of the upgrade. It is possible it could also occur at other points.
The errors seems to be related to the creation of a .db-journal file while executing SQLite commands. In the above instance the first Default Data statement was an insert and it caused the .db-journal file to be created. The next command was the update statement seen above and it failed.
The fix was to run the update on a Windows XP box that wasn't part of a domain. It isn't clear if the issue was Win7 or being on a domain.

Comments (0)