Unable to upgrade from 3.2 to 3.5

When upgrading from 3.2 to 3.5, I am receiving an error message stating;

System.Data.OleDb.OleDbException: The statement has been terminated.

Violation of UNIQUE KEY constraint 'IX_Group'. Cannot insert duplicate key in object 'dbo.Group'.

   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

   at GleamTech.FileVista.UpdatePage.c()

   at GleamTech.FileVista.UpdatePage.ButtonNext_Click(Object sender, EventArgs e)

Andrew,
Did you have a group named "Administrators" in the previous version? The update wizard will create the system group "Administrators" and it seems there is a conflict.

If you made a backup of you DB, please rename this group to some other name and put it App_Data\database folder and run the update wizard again. This is because your db is changed partly until the error so you need to restart the update with the initial db. If there is no backup, we can do the remaining modification to your db (.mdb file)  manually if you send it to us via email.

Arg! Now I'm getting this error.

System.Data.OleDb.OleDbException: The statement has been terminated.

The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Membership_User". The conflict occurred in database "FileVista", table "dbo.User", column 'UserID'.

   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

   at GleamTech.FileVista.UpdatePage.c()

   at GleamTech.FileVista.UpdatePage.ButtonNext_Click(Object sender, EventArgs e)

Arrrgggg! This is driving me nuts.

I got past all the db problems (a simple transactional install could have prevented all this) but now I'm getting an error that states the given key isn't in the directory.

HELP!

I can not update from version 3.2 to 3.5. I have the configuration in a SQL Server database and when I try to upgrade I get this error:

ERROR

System.Data.OleDb.OleDbExceptions: Cannot find the object "PermissionEntry" because it does not exist or you do not have permissions....

The strange thing is that the table PermissionEntry exists in the database and the web application can access the table. 

Any ideas?

Whatever user you're using to login to the SQL server as needs DBO access to the database.

Andrew,
Sorry, the update is one way procedure so you need be careful and do it correctly at the first time. I don't know your case but some customers select the wrong version range on the first page. Even if you select the correct version at the second time it’s too late because your database structure is already changed.

Anyway, if you solved the database update issues, then please restart FileVista to get rid of the error state. You can force a restart by touching web.config, ie. opening and then saving it. I also recommend using CTRL + F5 to refresh browser's cache if you receive any JS error after the update.

Joakim,
Your issue seems to be permission related. The application may access the table but the update wizard needs more permissions because it changes the database structure. Please give the user (which you use for connecting to SQL Server) database editing permissions temporarily for running the update wizard. You can then remove the permissions.

Once I was able to get everything cleared out of the db and re-run the update I was able to get the thing running by editing the web.config so the app would restart.

Thanks.

Thanks,

Now I'm running 3.5

/Joakim