BugNET

I have finally worked through the issues to upgrade our fairly large database from 0.67 to 0.7.854 e.g. no version number on the older databases so gives null exception, duplicate mail addresses,  demands a real username field for all users. The new version seems to have a number of very useful improvements e.g. alphabetic sorting of projects, my issues feature across all projects, the ability to fold projects in the project view (Not sure that this folding is remembered long term though), the count of items like attachments in the bug details view etc.

The only downside from our perspective was that the upgrade lost some of our per project security roles, which is not a great hardship. We also use Windows authentication  and so the user names are of the form  <domainname>/username.  The downside now is that a lot of the project based functions display using the user names rather than the display names as they used to. This means that we see the less user friendly <domainname>/username form a lot now. This is not a show stopper but does make it less user friendly.

Marty wrote Hi Neville, Looks like you have dealt with the problems I'm encountering now in upgrading from a v.66 to 7.854. I already handled the version number and got to the point of migrating users and have been getting 'username already in use'. Could this be related to what you referred to in your post: 'demands a real username field for all users'. I would appreciate any additional tips from your upgrade experience.

Try renaming the current admin user account to something different, ie "adminOld" or something like that and try the install again.

Davin Dubeau
BugNET - Core Developer

Marty wrote Thanks for your reply. I deleted all the rows in the Users table and just left the admin  user, renaming the username to something else. On that line of code where it calls the Membership.CreateUser, after checking the length of the password, I am now getting a different message: "The e-mail address is already in use". Since I don't have any other entry in the users table other than the adminold, it seems that it is trying to add the same row to the table and it is hitting the same email address. Any clue? Thanks.

Rename the admin email address  to something else and it should work after that.  Both usernames and email addresses must be unique for a user.

Davin Dubeau
BugNET - Core Developer