HTMLBody null and throws not implemented exception

Add-in Express™ Support Service
That's what is more important than anything else

HTMLBody null and throws not implemented exception
 
Jeff Noble




Posts: 120
 Joined: 2011-09-07
Hi Guys,

I was working on a bug and I was wondering if you have ever come across this. I have a machine that is set to Korean language. Windows 8, 32 bit running Outlook 2016. I was not able to read the HTMLBody property of the MailItem. I installed Outlook Spy on the machine and opened a new email. If I click the CurrentItem button in OutlookSpy, and select the HTMLBody property it's null. Not sure why, but that explains why I can't access it in code. Body is empty as well. Not sure how I can proceed.

[img]http://screencast.com/t/qMx3julhi[/img]

Any suggestions?

Thanks,
Jeff
Posted 13 Nov, 2015 10:45:16 Top
Dmitry Kostochko


Add-in Express team


Posts: 2875
 Joined: 2004-04-05
Hi Jeff,

I would suggest that you save the mail item before accessing the Body and HTMLBody properties. Does this help?
Posted 13 Nov, 2015 10:53:46 Top
Jeff Noble




Posts: 120
 Joined: 2011-09-07
Just tried, still null in OUtlookSpy and throws same exception in code. :(
Posted 13 Nov, 2015 11:18:35 Top
Dmitry Kostochko


Add-in Express team


Posts: 2875
 Joined: 2004-04-05
Jeff,

If this happens just on one machine, I would try to repair (or even reinstall) Microsoft Office.

BTW, do you see any other 3rd party add-ins installed there?
Posted 13 Nov, 2015 11:26:10 Top
Jeff Noble




Posts: 120
 Joined: 2011-09-07
I don't see anything 3rd party on it. I can ask them to repro the issue on another machine to make sure. Good idea.

-Jeff
Posted 13 Nov, 2015 11:38:21 Top
Andrei Smolin


Add-in Express team


Posts: 18819
 Joined: 2006-05-11
Hello Jeff,

Does the issue persists?


Andrei Smolin
Add-in Express Team Leader
Posted 17 Nov, 2015 07:05:07 Top
Jeff Noble




Posts: 120
 Joined: 2011-09-07
Sorry about the delay, I was waiting for an answer from our QA team. Here is their reply:

"We got same observation after checking on three machines: one is KOwin8.1x86, others are KOWin10x86. this issue only repro on Outlook2016, it works fine on KO Outlook 2013."


So it is still happening. Not sure what I can do about it though.... I would hate to discontinue support for our 2016 clients in Korean....

Any other ideas?
-Jeff
Posted 19 Nov, 2015 14:36:58 Top
Andrei Smolin


Add-in Express team


Posts: 18819
 Joined: 2006-05-11
Jeff,

Please send me such an email following these instructions: create an email (email #1); get an email (email #2) on which the issue is replicated and attach it to email #1; send email #1 to me; find the support email address in {Add-in Express installation folder}\readme.txt; make sure email #1 contains a link to this topic.


Andrei Smolin
Add-in Express Team Leader
Posted 20 Nov, 2015 03:16:54 Top
Daniel Ranft




Posts: 14
 Joined: 2012-09-13
Hi,

i would appreciate, if you could report the results of this case to the public, as i also came across such an error. Unfortunately, i'm not able to deliver you more data as i'm lacking them too.

Many Thanks
- Daniel
Posted 24 Nov, 2015 08:58:02 Top
Jeff Noble




Posts: 120
 Joined: 2011-09-07
Sorry for the delay, I was on vacation. I'll send you the email Andrei if the I still have access to that Korean machine.
-Jeff

After checking, I no longer have access to that machine. I am trying to get it back, will advise.
Posted 24 Nov, 2015 09:03:13 Top