BugNET

Open source issue tracking & project management
Welcome to BugNET Register | Login |

BugNET Forums

 
  Forum  Support  Upgrading probl...  .67 --> .7.820
Previous Previous
 
Next Next
New Post 3/28/2007 9:23 AM
User is offline BC
40 posts
No Ranking


Re: .67 --> .7.820 

OK,
I found the problem
first of all,
you should remove the folowing lines from the file: 0.7.820.0.SqlDataProvider.sql
PRINT N'Adding Administrator to Super Users Role'
EXEC dbo.BugNet_Role_AddUserToRole 'Admin',1
GO
(at the end of the file)
since this is the same as:
//add the admin user to the Super Users role.
Role.AddUserToRole("Admin", 1);
which can be found in the InstallBugNET() function

 

in my case, i upgraded my installation,
and my superuser was not named "Admin", but lets say "Abcd"
In your upgrade code you also say:
                //add the admin user to the super user role.
                Roles.AddUserToRole("Admin", Globals.SuperUserRole);
Which gives en error, because there is no Admin user in my installation.
You should (if possible get the correct username of the admin-account) before updating the database.

I hope my explanation is clear enough,
if not, just ask for more details. 


 
New Post 3/28/2007 12:55 PM
User is offline admin
641 posts
bugnetproject.com
1st Level Poster




Re: .67 --> .7.820 
Modified By admin  on 3/28/2007 11:57:45 AM)
 BC wrote

OK,
I found the problem
first of all,
you should remove the folowing lines from the file: 0.7.820.0.SqlDataProvider.sql
PRINT N'Adding Administrator to Super Users Role'
EXEC dbo.BugNet_Role_AddUserToRole 'Admin',1
GO
(at the end of the file)
since this is the same as:
//add the admin user to the Super Users role.
Role.AddUserToRole("Admin", 1);
which can be found in the InstallBugNET() function

 

in my case, i upgraded my installation,
and my superuser was not named "Admin", but lets say "Abcd"
In your upgrade code you also say:
                //add the admin user to the super user role.
                Roles.AddUserToRole("Admin", Globals.SuperUserRole);
Which gives en error, because there is no Admin user in my installation.
You should (if possible get the correct username of the admin-account) before updating the database.

I hope my explanation is clear enough,
if not, just ask for more details. 




The script assumes you have not renamed your admin account.    If we do not add the admin account to the superuser role you will not be able to access the administration area after upgrade.

When upgrading the scripts run in sequence so in 0.66 -> 0.7 B it migrates everything to the asp.net role provider, then in 0.7 - 0.7.820 it migrates it back to a custom implementation  so thats why the addusertorole occurs in two places.

This won't be needed in future installs but was necessary when turfing the asp.net role provider and back to a custom solution.

Davin Dubeau
BugNET - Core Developer

 
New Post 3/29/2007 1:08 AM
User is offline BC
40 posts
No Ranking


Re: .67 --> .7.820 
Ok,
I changed the admin accounts username back to admin,
run the update, all went fine
and then changed the username back to what is was before.

I have only one question left now,
the field "Version" in the table "HostSettings" nog contains the value "@VERSION@.0",
doesn't this has to be 0.7.820 or somethins similar?

Thank you for your help updating my installation.
 
New Post 3/29/2007 5:26 AM
User is offline admin
641 posts
bugnetproject.com
1st Level Poster




Re: .67 --> .7.820 
 BC wrote
Ok,
I changed the admin accounts username back to admin,
run the update, all went fine
and then changed the username back to what is was before.

I have only one question left now,
the field "Version" in the table "HostSettings" nog contains the value "@VERSION@.0",
doesn't this has to be 0.7.820 or somethins similar?

Thank you for your help updating my installation.


Yes it does, are you working with the source package?    These tokens get replaced in the build with the proper build number.

Davin Dubeau
BugNET - Core Developer

 
New Post 3/29/2007 6:49 AM
User is offline BC
40 posts
No Ranking


Re: .67 --> .7.820 

 Davin wrote
Yes it does, are you working with the source package?    These tokens get replaced in the build with the proper build number.

Apperently I mixed some build & source packages,
I redid the update, everything is fine now.

 
Previous Previous
 
Next Next
  Forum  Support  Upgrading probl...  .67 --> .7.820

Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.