0.67 -> 0.7 beta 1 - Upgrading problems

BugNET Forums

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

11/29/2006 1:43 PM

	scalvillo
6 posts
www.calvillo.net/sean

Re: 0.67 -> 0.7 beta 1

Excuse my ignorance, but how would i compare my hostsettngs table with the BugNet.Data.SQLDataProvider?

I am trying to make the release work. I would rather not have to deal with the source code, but I can if you tell me that is the only solution.

11/30/2006 6:19 PM

	admin
641 posts
bugnetproject.com

Re: 0.67 -> 0.7 beta 1

I have successfully upgraded the instance of BugNET at support.bugnetproject.com . I ran into a few issues in doing this and may be the same ones that you are having.

Using enterprise manager I noticed that some of the stored proc's had an owner of the username that is used on my webhosting to access the database instead of the "dbo" owner. When I did the upgrade this resulted in a failed upgrade and made duplicate copies of the stored procedures, one with the user account and another with the "dbo" owner. When I ran the application I obtained the same error as reported earlier in this thread along with a "cannot find users object" because the application was running the old stored procedure.

Thats great, how do I fix it?

You can run the script found in this Microsoft KB Article that will make statements that you can run to replace a dbowner of all objects in a database to "dbo". This will allow the proper stored proc's to be upgraded.

The other issue lies in the code in the global.asax, which clears and hides any error messages that would normally be reported to the web browser.

Check the log table in your BugNET database for detailed information if you are getting a blank page.

If you still have issues after these changes we will work to resolve them.

Davin Dubeau
BugNET - Core Developer

11/30/2006 8:54 PM

	scalvillo
6 posts
www.calvillo.net/sean

Re: 0.67 -> 0.7 beta 1

Davin,

Thanks for the follow up. I took my .67 database and I used the MS script to correct my stored procedures to be owned by dbo and not by the user name I use in the application. Unfortunately this did not help my problem. Again, the first time I browsed to Install.aspx, I received the error that the log table didn't exist. So then I created the log table manually so that I could validate the root exception. The stack is below. Any help is appreciated. If you prefer, I can get you on my server to troubleshoot... or we can continue to communicate this way.

Sean

System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at BugNET.Install.Install.UpgradeBugNET()
   at BugNET.Install.Install.UpgradeApplication()
   at BugNET.Install.Install.Page_Load(Object sender, EventArgs e)
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   --- End of inner exception stack trace ---
   at System.Web.UI.Page.HandleError(Exception e)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at ASP.install_install_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

12/11/2006 3:01 PM

	MarkM
2 posts

Re: 0.67 -> 0.7 beta 1

Well I finally got a chance to look at this again and I believe I have found the problem. There is a method named GetInstalledVersion(). For whatever reason, our .67 database does not have a record for the version so the sql command SELECT SettingValue FROM HostSettings WHERE SettingName='Version' ends up returning NULL from the method.

The calling method (int DatabaseVersion = Convert.ToInt32(GetInstalledVersion().Replace(".", ""));) ends up getting a fatal exception and the upgrade stops.

I executed the following command using SQL Server Management Console against our bugnet database and now the upgrade will execute.

if not exists(select * from hostsettings where settingname = 'Version')
INSERT INTO HostSettings(SettingName,SettingValue) Values('Version','0.67')

Page 3 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.