Exchange Web Services (EWS) support

PSCArmstrSM · #1 (**permalink**) 05-12-2010, 06:38 PM

BES 5.0.1 is theorized to have EWS support to replace CDO operation for Calendaring and Free/Busy. The limited documentation I've found on the subject state it is compatible with Exchange 2007 and 2010.

Once I upgraded my BES from 4.1.6mr6 to 5.0.1, I started testing it. What I found was that on Windows 2003 R2 x32, it worked fine. One of my BES servers however, was Windows 2003 R2 x64, and it did NOT work. The DART team didn't draw this correlation until I rebuilt my x32 server on new HW, and went with x64. Once we did this, EWS no longer functioned. Here is what we get in the CALH logs now:

Code:

[40000] (05/12 17:20:43.528):{0x494} {User.Name@domain.com} WSRequestParams::Process - CAL_MEETING_CANCEL_FROM_MB
[30580] (05/12 17:20:55.918):{0x494} {User.Name@domain.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #1
[30580] (05/12 17:20:55.918):{0x494} {User.Name@domain.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #2
[30580] (05/12 17:20:55.918):{0x494} {User.Name@domain.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #3
[30580] (05/12 17:20:55.918):{0x494} {User.Name@domain.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #4
[30580] (05/12 17:20:55.918):{0x494} {User.Name@domain.com} WSRequestParams::MeetingRequestWsToCiCAL - EWS Error: Meeting message has not been processed, get attempt #5
[30602] (05/12 17:20:55.918):{0x494} {User.Name@domain.com} WSRequestParams::MeetingRequestWsToCiCAL - Cannot find associated meeting in calendar

I just got off the line with a DART support rep, after working with him for over an hour. He said that he's been successful with EWS on a Windows 2003 R2 x64 to Exchange 2010, but hasn't attempted to 2007.

For clarification, we have only defined a single static agent as EWS enabled for testing.

Anyone tested EWS for Exchange 2007?

hdawg · #2 (**permalink**) 05-12-2010, 07:24 PM

I'll admit it I haven't done much of anything with EWS & BES, however it should work happily with Exchange 2007 SP1 or >

Sounds like some possible dll unhappiness ... I wish I could offer some more insight but I can't; sorry.

SteveE · #3 (**permalink**) 05-19-2010, 11:44 AM

I can say I'm seeing the same issue on a 2010 mailbox with 5.0.1, I plan on opening a support ticket with RIM today.

hdawg · #4 (**permalink**) 05-21-2010, 09:24 PM

any traction on this guys?

SteveE · #5 (**permalink**) 05-24-2010, 04:37 PM

No news yet, I submitted all my logs to RIM Support and they state a 2 busines day turnaround after that - even post-escalation with Advantage support.

In addition to event logs, magt/calh/sync logs, they had me perform some test scenarios and documenting the event uid of calendar items (retrieved by opening a calendar item, holding ALT and typing "view".

I'm seeing those warnings on my test mailbox, which is what we're troubleshooting now. They persisted through a wipe/re-add. It may be mailbox corruption, too soon to say.

guzowskif · #6 (**permalink**) 05-26-2010, 02:04 PM

Had a tough time with this as well. I am using EWS with BES 5.01. MR1 on WIN2K3 x64.

Documentation shows 2010 PS commnads. They were missing the impersonation commands for EX2007

RIM Support -----

Here are the commands to enable BlackBerry Enterprise Server version 5.0 SP1 to use Microsoft Exchange Web Services:

Microsoft Exchange Server 2007:
On the Exchange server while logged in as Domain Admin run the following power shell commands to set the correct impersonation rights.

get-mailboxserver "<ex2007_server_name>" | add-adpermission -user "<BESAdmin>" -accessrights ExtendedRight -extendedrights ms-Exch-EPI-May-Impersonate, ms-Exch-EPI-Impersonation

The second PowerShell command required the Distingushed name of the CAS server. the following command will return the name and DN of each CAS server.

get-clientaccessserver | select name,distinguishedname | fl

add-adpermission -Identity "<CAS distingueshed name>" -User <user> -ExtendedRights ms-Exch-EPI-Impersonation

This sets the impersonation rights on the specific CAS server we are using. Please note if CAS is configured for a round robin load balancing then this command needs to be run for each CAS server.

Follow Us On

Forum Sponsors

Google Advertisements