07-01-2013 08:29 AM
I have questions regarding Secure Work Space and need your help. My Environment: BES 10.1.1 on Windows Server 2012, Exchange 2010 SP2, Iphone 5/IOS 6.1.4.
The synchronization of Mail/Calendar/Contact data is working in the Secure Work Space, but the push notification does not. I am not able to receive notifications for new emails, when the app is in “background” (closed).
Is it possible to share the Secure Work Space contacts with the device contact app in IOS?
07-01-2013 08:47 AM
I also have the same issue with the Push notifications, everything else is working once you log in.
I think this may be affecting my Android activations too, i can activate the device and the secured workspace, but i canot get my mail profile to connect successfully
07-01-2013 10:44 AM
I'm not seeing notifications either on iOS 6.1.3 / 6.1.4
Based on the information that's on page 31 of the following document, the APNs should be updating the device on a normal basis.
07-01-2013 04:49 PM
the configuration guide is very poor/bad.
there are only 2 information, how to configure this feature.
in configuration guide on site 120 we can find the following lines:
Impersonation of all users on the Microsoft Exchange Server so that BlackBerry Enterprise Service 10 can request and receive notifications from the Microsoft Exchange Server when new or updated items are available in a user's mailbox
For iOS devices,an SSL connection between the Microsoft Exchange Server and BlackBerry Enterprise Service 10. See (Configure an SSL connection between the Microsoft Exchange Server and BlackBerry Enterprise Service 10)
so, i did the following steps in my environment:
on exchange 2010 i set the ms-Exch-EPI-Impersonation
(with besadmin i installed the bes10 and the services are running under this account)
can you try these steps ?
i did all these steps, but with no success. blackberry - please give us a full documentation about this feature.
thank you and good luck
07-02-2013 07:36 AM
thank you all for your answers.
@berryav - I have also configured all the steps you described except the step with ActiveSync (Gatekeeper) configuration, but with or without the “Use Exchange Web Services…” it´s not working.
After tracing the traffic between Exchange and BES I found that after closing the Secure Work Space App (SWS) on the iPhone, the BES is closing the established connection with Exchange on Port 443. When opening the SWS again, a new connection is established and new and changed items are synchronizing as long as the SWS is running in foreground. After closing the connection between Exchange and BES, how can Exchange notify the BES (Work Connect Service?) for changed/new items to sync?
07-02-2013 09:12 PM - edited 07-02-2013 09:13 PM
I am also experiencing this issue.
We are using Exchange 2010, and have configured the impersonation permissions etc. There was a new Work Connect client release today however it did not have any effect.
Looking forward to finding out the answer to this.
07-03-2013 12:56 PM
I have the same problem, Exchange 2010 SP2 and followed the instructions exactly. However the sync of email is either really slow or does not work at all after intial sync on the device.
IPhone 4s updated OS or Ipad 2 updated OS
I have opened a ticket with support but they have been really slow on responses lately.
07-03-2013 01:52 PM
07-03-2013 02:38 PM
I took at look at the logs for the RIM.BUDS.BWCN service (the Work Connect Notification Service), and there are a couple of errors that suggest it's not authenticating correctly, despite the fact that the authentication check in the UDS console succeeds.
In the asg.log file, you'll see a bunch of web service startup info, followed by something like the following:
[localhost-startStop-1] INFO : ASGStartupServlet:44 - ASG starting
[localhost-startStop-1] INFO : ASGStartupServlet:58 - ASGStartUpService found as com.openpeak.asg.ews.service.bb.impl.EwsStartUpSer
[localhost-startStop-1] ERROR: EwsStartUpServiceImpl:117 - Failed to check in to /asg/v1/CheckIn with nodeKey <18 digit number>
[localhost-startStop-1] INFO : ASGStartupServlet:60 - ASG started
[schedulerFactory_Worker-2] INFO : EwsScheduleServiceImpl:141 - staring running polling email registrations from Adam server...
[schedulerFactory_Worker-2] INFO : AuthChallengeProcessor:101 - NTLM authentication scheme selected
[schedulerFactory_Worker-2] INFO : HttpMethodDirector:722 - Failure authenticating with NTLM <any realm>@server.mydomain.com:443
[schedulerFactory_Worker-2] ERROR: EwsEmailNotificationDaoImpl:335 - Connection not established
After this there are repeated blocks of error text indicating that the EWS connection is not established, and it is unable to subscribe for notifications.
If I log the EWS traffic on the CAS server, the only connection attempts I see from the BES10 server are:
POST /ews/exchange.asmx - 443 - 172.27.11.35 ExchangeServicesClient/0.0.0.0 401 0 0 31
POST /ews/exchange.asmx - 443 - 172.27.11.35 ExchangeServicesClient/0.0.0.0 401 1 2148074254 15
POST /ews/exchange.asmx - 443 - 172.27.11.35 ExchangeServicesClient/0.0.0.0 401 1 2148074252 249
So, it looks like they are attempting NTML authentication and failing, so you can't connect to use Push notifications. This despite the fact that the BESAdmin user has impersonation rights and is setup with security permission to the EWS virtual directory, etc.
Do these guys even test their code before they ship it? Jeez.