It is really easy to do and reduces your risc to 0. Added: New options in Calendar (show only work hours, auto scale) Improved: Module selection bar Fixed: All known issues since last version Applies to EssentialPIM Pro only Changes for v3.73 - v3.74. Upon the next sync, no more problems, no more BAD REQUEST, no more http 400 errors.Ĭould it be, that this problem just have been caused by changing the database structure at Google's, in combination with unidirectional syncing?Īnyway, I really hope, this helps you as good as it helped me.įor those who do not want to risk their contacts database destroyed by a faulty synchronization, I do recommend to copy your database before trying this. So I reversed the direction again to its original setting: One direction, from EPIM to Google. Then I saw, that several fieldlabels had been added/changed during the sync from Google to EPIM. To my surprise, that worked fine, no BAD REQUEST, no http 400 error. Mind you, I always performed a single directed sync, from EPIM to Google, that is.Įver since the upgrade to EPIM r9.9x, that went wrong.įinally I decided to reverse the sync direction: So the new setting was One direction, from Google to EPIM. On every sync attempt I received a BAD REQUEST error (http 400) Since I upgraded to r9.9x I had this http 400 sync problem, every time I tried to synchronize with Google: I experienced the same problem, when I upgraded from EPIM r9.6 to r9.95, r9.96, r9.97. Ehm.I just may have found a clue to this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |