tracker issue : CF-4203610

select a category, or use search below
(searches all categories and all time range)

Error when using cfexchangemail in CF2018

| View in Tracker

Status/Resolution/Reason: To Fix//NeedMoreInfo

Reporter/Name(from Bugbase): Paul Turner / ()

Created: 12/02/2018

Components: CFExchange

Versions: 2016,2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 2018.0.01.311402 /

Priority/Frequency: Normal / All users will encounter

Locale/System: / Win 2016

Vote Count: 1

Problem Description: When utilizing the (cfexchangemail) tag in CF2018, the error "Could not get messages.
The property meeting:AssociatedCalendarItemId is not valid for this object type. The Current ExchangeVersion is Exchange2010."

However, running the same exact page code in CF2016 completes without issue.

Steps to Reproduce: To Reproduce this error, the index.cfm page file in the attached zip file can be run. 

***Note: Due to obvious security concerns, the Exchange User and Password used to test this issue have been removed. In order test the values for the following variables will need to be substituted for valid credentials (emailAddressForOffice365User) and (passwordForOffice365User) within the index.cfm script 

Actual Result:
See attached PDF: "cfexchangemail - Tag Failure CF2018.pdf"

Expected Result:
See attached PDF: "cfexchangemail - Tag Success CF2016.pdf"

Any Workarounds:



Paul, We have not certified CF with office 365 service. Is there a way you can find out the exchange version of the exchange service you are using? The supported versions are: 2010_SP2, 2010_SP1, 2010 and 2013. 2016 will also be supported with a soon to be released update.   
Comment by Piyush K.
30209 | February 08, 2019 09:35:08 AM GMT
Hi Piyush, Hmm, it looks like the Exchange version is in the error message?: "Could not get messages. The property meeting:AssociatedCalendarItemId is not valid for this object type. The Current ExchangeVersion is Exchange2010." Or the error message defaults to say "Exchange2010" if it's unable to determine the version? Thanks!, -Aaron
Comment by Aaron N.
30211 | February 08, 2019 02:21:58 PM GMT
Hello Piyush, Thank you for your reply to this bug ticket. In this case, I have been able to identify that the Exchange version number being used for our client's services is (15.20.1404.011), which incidentally is exclusive to the Office365 Exchange server. With that said, while I can appreciate that CF is not certified for use with Office365 there are a couple of points of contention that we have: First, our client is not encountering this issue within ColdFusion 2016 and earlier, which may be a happy coincidence since they have been utilizing the (cfexchangemail) tag without issue prior to CF2018. Although, we understand that CF2018 is not CF2016 and is not a particularly strong argument, we still find what appears to be a loss of functionality/compatibility with the newer version concerning. Second, while we understand that changes to the operational base of these tags may have very-well changed quite a bit between CF2016 and CF2018 releases, the other point of contention is that our client can utilize the (cfexchangecalendar) tag within CF2018 without issue, wherein we find it odd that the (cfexchangecalendar) tag works without issue while the (cfexchangemail) tag experiences what appears to be an issue with some facet of CF 2018's stricter data type preservation. Third, I would also note that none of the emails that would have been pulled, by the (cfexchangemail) tag in the example we used, included any emails with meeting invitations or any other meeting or calendar associated objects. Thank you, Paul T.
Comment by Paul T.
30216 | February 10, 2019 02:36:45 AM GMT
Paul, There are some new changes and checks to support the new Exchange 2010 service packs and the newer exchange versions 2013 and 2016. These changes are also included in the recently released update 8 for CF2016. So, if cfexchangemail is working for your client with CF2016, then I guess the server is on an older update. Anyway, can you pls. place the attached jar in the <cf_root>/cfusion/lib/updates/ dir of your CF2018 server, restart it and check the output with the test code. 
Comment by Piyush K.
30242 | February 13, 2019 01:01:24 PM GMT
Piyush, Thank you for your update to this bug tracker. In this case, I have been able to install the patch you provided per your instructions and have been able to test the tag using the test code we had submitted previously. Currently, the patch applied appears to have corrected the errors reported to us by our client's via our copy of the testing script. However, we have contacted our client's so that they can conduct additional testing via their more specialized pages as needed. Once we have confirmation of their results, we will be happy to report back with the findings from their field testing. Thank you again, Paul T.
Comment by Paul T.
30243 | February 13, 2019 02:37:49 PM GMT
Thanks Paul. Can you also confirm the update level of your client's CF 2016 server. If it it not patched with the recently released update 8, will it be possible to you to check if the problem crops up when you apply the update, and if using the patch shared here, fixes that?
Comment by Piyush K.
30246 | February 14, 2019 07:36:29 AM GMT
Hi Paul, Can you pls. confirm if it would be possible for you to check if the patch works for CF 2016 on the latest update.
Comment by Piyush K.
30389 | February 25, 2019 08:10:20 AM GMT