Execution of request failed


Trying to run my first sync after installing, checked the password several times, also stoped using 'special' charactors in the password buy I get this message:
Please report this error:
Execution of request failed:
Device T-Mobile MDA, WM6


rwbolt wrote Jun 13, 2007 at 7:15 AM

Same issue on an Eten X500 with WM6. My Password contains only letters and numbers.

wrote Jun 30, 2007 at 12:25 AM

mapitman wrote Jun 30, 2007 at 12:27 AM

I am getting a similar error when I attempt to sync. It downloads the events, then uploads any changed events and then I get a message box with the error:Execution of request failed: http://www.google.com/calendar/feeds/default/private/full

mapitman wrote Jun 30, 2007 at 12:28 AM

I forgot to mention that I am running on a T-Mobile MDA, WM5 and I do use a proxy to connect to the web.

wrote Oct 9, 2007 at 12:57 PM

wrote Oct 17, 2007 at 5:47 AM

wrote Mar 1, 2008 at 5:23 PM

reo4ua wrote Mar 1, 2008 at 5:23 PM

Same error here on HTC/Cingular 8125

thebourboncowboy wrote Mar 27, 2008 at 4:09 AM

This is not a problem with gmobilesync. You do not have enough space left on your phone. delete something. if you downloaded the cab files for install, start with those. If you are low on space your phone can't establish a data network connection.

wrote Jun 4, 2008 at 6:34 AM

llama233 wrote Jun 4, 2008 at 6:36 AM

Same issue for me with a Telecom NZ Okta Agent (a rebranded Pantech or something I think). It only started doing this a few days ago, before that was fine.

wrote Jul 11, 2008 at 9:50 PM

msmalazan wrote Jul 11, 2008 at 9:50 PM

Same error. I don't think it's a problem with space...I'm using it on my PDA and have tons of room.

lifanxi wrote Feb 5, 2009 at 5:27 AM

Can be reproduced with GMobileSync 1.3.6.

This seems to be a bug in the old version of Google Data API, because the URL requested contain unacceptable characters: ":" or "+", these characters should be escaped. This URL is generated by the Google Data API, from the GMobileSync side, we only pass DateTime value to the APIs.

After upgraded the Google Data API Library to 1.3.1, this problem seems to be disappeared.

[Change Set]

wrote Feb 5, 2009 at 5:27 AM

wrote Feb 14, 2013 at 12:35 AM

wrote May 16, 2013 at 4:03 AM

wrote May 16, 2013 at 4:03 AM

wrote Jun 14, 2013 at 8:21 AM