BLOCKER: Unable to open issue after upgrade v1.6.339

Topics: General
Nov 30, 2014 at 10:42 PM
Edited Nov 30, 2014 at 10:42 PM
After upgrading to v1.6.339 opening an issue page results in this exception

Thank you.

Server Error in '/' Application.

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.IndexOutOfRangeException: StatusEditVisibility

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:

[IndexOutOfRangeException: StatusEditVisibility]
System.Data.SqlClient.SqlDataReader.GetOrdinal(String name) +318
System.Data.SqlClient.SqlDataReader.get_Item(String name) +22
BugNET.Providers.DataProviders.SqlDataProvider.TGenerateDefaultValueListFromReader(SqlDataReader returnData, List1& defaultList) +2289
BugNET.Providers.DataProviders.SqlDataProvider.ExecuteReaderCmd(SqlCommand sqlCmd, GenerateListFromReader
1 gcfr, List`1& list) +175
BugNET.Providers.DataProviders.SqlDataProvider.GetDefaultIssueTypeByProjectId(Int32 projectId) +297
BugNET.Issues.IssueDetail.BindValues(Issue currentIssue) +1703
BugNET.Issues.IssueDetail.Page_Load(Object sender, EventArgs e) +799
BugNET.UserInterfaceLayer.BasePage.OnLoad(EventArgs e) +92
System.Web.UI.<LoadRecursiveAsync>d__4.MoveNext() +526
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +144
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +84
System.Web.Util.WithinCancellableCallbackTaskAwaiter.GetResult() +69
System.Web.UI.<ProcessRequestMainAsync>d__14.MoveNext() +6862

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34209
Dec 3, 2014 at 1:06 PM
This is now fixed with the rereleased 1.6.339 package.

Thank you.
Dec 3, 2014 at 2:17 PM
EPinci wrote:
This is now fixed with the rereleased 1.6.339 package.

Thank you.