Question

The notification text:

10/16/2010 2:12 AM (GMT-04:00): System.InvalidCastException: Specified cast is not valid.

Server stack trace: at FogCreek.FogBugz.CaseHistory.BugHistoryEntry..ctor(CPluginApi api, DataRow rsBugEvent, RecordType nRecordType) at FogCreek.FogBugz.CaseHistory.Estimator.GenerateEstimates(Int32 ixBugMinExclusive, Int32 ixBugMaxInclusive) at FogCreek.FogBugz.CaseHistory.CaseHistory.HeartbeatTask() at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at FogCreek.FogBugz.Plugins.Interfaces.IPluginHeartbeatTask.HeartbeatTask() at FogCreek.FogBugz.__Global.SingleHeartbeatPlugins() in c:\src\FogBugz\distribution\src-Website\singleHeartbeat.was:line 235

Case FC1958946

Answer 1

We're aware of this problem, and it should only affect FogBugz 8.0 customers; we're working on a fix to prevent this error from showing up in the future.

It can happen on two occasions: The initial install/upgrade to FogBugz 8, and if you click the "configure" button for the Case History plugin. In both cases, the error message is completely benign and can be ignored with no ill effects.

Naturally, the workaround is to not try to configure the Cast History plugin. There is no configuration that can be performed by the user and that page will only contain a brief statistic about case event indexing that the Reporting plugin needs.

If you have questions about this error, please don't hesitate to contact us!