Search found 123 matches
- Wed Sep 02, 2009 2:07 am
- Forum: Support (Fortress)
- Topic: Error 500 When Edit Saved Query
- Replies: 6
- Views: 8141
Re: Error 500 When Edit Saved Query
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.
- Tue Sep 01, 2009 9:31 am
- Forum: Support (Fortress)
- Topic: Error 500 When Edit Saved Query
- Replies: 6
- Views: 8141
Re: Error 500 When Edit Saved Query
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.
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.
- Mon Aug 31, 2009 10:09 am
- Forum: Support (Fortress)
- Topic: Error 500 When Edit Saved Query
- Replies: 6
- Views: 8141
Error 500 When Edit Saved Query
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...
- Tue Aug 18, 2009 2:41 am
- Forum: Support (Fortress)
- Topic: Custom Field names missing after 2.0 upgrade
- Replies: 6
- Views: 7405
Re: Custom Field names missing after 2.0 upgrade
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:
Notification e-mail snippets showing the issue:
Pre-upgrade:
Requestor:
Validator / Reminder Week(s):
Post upgrade:
Custom1:
Custom2:
- Mon Aug 17, 2009 2:24 am
- Forum: Support (Fortress)
- Topic: Custom Field names missing after 2.0 upgrade
- Replies: 6
- Views: 7405
Re: Custom Field names missing after 2.0 upgrade
It was an in-place upgrade from 1.1.4. Server is Win 2003 Std SP2 x86
- Fri Aug 14, 2009 9:41 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
.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.
- Fri Aug 14, 2009 9:08 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
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...
- Fri Aug 14, 2009 6:57 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
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.
By the way the kicking occurs regardless if a proxy server is used.
- Fri Aug 14, 2009 6:51 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
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...
- Fri Aug 14, 2009 6:50 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
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...
- Thu Aug 13, 2009 2:38 am
- Forum: Support (Fortress)
- Topic: Custom Field names missing after 2.0 upgrade
- Replies: 6
- Views: 7405
Custom Field names missing after 2.0 upgrade
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.
I had to rename them to their previous settings after upgrade.
- Thu Aug 13, 2009 2:30 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
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...
- Wed Aug 12, 2009 10:18 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Re: Invalid Viewstate & Error 500 in version 2.0
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.
I have changed the setting to 65536 and will monitor. Setting to 32768 made no difference.
- Wed Aug 12, 2009 7:07 am
- Forum: Support (Fortress)
- Topic: Categories Not Updating In Modify Item in version 2.00
- Replies: 1
- Views: 3088
Categories Not Updating In Modify Item in version 2.00
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...
- Wed Aug 12, 2009 4:26 am
- Forum: Support (Fortress)
- Topic: Invalid Viewstate & Error 500 in version 2.0
- Replies: 11
- Views: 22744
Invalid Viewstate & Error 500 in version 2.0
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...