Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
Contributor
Posts: 30
Registered: ‎10-12-2010
My Device: Not Specified

Communication Logs: action.eassync failure

Has anyone come across this in their communication logs?  There's no information on it on the BlackBerry support site, and I've never run across it before.

 

action.eassync      failure

 

I've got a single user who I can't push the EAS profile to. iPhone 5 CDMA/LTE.  All other profiles get pushed to the user properly. 

 

Running latest version of UDS.

Contributor
Posts: 22
Registered: ‎10-03-2011
My Device: 8520
My Carrier: Claro

Re: Communication Logs: action.eassync failure

Same problem, any idea?

 

Anybody?

 

 

BlackBerry Employee
Posts: 750
Registered: ‎05-15-2008
My Device: Z10
My Carrier: Rogers

Re: Communication Logs: action.eassync failure

What version is the iphone at?

Contributor
Posts: 22
Registered: ‎10-03-2011
My Device: 8520
My Carrier: Claro

Re: Communication Logs: action.eassync failure

I had the same issue with android 2.3

Contributor
Posts: 30
Registered: ‎10-12-2010
My Device: Not Specified

Re: Communication Logs: action.eassync failure

In my situation it was 6.0.1

New Contributor
Posts: 2
Registered: ‎03-05-2013
My Device: Bold 9900
My Carrier: Rogers

Re: Communication Logs: action.eassync failure

[ Edited ]

same error here - i phone 4S

OS if 6.1 - carrier is Sprint.  UDS is at the latest level and we haven't seen this on the ipads using the same OS

New Contributor
Posts: 2
Registered: ‎03-22-2013
My Device: Blackberry 9700
My Carrier: Proximus

Re: Communication Logs: action.eassync failure

we have 100% the same problem, iphone 4S, OS 6.1

maart 22, 2013 1:33:58 PM (CET): command.application success
maart 22, 2013 1:33:57 PM (CET): command.deviceinfo success
maart 22, 2013 1:33:50 PM (CET): action.poke success
maart 22, 2013 1:33:50 PM (CET): command.application request
maart 22, 2013 1:33:50 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 1:33:50 PM (CET): command.deviceinfo request
maart 22, 2013 1:18:46 PM (CET): command.application success
maart 22, 2013 1:18:45 PM (CET): command.deviceinfo success
maart 22, 2013 1:18:38 PM (CET): action.poke success
maart 22, 2013 1:18:38 PM (CET): command.application request
maart 22, 2013 1:18:38 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 1:18:38 PM (CET): command.deviceinfo request
maart 22, 2013 1:03:35 PM (CET): action.poke success
maart 22, 2013 1:03:35 PM (CET): command.application request
maart 22, 2013 1:03:35 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 1:03:35 PM (CET): command.deviceinfo request
maart 22, 2013 1:03:35 PM (CET): action.breach success
maart 22, 2013 12:50:19 PM (CET): action.eassync failure
maart 22, 2013 12:48:28 PM (CET): command.application success
maart 22, 2013 12:48:26 PM (CET): command.deviceinfo success
maart 22, 2013 12:48:26 PM (CET): action.eassync request
maart 22, 2013 12:48:25 PM (CET): action.poke success
maart 22, 2013 12:48:23 PM (CET): action.poke success
maart 22, 2013 12:48:20 PM (CET): action.poke success
maart 22, 2013 12:48:20 PM (CET): command.application request
maart 22, 2013 12:48:20 PM (CET): command.deviceinfo_bdmi request
maart 22, 2013 12:48:20 PM (CET): command.deviceinfo request
New Contributor
Posts: 2
Registered: ‎03-05-2013
My Device: Bold 9900
My Carrier: Rogers

Re: Communication Logs: action.eassync failure

Exact same for all Non-BB device users oin our UDS however all are receiving their email so I'm not sure what to make of it.

April 5, 2013 10:49:11 AM (EDT):command.applicationsuccess
April 5, 2013 10:48:52 AM (EDT):action.pokesuccess
April 5, 2013 10:48:52 AM (EDT):command.applicationrequest
April 5, 2013 10:46:18 AM (EDT):command.deviceinfosuccess
April 5, 2013 10:46:12 AM (EDT):action.pokesuccess
April 5, 2013 10:46:12 AM (EDT):command.deviceinfo_bdmirequest
April 5, 2013 10:46:12 AM (EDT):command.deviceinforequest
April 5, 2013 10:40:13 AM (EDT):action.eassyncfailure
April 5, 2013 10:38:48 AM (EDT):command.applicationsuccess
April 5, 2013 10:37:51 AM (EDT):action.pokesuccess
April 5, 2013 10:37:51 AM (EDT):command.applicationrequest
April 5, 2013 10:36:08 AM (EDT):command.deviceinfosuccess
April 5, 2013 10:36:00 AM (EDT):action.pokesuccess
April 5, 2013 10:36:00 AM (EDT):command.deviceinfo_bdmirequest
April 5, 2013 10:36:00 AM (EDT):command.deviceinforequest
April 5, 2013 10:27:49 AM (EDT):command.applicationsuccess
April 5, 2013 10:27:19 AM (EDT):action.pokesuccess
Visitor
Posts: 1
Registered: ‎11-11-2013
My Device: Z10
My Carrier: Telekom

Re: Communication Logs: action.eassync failure

Any updates on this? 
Getting the same error with iOS 7 and UDS 10.1.3.