Open page not working

[IanG]

Hi
We are using fortress 1.1.2 and are currently having problems getting the open page for one project to display. Every time we try to view the open items page for this one project we get the following error:

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


Looking in the sgvault.log file with debug swiched on we seem to be getting the folowing messages when anyone trys to view the open items page:

----7/1/2008 9:52:43 AM --192.168.97.133(192.168.97.133)--SSL Disabled AuthTokenHash matched, but couldn't get the userid

and

2008-07-01 09:52:35.730 desktop11.paragon.pgn (192.168.97.133)-admin : Server error 500 Object reference not set to an instance of an object. at Mantis.SortByMilestoneControl.GetItemListsByMilestone() 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)


in the fortress log.

We can do a query to return the same results as the open items page would show and it works for other projects, any ideas about what could be wrong?

Rgrds Ian

[Beth]

Is this the same for all users and all machines, or either just select users or machines?

What happens if you try to open that page right on the Vault server using localhost for the server name part of the URL?

[IanG]

Yes it's the same for all users and I get the same error if I connect to fortress using localhost on the server its self.
Ian

[Beth]

Do you know if any milestones were deleted?

Can you send me an email to support at sourcegear.com (attn: Beth) with a link to this forum thread? I may have something for you to run against your database.

[IanG]

With help from SG I have sorted this problem out and I thought I would document the solution here in case anybody else has a similar issue.
We discovered that there were a couple of open items that were included in inactive milestones, once we changed thier state to closed everything started working correctly again.

I would be nice if this didn't cause a problem, or maybe there could be some way to prevent this situation happening.

Rgrds
Ian.

[Beth]

I'll get this logged as a request. Thanks.