03-02-2015 05:41 PM
If you are on Act! v16 or Act! v17 there is an update that will fix it.
03-02-2015 05:42 PM
You need to upgrade to 16.3.
03-04-2015 08:11 AM
Act! 16.3 is the fix so you'll need to upgrade to that version.
03-04-2015 08:25 AM
Thanks - part two of the question above was: Does it work? I'm interested in hearing from folks who have tried it and give it the thumbs up. Appropriately lacking full trust at this point. Thanks.
03-11-2015 09:14 AM
Since you are the ACT Moderator for this thread, I am sending this to you through the thread
on March 2, 2015 you wrote
Google Integration Fix is available now in 17.1 and 16.3.http://kb.swiftpage.com/app/answers/detail/a_id/38005/
Thank you for your patience.
I really need your HELP!!! As of today, I am still unable to Integrate Act v17.1 with my Google Calendar. I own my company and have full admin privileges. I also have .NET v 4.5.2 installed. I have done everything that has been suggested in this and other threads to have your software function with Google Calendar with no success. [Special thanks to Stan Smith]. I am way beyond all the emotions everyone have expressed. I simply MUST HAVE you or someone you designate actually FIX this longstanding failure.
PLEASE, I BEG YOU, PLEASE FIX THIS.
I am attaching two screen captures showing you the exact integration history results when doing both a Scheduled integration and a Manual integration. The Exception, Source, and Call Stacks are different. I am running Act Pro v17.,1; with .NET framework 4.5.2 installed and I have full Admin priviledges. I really hope this helps.
Scheduled Integration result:
CONTEXT: Syncronizing Activities; DESCRIPTION: Value cannot be null. Parameter name: source; EXCEPTION and SOURCE: System.Core
Manual Integration results:
Again, Please Help.
03-12-2015 05:38 AM
I'm curious as well if any one has had sucess implemting the fix for V16 owners. I am eery of the "fixed" version just simply based on the way they've handled this whole situation.
I'll have time this weekend to mess around with it, but I'm backing up my act contacts, setting a restore point, and taking an image of my hard drive because I have little faith it will work. It appears V17 isn't fixed yet for all as noted in this thread. Perhaps they just threw us a placebo to buy them more time? ;-)