FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Email no longer working

For some reason email notifications are no longer being sent by FogBugz. It was working after our upgrade to 4.0.9 but recenlty it stopped.

I know its probably something on our end but I'm at a loss on how to debug this. Does FogBugz keep a log of errors when connecting/sending mails?

I've tried telnetting to the mail server from the FogBugz machine and that works fine so I know the server name is OK (and other internal applications are sending SMTP mail without problems).

Any suggestions?

Thanks.
David Avraamides Send private email
Wednesday, March 16, 2005
 
 
Hi David-
Did you go through this knowledge base article?
http://www.fogcreek.com/FogBugz/KB/trouble/NotificationProblems.html

If you have gone through that and found nothing, could you try running "SELECT * FROM MailQueue" against your fogbugz database and see if that turns anything up?
Brett Kiefer Send private email
Wednesday, March 16, 2005
 
 
I checked and the maintenance service was installed but not running. I started it but still no mails.

There are 184 rows in the MailQueue table.

I tried to open the heartbeat.asp page and I got a FogBugz exception, which I just submitted to you guys as a bug.
David Avraamides Send private email
Wednesday, March 16, 2005
 
 
David,

I looked at the error you submitted and it is complaining that a column that should be there is not 'ixMailbox' which exists both in the Bug table and in the Mailbox table.  Have you modified your database at all?  Can you check those tables and columns?
Michael H. Pryor Send private email
Wednesday, March 16, 2005
 
 
They are there. But I should note that we have a case-sensitive database and had a previous problem with your install script (that was using 'Drop' in the full-text setup rather than 'drop'). Could that be it?

--

select * from Bug where 1 = 0

ixBug,fOpen,dtOpened,dtResolved,dtClosed,sTitle,ixProject,ixArea,ixPersonOpenedBy,ixPersonAssignedTo,ixStatus,ixPriority,ixFixFor,sVersion,sComputer,hrsOrigEst,hrsCurrEst,hrsElapsed,c,sCustomerEmail,sGPFid,ixMailbox,ixCategory,sBugDispatchoID,ixBugEventLatest,fTrained,fReplied,fForwarded,ixOriginalPrediction,nStatType,sTicket,ixDiscussTopic,dtDue,sReleaseNotes

(0 row(s) affected)

select * from Mailbox where 1 = 0

ixMailbox,sEmail,sFullName,sUser,sPass,sServer,sPort,sURLPrefix,ixProject,ixArea,ixFixFor,ixPriority,ixPersonOpenedBy,ixPersonAssignedTo,nDeleteSPAM,nDeleteInquiries,fDeleted,fAutoSort,fAutoReply,sReplySubject,fDueDate,nDue,nDueTime,sLastMessageDownloaded,sTemplate,sReplyMessage

(0 row(s) affected)
David Avraamides Send private email
Wednesday, March 16, 2005
 
 
I see one problem. The SQL says "WHERE Bug.ixMailBox <> 0" but the correct spelling of it is ixMailbox (lower b).

Looks like there are still a few subtle bugs around case-sensitivity in FogBugz...
David Avraamides Send private email
Wednesday, March 16, 2005
 
 
Got it. I have opened bug against myself to fix this for our next minor release: in the meantime (as you may have found already) you can make the change from ixMailBox to ixMailbox on line 70 of CDailyTask.asp.
Brett Kiefer Send private email
Wednesday, March 16, 2005
 
 
I made the change to CDailyTask.asp and heartbeat.asp now returns '+' as expected. The maintenance service is running, too.

But MailQueue still shows 184 rows and no mail is going out. Do I need to run something to actually force it to catch up on the queued notifications? Or do I just need to wait a while?
David Avraamides Send private email
Wednesday, March 16, 2005
 
 
OK, I understand it now. Each get of heartbeat.asp sends one queued mail message. After hitting the F5 key 184 times, I think we are back in business.

Just a suggestion: this is the second bug I've run into due to case-sensitivity. It would be nice if you guys would build a case-sensitive database and test FogBugz on your end to flush out any more that may be there.

Thanks again,
-Dave
David Avraamides Send private email
Wednesday, March 16, 2005
 
 
Thanks, David. Once more, we apologize for the inconvenience,  and case-sensitive MSSQL databases are on our list of test environments for future major and minor FogBugz releases.
Brett Kiefer Send private email
Wednesday, March 16, 2005
 
 
The above action corrected my database case sensitivity issue.  But I now have an another issue with the same SELECT statement which states that 'The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.'  Is this due to a US-UK date formatting comflict?
Harvey Keefe Send private email
Tuesday, March 22, 2005
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.