Keyword Search Across Projects does not work on 1.1.3

[seejee]

Hello,

After upgrading Fortress to 1.1.3, our team is finding that keyword searches across projects (using either the Query Projects screen or using the Goto Item search on the Projects-At-A-Glance page) is not working. Both result in an Error 500.

To reproduce: (Scenario 1)

Go to the Projects-At-A-Glace page.
Type in a non-numerical value into the Goto Item box.
Press Enter.

To reproduce: (Scenario 2)

Go to the Query Across Projects screen.
Type in a non-numerical value into the Keyword text box.
Click Submit.

What actually happens:

Error 500.

What should happen:

I should see a list of results from all projects that match the keyword I typed into the Goto Item/Keyword box.

Our QA/Testing team uses this feature extensively, so this flaw has negatively impacted their ability to use Fortress effectively.

Thank you,

Chris G

[lbauer]

I was able to reproduce this on two Fortress servers. This is the first report we've had of a 500 error in 1.1.3, so we'll need to detemine what the problem is.

[cs]

We are being impacted by this bug straight after upgrading to 1.1.3.

Stuff like this puts us off from taking new versions from you guys.

In event log:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 07/10/2008
Time: 13:59:54
User: N/A
Computer: MYSERVER
Description:
Event code: 3005 Event message: An unhandled exception has occurred.
Event time: 07/10/2008 13:59:54
Event time (UTC): 07/10/2008 12:59:54
Event ID: 8ad400fb4bef4641944be2e6f55a4310
Event sequence: 102
Event occurrence: 11
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Fortress-6-128678552897048909
Trust level: Full
Application Virtual Path: /Fortress
Application Path: C:\Inetpub\wwwroot\Fortress\
Machine name: MYSERVER
Process information:
Process ID: 2188
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
Request information:
Request URL:
Request path:
User host address:
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 6
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at MantisServiceLib.Helpers.LogMessage(DNLogEntryType let, String strMsg)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss, Boolean signOut)
at MantisServiceLib.Helpers.DeleteSession(HttpSessionState hss)
at Mantis.Global.Session_End(Object sender, EventArgs e)
Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[cs]

Dump in log file:

2008-10-08 12:22:57.301 dsl-JohnUser.mydomain.local (10.0.0.196)-JohnUser : Helpers::QueryItems The column prefix 'p' does not match with a table name or alias name used in the query. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at MantisSQLService.MantisSQLService.QueryItems(MantisSqlConn conn, Int32 nAuthUID, MantisItemQueryFilter miqf, String strXmlKeywords, String strXmlAnyTags, String strXmlAllTags, String strAuthToken, Boolean bPageResults, Boolean bNotPagedRetrieveItemContents, String& strQueryToken, Int32& nRowsRetrieved, MantisItemExpandedColl& meiColl, CloudColl& clouds) at MantisSQLService.MantisSQLService.QueryItems(MantisSqlConn conn, Int32 nAuthUID, MantisItemQueryFilter miqf, String strXmlKeywords, String strXmlAnyTags, String strXmlAllTags, Boolean bRetrieveItemContents, MantisItemExpandedColl& meiColl, CloudColl& clouds) at MantisServiceAPI.MantisServiceAPI.QueryItems(Int32 nAuthUID, String strAuthToken, MantisItemQueryFilter miqf, Boolean bRetrieveItemContents, MantisItemExpandedColl& meiColl, CloudColl& clouds) at MantisServiceLib.Helpers.QueryItems(MantisItemQueryFilter qf, Boolean bRetrieveContents, MantisItemExpandedColl& mItems, CloudColl& clouds)
2008-10-08 12:22:57.301 dsl-JohnUser.mydomain.local (10.0.0.196)-JohnUser : Server error 500 The column prefix 'p' does not match with a table name or alias name used in the query. at MantisServiceLib.Helpers.QueryItems(MantisItemQueryFilter qf, Boolean bRetrieveContents, MantisItemExpandedColl& mItems, CloudColl& clouds) at Mantis.SortByMilestoneControl.GetItems() at Mantis.SortByMilestoneControl.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

[lbauer]

This is a known issue and is logged as bug 13729. We are working on a fix for this. We don't have a release date as yet.

[jeremy_sg]

I've identified the cause of this problem, and a fix has been checked in. If you would like to try a prerelease 1.1.4 build, please email support at sourcegear.com ATTN: jeremy with a link to this thread.