SourceGear Support

This is a new problem that's appeared since we updated to Fortress 1.1.0.16216. Run a cross-project query, and on the query results page click the Printable button. The new page contains the message "An unknown error has occurred". This only seems to happen with cross-project queries, quer...

Logging out and back in again works around the bug/issue. This may prove inconvenient however.

Can you reproduce this issue?

The Milestone drop down in the Item editing screen does not update if changes are made to the Milestone Name. Steps: 1) Create a milestone 2) Add an item using that Milestone 3) Edit the Milestone Name 4) Edit the newly created item or add a new Item - the milestone drop down has the old milestone n...

The queries are cross-project. Glad you can reproduce the issue.

No, sorry, are you asking me to?

In the server Application event log we have multiple instances of: I can't track down exactly what is causing this. Event Type: Warning Event Source: ASP.NET 2.0.50727.0 Event Category: Web Event Event ID: 1309 Date: 05/03/2008 Time: 11:12:49 User: N/A Computer: SERVERNAME Description: Event code: 3...

On initial login the list is ordered correctly. After viewing items and clicking Home, etc, the list ordering is broken.

Steps to replicate: 1) Log in 2) Click Item Tracking 3) Click on any Saved Query - the query results then appear 4) Click Home - THIS JUMPS TO QUERY PAGE NOT HOME The saved queries drop down is empty and the list of saved queries on the right hand side menu 'Saved Queries' is empty. Clicking Home ag...

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

When I click 'Home' the projects appear in the wrong order.

Projects At-A-Glance

Since upgrading to 1.1 our projects have been re-ordered. Previously they were shown in the Projects window and drop-down in alphabetic order. This has changed to another order I'm not familiar with. How can I change the list of projects to be in alphabetic order again? Apologies if I misunderstand ...

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?

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

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 MantisServic...