BugNET

Open source issue tracking & project management
  search

Forums

HomeHomeSupportSupportUpgrading BugNE...Upgrading BugNE...0.7.921 to 0.7.942 SQL errors 0.7.921 to 0.7.942 SQL errors
Previous
 
Next
New Post
7/2/2009 6:20 AM
 
User is offline Davin Dubeau
1st Level Poster


Davin Dubeau's Avatar

bugnetproject.com
Joined: 3/2/2006
Posts: 1425

LisaM wrote

I did the script against db and cleaned it up.  Since all the errors were such that keys already existed and such, I just deleted all that.  Got it to run.  Ran install again and now got yellow screen of death.

 

Server Error in '/' Application.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[FormatException: Input string was not in a correct format.]
   System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2755599
   System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +112
   BugNET.Install.Install.UpgradeBugNET() +833
   BugNET.Install.Install.UpgradeApplication() +395
   BugNET.Install.Install.Page_Load(Object sender, EventArgs e) +270
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

This error looks like it can't parse the version number stored in the host settings table, maybe recycling the application in IIS would do it.

Davin Dubeau

follow us on twitter facebook users group google plus
 
New Post
7/2/2009 6:49 AM
 
User is offline Lisa
No Ranking

Joined: 6/4/2008
Posts: 15

I got the same error after cycling it in iis.  0.7.921.0 is the version in my hostsettings table.  ADPassword is blank and ADPath is blank and ADUserName is blank.  Is that ok?
 
New Post
7/2/2009 7:26 AM
 
User is offline Lisa
No Ranking

Joined: 6/4/2008
Posts: 15

I got it working but for the record here is what I did.  Backed up my BugNet DB.  Deleted DB and recreated blank DB.  Ran install so it set it up from scratch.  Then did a compare between the databases and synced the 3 objects left that were different.  Then put backed up DB over the new DB and things work fine now.  So far.  Must test the email ssl fix to be 100% thrilled.
 
New Post
7/9/2009 3:45 AM
 
User is offline Damien McGivern
No Ranking

Joined: 4/8/2008
Posts: 7

Are you sure this is the latest script as the header states that is was generated on March 08

http://bugnet.svn.sourceforge.net/viewvc/bugnet/trunk/BugNET/src/BugNET_WAP/Install/dbscripts/0.7.942.0.SqlDataProvider.sql?revision=826

 

/**************************************************************************
-- -Generated by xSQL SDK for Schema Comparison and Synchronization
-- -Date/Time: March 08, 2009 12:53:37
**************************************************************************/

 

 
 
New Post
7/9/2009 3:54 AM
 
User is offline Damien McGivern
No Ranking

Joined: 4/8/2008
Posts: 7

I downloaded the latestversion you linked to and I get the following output

 

Cleaning up all deleted bugs and related tables

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)
Cleaning up project tables

(35 row(s) affected)

(21 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)
Deleting orphaned records in user projects table

(8 row(s) affected)
Deleting orphaned records in user roles table

(9 row(s) affected)

(0 row(s) affected)
Updating bugs with orphaned assigned user ids

(0 row(s) affected)
Updating bugs with orphaned reporter user ids

(0 row(s) affected)
Updating bugs with orphaned last updated user ids

(0 row(s) affected)
Updating bugs with orphaned components

(0 row(s) affected)
Updating bug attachments with orphaned users

(0 row(s) affected)
Updating bug comments with orphaned users

(0 row(s) affected)
Updating bug history records with orphaned users

(0 row(s) affected)
Deleting bug notifications for orphaned users

(0 row(s) affected)
Updating bug time entries for orphaned users

(0 row(s) affected)
Updating project creators with orphaned user ids

(0 row(s) affected)
Updating project managers with orphaned user ids

(0 row(s) affected)
Updating project mailboxes with orphaned users

(0 row(s) affected)
Updating bugs with missing versions

(225 row(s) affected)
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_Bug_Component' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

(1 row(s) affected)
Msg 547, Level 16, State 0, Line 2
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_Bug_FixedInVersionId". The conflict occurred in database "aurion_issuetracting_bugnet", table "dbo.Version", column 'VersionID'.

(1 row(s) affected)
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_Bug_Priority' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

(1 row(s) affected)
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_Bug_Project' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

(1 row(s) affected)
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_Bug_Resolution' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

(1 row(s) affected)
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_Bug_Status' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

(1 row(s) affected)
Msg 2714, Level 16, State 4, Line 2
There is already an object named 'FK_Bug_Type' in the database.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.

(1 row(s) affected)
Msg 547, Level 16, State 0, Line 2
The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_UserRoles_aspnet_Users". The conflict occurred in database "aurion_issuetracting_bugnet", table "dbo.aspnet_Users", column 'UserId'.

(1 row(s) affected)

(1 row(s) affected)
Database synchronization script failed
 
 
 Page 3 of 4
Previous1234Next 
Previous
 
Next
HomeHomeSupportSupportUpgrading BugNE...Upgrading BugNE...0.7.921 to 0.7.942 SQL errors 0.7.921 to 0.7.942 SQL errors


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.
Copyright © 2011 BugNET   Terms Of Use  Privacy Statement  Page generated in 0.0624012 seconds.