ColdFusion 10 and Exchange 2010 using cfexchangecontact

Report · Sep 22, 2012

We recently upgraded from CF9 to CF10 so that we can support Exchange 2010 contacts and calendar events. However, I am having difficulties with the CFEXCHANGECONTACT tag. I am able to successfully connect to the Exchange service but it doesn't appear to understand the CF. I've search the Adobe website but there is little to no information regarding this issue.

I am receiving the following error messages when I am using the different ACTION attribute values:

CODE: <cfexchangecontact action="get" connection="myExchangeConnection" name="exchangeContact">

MESSAGE: "The request failed. Could not read value from START_ELEMENT.Could not find CHARACTERS"

CODE: <cfexchangecontact action="create" connection="myExchangeConnection" name="exchangeContact">

MESSAGE: "Error occurred during an operation is executed in the exchange server. Error Code : ErrorInvalidArgument"

CODE: <cfexchangecontact action="modify" connection="myExchangeConnection" name="exchangeContact">

MESSAGE: "Error occurred during an operation is executed in the exchange server. UID is malformed"

The error messages are so generic that I am unable to determine where the error is occuring. I can't tell if it's an exchange issue or an issue with CF10. If anyone has able to get CF10 to successfully update information in Exchange 2010 I would greatly appreciate your input.

Thank you in advance for your assistance!

Bettina

Report · Sep 24, 2012

I've only used the Exchange connectivity stuff superficially. I'll say that upfront.

Just to confirm a coupla things:

* can we see your <cfexchanegconnection> code? You've got the SERVERVERSION set correctly, yes? I presume you'd not get as far as you did if not, but best to confirm

* can you perform other actions with Exchange OK, like reading calendars, email, etc?

* are there any logs on the Exchange end of things that might be indicating a bad connection / request or something?

* anything else in any of the CF logs?

--

Adam

Report · Mar 05, 2013

We were finally able to get this working. The issue was that we needed to add the server version attribute to the CFEXCHANGECONNECTION tag. That fixed it.