SourceGear Support

The query I tried to edit was one which I used regularly in the previous Fortress version. It searched for all items with open/pending status from one particular assignee. No specific projects or other criteria were present.

It worked until I upgraded to version 2.00.

Item tracking fields were not modified after the upgrade. Apart from I had to rename the 'Custom1' and 'Custom2' fields as per my other forum post.

I have now deleted the queries as a workaround.

When I try to edit a saved query, the following error appears in the Fortress log: 2009-08-31 17:03:10.390 10.0.0.196 (10.0.0.196)-MyUserName: Server error 500 'SavedQueryList1' has a SelectedValue which is invalid because it does not exist in the list of items. Parameter name: value at System.Web.U...

Yes, we had data in those fields and the data has not been lost.

Notification e-mail snippets showing the issue:

Pre-upgrade:

Requestor:
Validator / Reminder Week(s):

Post upgrade:

Custom1:
Custom2:

It was an in-place upgrade from 1.1.4. Server is Win 2003 Std SP2 x86

.NET 3.5 SP1 installed and rebooted. The kicking issue is still present on http://localhost/Fortress. I am kicked after a half dozen random clicks around Fortress.

Using http://localhost/Fortress on the server demonstrates the kicking issue. I have tried the following settings for the web.config parameter with no success: 1024 2048 8192 32768 65536 After each time I have changed the setting I have recycled the Vault app pool in IIS. I will send you the full lo...

The errors in the fortress.log and the constant kicking from Fortress may not be related. There are much less errors in the fortress.log than the amount of times everyone is kicked.

By the way the kicking occurs regardless if a proxy server is used.

Another type of error 500 from fortress.log: 2009-08-14 11:58:30.226 MyProxyServer (10.0.0.1)-MyUserName : Server error 500 Object reference not set to an instance of an object. at Mantis.QueryUpControl.Repeater1_ItemCreated(Object sender, RepeaterItemEventArgs e) at System.Web.UI.WebControls.Repeat...

This happens to all users on multiple computers. Behaviour is seen in IE 7 and 8. Please note this also happens when running the web client on the Fortress server. This is when logged in to Fortress as any user including Admin. Here is an example of the Error 500's from Fortress.log: 2009-08-13 18:0...

The names of item tracking fields 'Custom1' and 'Custom2' were lost after upgrading to 2.0

I had to rename them to their previous settings after upgrade.

Steps I can do to reproduce: 1) Close all browsers (IE 8) 2) Launch Fortress 3) Enter any item number into the search box at the top right and click Search 4) I get kicked to Fortress login screen The 'Remember login on this machine' setting is always forgotten. The above happens frequently and also...

This issue is reproducable for me when moving between items/views and is not tied into any idle timeouts or similar.

I have changed the setting to 65536 and will monitor. Setting to 32768 made no difference.

In version 2.0 changing an item's Project causes issues. Steps: 1) Change the Project of an item and click save 2) Click to Modify the item 3) The Category dropdown shows the categories for the previously-assigned Project, not the currently assigned Project I have to click Home or similar and then r...

I am seeing intermittent errors in Fortress.log file. This is coinciding with users being kicked from Fortress. Examples below: 2009-08-11 23:34:49.448 MyServer.MyDomain.local (10.0.0.1)-MyUserName : Server error 500 Invalid viewstate. Client IP: 10.0.0.1 Port: 55855 User-Agent: Mozilla/4.0 (compati...