Error 500 When Searching For Tags in 1.1

If you are having a problem using Fortress, post a message here.

Moderator: SourceGear

Post Reply
cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Error 500 When Searching For Tags in 1.1

Post by cs » Tue Mar 04, 2008 8:13 am

The following error appears:

Error 500: The Server is unable to process your request, click the login button to go back to the login page

Whenever I:

Click on a tag in the tags popup

OR

Enter any tag text in the tag text box on the Query page and click Submit.



At the moment tags crash the web client. Please let me know how we can use tags.

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Log File Excerpt

Post by cs » Tue Mar 04, 2008 8:53 am

Seems related to collation. Please note I did not have the 1.0.6 client installed on the server prior to install of 1.1

Sample from log file:

2008-03-04 14:26:49.733 pc.domain.local (10.0.0.196)-name_of_user : Server error 500 Cannot resolve collation conflict for equal to operation. 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.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

2008-03-04 14:27:31.436 pc.domain.local (10.0.0.196)-name_of_user : Helpers::QueryItems Cannot resolve collation conflict for equal to operation. 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-03-04 14:27:31.452 pc.domain.local (10.0.0.196)-name_of_user : Server error 500 Cannot resolve collation conflict for equal to operation. 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.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Tue Mar 04, 2008 10:07 am

What collation are you using?
Mary Jo Skrobul
SourceGear

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Post by cs » Tue Mar 04, 2008 10:09 am

For databases sgdragnet, sgvault and sgmaster we are using SQL_Latin1_General_CP1_CI_AS

Also in the majority of cases when using the query tool the error 500 appears and we are bounced back to the login page.

We upgraded from 1.06 to 1.1 just before these issues started.

Our search functionality is unusable.

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Tue Mar 04, 2008 10:36 am

Is the default collation for your SQL installation a different collation from that of your Fortress databases?

It could be that the temp tables created for the query are using the default collation on your server instead of the collation for the Fortress databases thus causing problems.
Mary Jo Skrobul
SourceGear

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Post by cs » Tue Mar 04, 2008 10:42 am

The tempdb database is using the Latin1_General_CI_AS collation.

This is indeed different from the SourceGear databases.

Has the Fortress upgrade changed something?

These crashing issues did not exist for some time until the upgrade today.

How can I fix the issue?

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Tue Mar 04, 2008 10:47 am

The problem is specific to some temp tables we are using to search tags (tags are new).

We will get you a sql script to fix your issue today and this will be fixed in the 1.1.1. release which will be out soon.

Thanks for the report.
Mary Jo Skrobul
SourceGear

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Tue Mar 04, 2008 11:02 am

Can you email me directly using the email button at the bottom of the page so we can get the email address to send the script to?

We don't like to post SQL scripts on the forum.

Thanks!
Mary Jo Skrobul
SourceGear

cs
Posts: 126
Joined: Mon Apr 11, 2005 5:20 am

Post by cs » Tue Mar 04, 2008 11:34 am

The revised stored procedure I was sent appears to have fixed the tables/data affected by the upgrade bug/issue.

Post Reply