0.67 -> 0.7 beta 1 - Upgrading problems

BugNET Forums

Forum Support Upgrading probl... 0.67 -> 0.7 beta 1

11/17/2006 10:37 AM

	admin
641 posts
bugnetproject.com

Re: 0.67 -> 0.7 beta 1

MarkM wrote
I am also having issues upgrading from 0.67. I am able to install the new version without doing an upgrade, so my environment appears to be setup correctly. I was looking at the install.aspx code and tried to detect what order the SQL install scripts are being run. Is it an option to just run the scripts directly?

Looking at the install aspx, it looks like the scripts need to be run in this order: InstallCommon.sql, InstallMembership.sql, InstallProfile.sql, InstallRoles.sql, BugNET.Schema.SqlDataProvider.sql and BugNET.Data.SqlDataProvider.sql. But I get errors with missing fields, etc. when attempting to run BugNET.Schema.SqlDataProvider.sql. I tried running 0.7.719.0.SqlDataProvider.sql prior to that script, but I am getting various errors about inserting nulls, etc. Am I missing something trying to run the scripts directly, perhaps I am running them in the incorrect order? It appears that 0.7.719.0.SqlDataProvider.sql is needed but I am not seeing it called from the install routine?

For an upgrade the following is performed:

InstallCommon.sql
InstallMembership.sql
nstallProfile.sql
InstallRoles.sql
Users are migrated from old user tables to new membership provider through code.
The upgrade script is run.

You may not have seen the upgrade code that will check the database versions and then run all the scripts upgrade scripts applicable in the dbscripts folder.

Unfortunatly I found no way to migrate users without the code which makes it impossible to run the scripts by themselves.

Davin Dubeau
BugNET - Core Developer

11/28/2006 7:12 PM

	scalvillo
6 posts
www.calvillo.net/sean

Re: 0.67 -> 0.7 beta 1

Did anyone find a solution to this. I am getting the same problem with the Invalid object name 'Log' error. Here is my configuration:

Windows 2003 sp1
SQL Server 2005 Express
Upgrading from .67

My BugNET directory is wide open from a security perspective. I don't have any users with duplicate email address or user names. Any help is appreciated.

Sean

11/29/2006 11:59 AM

	scalvillo
6 posts
www.calvillo.net/sean

Re: 0.67 -> 0.7 beta 1

Ok, I went ahead and just ran the script to create the log table as I figured if I could allow the installer to log the exception it was getting, I could get at the root problem instead of just "the log table does not exist.". With the original web.config edited with my proper db connect string, I now get messages in my log table when running the installer for the first time. The error now is

System.Data.SqlClient.SqlException: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

The full error stack can be found at http://support7.triteknyc.com/bugnet7errors.csv

I am assuming that this stored procedure is added by the installer itself when it runs InstallCommon.sql. So my question is why is it skipping over the running of the necessary dbscripts.

Sean

11/29/2006 12:12 PM

	scalvillo
6 posts
www.calvillo.net/sean

Re: 0.67 -> 0.7 beta 1

Just for giggles, I went ahead an ran the following scripts with success.

InstallCommon.sql

InstallMembership.sql

nstallProfile.sql

InstallRoles.sql

Now, I just get the following error in the log table:

System.FormatException: String was not recognized as a valid Boolean

Can someone provide a modified installer that just moves the users into the new aspnet authentication and then I can just run the upgrade script. I have no idea why the installer is not running the database scripts it self... or if someone can provide a solution my previous posts, I can just start from scratch.

11/29/2006 1:31 PM

	admin
641 posts
bugnetproject.com

Re: 0.67 -> 0.7 beta 1

scalvillo wrote
Just for giggles, I went ahead an ran the following scripts with success.

InstallCommon.sql

InstallMembership.sql

nstallProfile.sql

InstallRoles.sql

I usually get this error when the application is trying to retrieve a hostsetting that doesn't exist. Can you compare your hostsettings table and the BugNet.Data.SqlDataProvider.sql to see if there are any differences.

If you are compiling the source there is a line in the global.asax that should be removed "Server.ClearLastError()" so that errors are displayed at the page level. This should allow these errors not to be hidden.

Davin Dubeau
BugNET - Core Developer

Page 2 of 3

Forum

Support

Upgrading probl...

0.67 -> 0.7 beta 1

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.