Question

We have several cases that are very old that always show up on the Escalation Report. When we go to these cases in FogBugz to close them we get the following error. Can anyone tell us what is going on here?

FogBugz Internal Error

An internal error occurred in FogBugz. If you are unsure of how to fix this error, and you have made no changes to the source code of FogBugz, please report this error to Fog Creek Software by clicking "Submit."

Error:  Invalid value for ixBugEventViewed Parameter name: ixBugEventViewed
Stack Trace:    Hide Stack Trace
System.ArgumentException: Invalid value for ixBugEventViewed
Parameter name: ixBugEventViewed
  at FogCreek.FogBugz.CBug.RecordView (Int32 ixPerson, Nullable`1 dtView, Nullable`1 ixBugEventViewed) [0x00000] 
  at FogCreek.FogBugz.CBug.RecordView () [0x00000] 
  at (wrapper remoting-invoke-with-check) FogCreek.FogBugz.CBug:RecordView ()
  at FogCreek.FogBugz.__Global.RenderEntireBug (FogCreek.FogBugz.CBug c, FogCreek.FogBugz.CPerson cp, System.String sCommand, Boolean fMultipleBugs, System.String sBugs, System.String[] rgBugs, Int32 ixBugEventLatest, Int32 ixDiscussTopic, Int32 ixScreenshot, Boolean bCanWriteAllBugs, Boolean fShowLastEvent, Int32 ixPersonLastOwner, System.String sDefaultText, Wasabi.Runtime.Function`1 fxHTMLPluginTop, Wasabi.Runtime.Function`1 fxHTMLPluginLeft, Wasabi.Runtime.Function`1 fxHTMLPluginLink, Int32 ixBugEvent) [0x00000] 
  at FogCreek.FogBugz.__Global.EditBugPage (System.String sCommand, Int32 ixBugEventLatest, Int32 ixDiscussTopic, Boolean fShowLastEvent, Boolean fNewBug, Int32 ixScreenshot) [0x00000] 
  at FogCreek.FogBugz.__Global.RawpgEditBug () [0x00000] 
  at FogCreek.FogBugz.__Global.pgEditBug () [0x00000] 
  at FogCreek.FogBugz.__Global.RunPg () [0x00000] 
  at Wasabi.Runtime.Web.Response.PictureOf (Wasabi.Runtime.Sub sub) [0x00000] 
  at (wrapper remoting-invoke-with-check) Wasabi.Runtime.Web.Response:PictureOf (Wasabi.Runtime.Functional/Sub)
  at FogCreek.FogBugz.__Global.RawRunFogBugz () [0x00000] 
  at FogCreek.FogBugz.__Global.RunFogBugz () [0x00000] 
  at FogCreek.FogBugz.__Global.StartDefault () [0x00000] 
  at FogCreek.FogBugz.HttpHandler.ProcessRequest (System.Web.HttpContext context) [0x00000] 
Browser:     Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.18.1 (KHTML, like Gecko) Version/5.0.2 Safari/533.18.5
Source:  FogBugz
OS Version:  Unix 2.6.31.302
Database:    MySQL
QueryString:     ?pre=preMultiSearch&pg=pgList&pgBack=pgSearch&search=2&searchFor=1672
URL:     /default.asp
Content Length: 
Local Addr:  [redacted]
Remote Addr:     [redacted]
Time:    11/11/2010 3:58:01 PM
Site:    [redacted]

Answer 1

This is happening because the escalation report only queries the Bug table. If you have a record that slipped into the Bug table that doesn't have any matching BugEvents, then the escalation report sees it, but it's not a valid FogBugz case.

Usually, these are old cases that failed to get created. We don't have any current issue with these kinds of failures, so your choices are to delete the rows from the Bug table or ignore these cases.

I'm filing a bug to make the escalation report do an INNER JOIN on the BugEvent table.