This project is read-only.


HRESULT: 0x80040108


For your additional information... I installed Attachment Reminder two days ago. It does show a message when any of the key words are in the message, but I also get an error message HRESULT: 0x80040108 when I select SEND on a message that does not have one of the keywords. I am running on Win 7, 64 bit laptop with Office 2007.
Closed Sep 29, 2011 at 5:00 PM by gouravdas
Fixed some of these in 1.0 RC update 1


melvynadam wrote Jun 22, 2011 at 10:25 AM

I have the same issue.
I'm running v1.0b and the reminder works (use of keywords leads to a prompt) but I get HRESULT: 0x80040108 for every other email.
In addition, whenever I close Outlook and relaunch it I am told that I need to create the first rule for OAR.

This is from the log file:


16/05/2011 13:28:22

Message: Exception from HRESULT: 0x80040108
Stack: at Microsoft.Office.Interop.Outlook._MailItem.get_ConversationIndex()

at OutlookAttachmentReminder.OutlookAttachmentReminderAddin.Application_ItemSend(Object Item, Boolean& cancel)*************************

melvynadam wrote Jun 22, 2011 at 10:28 AM

Should have said that I'm running Win7 Enterprise 64-bit (SP1) with Office 2007 (SP2).

allanwalters wrote Sep 1, 2011 at 10:58 AM

Yes, I am getting the same 'Exception from HRESULT: 0x80040108' error message intermittently too (with the identical text appearing in the OAR log file as reported by melvynadam on 22nd June). I am running Windows 7 64-bit and 32-bit Office 2010 with OAR version Beta.

Is there a fix planned for this problem?

gouravdas wrote Sep 1, 2011 at 1:50 PM

We will be starting Full time development on this in couple of months from now. So all fixes are postponed till then.

gouravdas wrote Sep 29, 2011 at 10:02 AM

Hello melvynadam, the prompt you get when outlook is launched is just a reminder that you can add rules. I have changes it to a more intuitive message.

allanwalters, could you try There are many fixes for 0x80040108 in that version.

BTW, I am making another change that is to cover another scenario that causes 0x80040108. It should be out shortly.

wrote Sep 29, 2011 at 5:00 PM

wrote Feb 14, 2013 at 2:02 AM

wrote May 16, 2013 at 8:22 AM