Question

Hi,

I recently upgraded from 8.0.32 to 8.1.1, and it seemed that all went flawlessly. I tested email, etc. and it seemed to work. Now I have users coming to me saying that email is not working, and I need to figure out how to find and fix the problem. Any thoughts?

On step 11 of the diagnostics, I get the following:

The maintenance url can be reached successfully!

HOWEVER, the maintenance URL should return simply a +, a -, or a # but in this install it is returning:

! The Fog Creek Maintenance Service has reported an error. (-2147024809) System: The parameter 'address' cannot be an empty string. Parameter name: address

System.ArgumentException: The parameter 'address' cannot be an empty string. Parameter name: address at System.Net.Mail.MailAddress..ctor(String address, String displayName, Encoding displayNameEncoding) at Wasabi.Runtime.Mail.MailMessage.SetItems(MailAddressCollection targ, IEnumerable src, MailAddressCollection overflow) in c:\src\Wasabi\Wasabi.Runtime\Mail\MailMessage.cs:line 369 at Wasabi.Runtime.Mail.MailMessage.ParseEmail(Stream stream, Nullable1 optfPreferHTML, Nullable1 optfDelayNonInlineAttachments) in c:\src\Wasabi\Wasabi.Runtime\Mail\MailMessage.cs:line 323 at FogCreek.FogBugz.CBugEvent.ParseEmail() in c:\src\FogBugz\distribution\src-Website\CBugEvent.was:line 490 at FogCreek.FogBugz.CBugEvent.CreateHTMLVersion() in c:\src\FogBugz\distribution\src-Website\CBugEvent.was:line 783 at FogCreek.FogBugz.CBugEvent.InternalLoad(Int32 ixBugEventLoad) in c:\src\FogBugz\distribution\src-Website\CBugEvent.was:line 310 at FogCreek.FogBugz.CBugEvent.Load(Int32 ixBugEventLoad) in c:\src\FogBugz\distribution\src-Website\CBugEvent.was:line 237 at FogCreek.FogBugz.CHeartbeatTask.BackFillSummary() in c:\src\FogBugz\distribution\src-Website\CHeartbeatTask.was:line 404 at FogCreek.FogBugz.CHeartbeatTask.PerformTask(Function`3 fxErr, Int32 nTimeout) in c:\src\FogBugz\distribution\src-Website\CHeartbeatTask.was:line 114 at FogCreek.FogBugz._Global.SingleHeartbeatFogBugz(Int32 cMaxBayesianRequests, Int32 cMaxMailMessages, Int32 nEmailTimeout) in c:\src\FogBugz\distribution\src-Website\singleHeartbeat.was:line 112 at FogCreek.FogBugz._Global.SingleHeartbeatPlatform(Int32 cMaxBayesianRequests, Int32 cMaxMailMessages, Int32 nEmailTimeout) in c:\src\FogBugz\distribution\src-Website\singleHeartbeat.was:line 45 at FogCreek.FogBugz.__Global.StartHeartbeat() in c:\src\FogBugz\distribution\src-Website\heartbeat.was:line 70

Answer 1

There's something "bad" in your database, but we aren't sure where it is. I'll provide some instructions here on how to fix it, but also feel free to email support for assistance.

First, a little background. We made a change to how we store the little text summaries in 8.1, so after upgrade we run a task that goes back and fixes them all. There's a bad bug event in your database that causes a crash when trying to load an old bug.

To stop the backfill, you'll need to edit the database. (Mind the single quotes, all these values are actually strings in the db.)

select sValue from Setting where sKey = 'ixLatestTextSummaryBackfill';

This will return some number, which is as far as the backfill has gotten. Now we can tell FogBugz to stop. Replace "that number" in the below SQL as appropriate.

update Setting set sValue = '[that number]' where sKey = 'ixLatestTextSummaryBackfillStop';

If the bug that caused problems is an old one, and you don't care too much about the summaries of older bugs, you can probably leave off now.

The backfill works a 100 bugs at a time, so the bad bug will be within 100 less than the value from above. To find the bad one, start at that bug and go back one by one. Eventually, FogBugz will crash again trying to display the bug with an error similar to the one above. At this point, you'll probably need to email support anyway to send us the contents of the broken email.

I apologize for the inconvenience, and of course support will be able to walk you through the above procedure if you have any questions.