bennor3814

So far as I've seen, it doesn't appear that this bug has been acknowledged by the developer. This bug apparently has been mentioned in several other open requests in the past: https://sourceforge.net/p/googlesyncmod/bugs/1411/ https://sourceforge.net/p/googlesyncmod/bugs/1410/ https://sourceforge.net/p/googlesyncmod/support-requests/1026/ I've rolled back to 4.1.33 which doesn't exhibit this issue that 4.2.1 did and just ignore the 4.2.1 update nag message when running/using the program.

None that I found, I just rolled back to 4.1.33, and then just ignore the new version nag notice every time I run the Googlesyncmod application and do a sync.

Roll back to version 4.1.33 and it should sync properly without the errors one gets n 4.2.1.

Probably the same or similar issue as reported here: https://sourceforge.net/p/googlesyncmod/bugs/1410/ https://sourceforge.net/p/googlesyncmod/bugs/1408/

Sounds like the same or similar issue mentioned here: https://sourceforge.net/p/googlesyncmod/bugs/1408/ And earlier in the Support subforum: https://sourceforge.net/p/googlesyncmod/support-requests/1026/

Can confirm. Both 4.2.0 and 4.2.1 have the issue in my setup. Downgrading to 4.1.33 and the sync runs correctly, without this issue.

V4.2.1 - Every sync indicates "Updated from Google to Outlook"