gSyncit Frequently Asked Questions and Common Solutions
Provided below are many of the frequently asked
questions and issues experienced by end-users of this
product. Please consult this information first before
contacting product support.
APPLICATION ERRORS /
PROBLEMS (CLICK TO EXPAND)
INSTALL / LICENSE / BACKUP QUESTIONS (CLICK
TO EXPAND)
APPLICATION CONFIGURATION & OPTIONS QUESTIONS (CLICK TO EXPAND)
COMMON APPLICATION ISSUES (CLICK TO EXPAND)
GOOGLE SYNC (CLICK TO EXPAND)
TOODLEDO CONFIGURATION (CLICK TO EXPAND)
POCKET INFORMANT CONFIGURATION (CLICK TO EXPAND)
NOZBE CONFIGURATION (CLICK TO EXPAND)
SOLUTION:
If you encounter the error "Can have at most one
primary email address, found 2" this error happens when
you have two or more contacts in Gmail that have the
same exact email address set as the primary email
address. gSyncit tries to match up entries to avoid
duplicates but if two contact entries exist but share
the same email address then this error will come up when
gSyncit tries to add a new contact to Gmail.
The way to resolve this is to consolidate multiple
contact entries in Gmail that share the same email
address into a single entry. You can optionally use the
"Find & merge duplicates" option in Gmail which will
consolidate your contacts into a single entry. The
following image shows how to access this feature in
Gmail.
SOLUTION:
On the gSyncit Nozbe sync mapping select the Other
tab as shown above and enable the option to sync Outlook
user-defined fields with Nozbe task fields. You can
use the default mapping or control which Outlook
user-defined fields are synced with specific Nozbe task fields.
To use/display the extended Toodledo properties from
within the Outlook task list select the Outlook task list
you are syncing with. Then right-click the task list columns,
open the field chooser, select "User-Defined fields in
folder" ...
... on the field chooser click "New..." and add the
following custom fields to this list: @Context,
@Next, @NextSort, @Project, @ProjectSort and @Tag. All fields
are of type "Text" except the "@Next"
field which is is YesNo/Boolean.
... Once that is completed _drag_ each of these newly
created fields into the Outlook task list view COLUMN
area to place each field into the task list view.
IMPORTANT: To make sure these values are
populated from Nozbe on the initial sync change the
primary source on the gSyncit Nozbe mapping use
Nozbe so that the Nozbe values will be imported
into Outlook first. Otherwise, after the initial sync
these user-defined fields may not be populated.
SOLUTION:
On the gSyncit Toodledo sync mapping select the Other
tab as shown above and enable the option to sync Outlook
user-defined fields with Toodledo task fields. You can
use the default mapping or control which Outlook
user-defined fields are synced with specific Toodledo
task fields.
To use/display the extended Toodledo properties from
within the Outlook task list select the Outlook task list
you are syncing with. Then right-click the task list columns,
open the field chooser, select "User-Defined fields in
folder" ...
... on the field chooser click "New..." and add the
following custom fields to this list: @Context,
@Location, @Star, @Meta, @Folder, @Goal, @Priority,
@Status, @Length, @Tag, @GroupID and @TaskID. All fields
are of type "Text" except the "@Length" field which is a
"Number" type and @Star with is YesNo/Boolean. @GroupID
allows sorting tasks and related subtasks together.
... Once that is completed _drag_ each of these newly
created fields into the Outlook task list view COLUMN
area to place each field into the task list view.
IMPORTANT: To make sure these values are
populated from Toodledo on the initial sync change the
primary source on the gSyncit Toodledo mapping use
Toodledo so that the Toodledo values will be imported
into Outlook first. Otherwise, after the initial sync
these user-defined fields may not be populated.
SOLUTION:
If you receive a "Attempted
to perform an unauthorized operation" while registering
then follow these steps to correct this issue caused by
gSyncit being blocked from updating you Windows
registry.
1. Close Outlook
2. Locate the Outlook program icon and right-click it
3. Select "Run as Administrator"
4. Register gSyncit
SOLUTION:
In some instances after installing gSyncit users may notice that Outlook
terminates when loading or reports that Outlook is indicating that gSyncit did
not exit properly and Outlook wants to disable it.
To help determine the root cause of this issue it is recommended to check the
Windows event logs accessible from the Windows control panel and look for any
errors related to Outlook. There is a good chance that if gSyncit caused Outlook
to fail that their will be an error that contains details similar to the
following error ...
Problem
signature: Problem Event Name: APPCRASH Application Name: OUTLOOK.EXE Application Version: 11.0.8326.0 Application Timestamp: 4c1c2372 Fault Module Name: mscorlib.dll
This error indicates that the Microsoft .Net Framework which is used the
run/execute gSyncit encountered a failure causing the OUTLOOK.EXE process to
crash.
To resolve this issue the Microsoft .Net Framework v3.5 installation needs to be
repaired or reinstalled. There are several ways to go about doing this...
SOLUTION #1:
WINXP:
Go to the "add/remove programs" applet found on the
windows control panel. From here the Microsoft .Net
Framework can be removed/uninstalled. Once uninstalled
go to the following link to download and reinstall the
Microsoft .Net Framework
Go to the "programs and
features" applet found on the windows control panel. The .Net Framework can be removed
by turning this "feature" off and then turning it back on. You will
need to restart Windows after this. If you are
using gSyncit v3.6 turn on/off .Net v3.5 and if you are
using gSyncit v3.7 or higher turn off/on .Net 4.0
SOLUTION #2:
The next approach is to use the .Net cleanup utility to fully remove the
Microsoft .Net Framework from your system and reinstall it. To do
this take the following steps ...
1. Download the Microsoft .Net Cleanup Tool from the following link ...
So far this solution has worked the best to correct this issue.
SOLUTION:
This error indicates that
the gSyncit settings file cannot be read and
might be corrupt. Delete the gSyncit
settings file referenced in the error
message. gSyncit does maintain a backup
which gSyncit will attempt to use.
Otherwise, you will need to reconfigure
gSyncit when Outlook is restarted.
For example, the error that commonly appears is
...
"Internal error. Failed to load settings
[C:\Documents and Settings\(user)\Application
Data\gSyncit\settings.xml]. Invalid character in
a Base-64 string."
To resolve this open the windows file explorer
and navigate to the folder noted in the error
message (e.g "C:\Documents
and Settings\(user)\Application Data\gSyncit\").
Then delete the file "settings.xml" and restart
Outlook.
You will need to reconfigure gSyncit after doing
this.
BACKING UP OUTLOOK/GOOGLE DATA:
You can backup your
Outlook data by simply making a backup copy
of your Outlook .pst file. If you do not
know the path to your .pst file you can
retrieve is by using the "Mail" applet on
the Windows control panel and click "Data
Files". If you should need to restore your
data you can either replace the .pst file
with the backup copy or open the .pst file
from within Outlook and copy the data into
your Personal Folders.
Another more simplified
option is to create a copy of an Outlook
folder you plan to sync and configure the
sync process to use the COPY of your Outlook
data rather than your master/original data.
In this case you are working from a staging
or temp copy of your data to test the sync
process.
To backup your Google data use the Google
options available for Gmail and Google to export
your data. Google does not provide a way to
export tasks so you will not be able to backup
this information.
Check that the correct 32/64 bit version of gSyncit
is installed. If you are not using a 64-bit version
of Outlook which includes Outlook 2010/2013 64-bit
then you need to install the 32-bit version
of gSyncit. You can check the "about" information for
both gSyncit and Outlook to confirm this.
A common mistake is installing the 32-bit version of
gSyncit when using the 64-bit version of Outlook.
This causes the gSyncit toolbar to not appear on the
Outlook toolbar and the sync will not work.
There is no difference in performance or
functionality between the 32/64 bit versions of
gSyncit.
SUGGESTION #2 - CHECK OUTLOOK ADD-IN
DISABLED ITEMS
Check if gSyncit has been disabled by Outlook. To
do this...
Outlook 2003
- In Outlook click Help / About / Disabled Items
/ enable gSyncit
Outlook
2007 -
In Outlook click Help / Disabled items / enable
gSyncit
Outlook 2010 - In Outlook click File /
Options / Add-ins / Select "Disabled Items" from the
"Manage" list and click "GO" / enable gSyncit.
Outlook 2013 - In Outlook click File /
Options / Add-ins / Select "Disabled Items" from the
"Manage" list and click "GO" / enable gSyncit.
In Outlook 2013 you
can also check the disabled items directly from the
File / Info menu as follows to make sure gSyncit is
not set as disabled by Outlook.
SUGGESTION #3
Try logging out and back into Windows and then start
Outlook.
SUGGESTION #4 - CHECKING MACRO SECURITY
In Outlook open the Macro Security settings and
check that it is set to at least "Warnings for signed
macros; all unsigned macros are disabled". It should
not be set to "No warnings and disable all macros"
as this will prevent gSyncit from loading into Outlook.
After making this change go to the Outlook add-ins
list and re-enable the "gSyncit for Outlook" addin.
SUGGESTION #5
There might be a conflict with
another add-in. You may need to try turning off
other add-ins to determine which one is conflicting
with gSyncit.
SUGGESTION #6
1) Uninstall gSyncit (Click Start/Programs/gSyncit/Uninstall)
2) Remove the folder c:\program files\gsyncit
3) Reinstall gSyncit from the gSyncit Download Page
SOLUTION:
This error is typically associated
with additional error information that includes
the following ... "This operation
failed because the QueryInterface call on the COM
component for the interface with IID '{00063001-0000-0000-C000-000000000046}'
failed due to the following error: Error loading
type library/DLL. (Exception from HRESULT: 0x80029C4A
(TYPE_E_CANTLOADLIBRARY))."
The critical
part of this error message is the error code TYPE_E_CANTLOADLIBRARY
which is returned by the windows operating system.
This error is then returned by gSyncit indicating
that an Outlook registry entry is missing/empty
or pointing to an invalid file location.
Additionally,
another error code associated with this type of
error is TYPE_E_LIBNOTREGISTERED. This can
occur when certain Outlook components are not registered
properly and a particular Outlook component could
not be correctly located in the Windows registry.
SOLUTION
#1 (TYPE_E_LIBNOTREGISTERED)
1. Access the registry via Start, Run,
Cmd, RegEdt32, enter. 2.
Navigate to HKEY_CLASSES_ROOT\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib
3. You should find a 'default' entry with the
value '{00062FFF-0000-0000-C000-000000000046}'
4. You should find a 'version' entry with the
number '9.3'. If not, change the version to 9.3.
If using Outlook 2010 the version should be 9.4
SOLUTION
#2 (TYPE_E_LIBNOTREGISTERED)
This solution is for
using Visio 2010 with Outlook 2007 or older.
1. Access the registry via Start, Run, Cmd,
RegEdt32, enter. 2.
Navigate to HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}
3. You should find an entry with the number '9.4'.
4. Right click on the entry '9.4' and choose 'Rename'.
5. Rename the entry from ‘9.4’ to "DoNotUseThis9.4".
6. Close 'Registry Editor' window.
7. Open Outlook
SOLUTION #3 (TYPE_E_CANTLOADLIBRARY)
Access the registry via
Start, Run, Cmd, RegEdt32, enter.
Once the registry editor
loads up, do a search (ctrl F3) on "00063001-0000-0000-C000-000000000046".
The registry should find a key located under the
HKEY_CLASSES_ROOT -> CLSID subkey.
Expand this key and you
should see 3 nodes: ProxyStubCLSID,ProxyStubCLSID32
and the important one - TypeLib. Essentially what
is happening is that when you make the COM call
to a specific Office assembly. The assembly opens
up the registry and finds this key which gives it
the CLSID of the TypeLib it must call in order to
initiate a call to the COM.
Under the TypeLib key
copy the (Default) Entry (It should be
another long CSLID key). Now the easiest way to
find this new key entry relating to the CLSID, is
to go back up to the root key, HKEY_CLASSES_ROOT
and look for the TypeLib subkey. Do this simply
by pushing "T" on the keyboard until you get to
the key "TypeLib".
Once you find this key, highlight the key and do
a search (Ctrl F3) from this key for the TypeLib
CLSID that you copied earlier. Once you find it,
expand it and see if there are multiple versions
of the typelib i.e. 8.3, 8.4, 8.5. You want to eliminate
the the later versions that are pointing to non-existant
TypeLib's.
To do this, expand the Version key (ie. 8.3), then
expand the "0" key, then the win32 key and check
the value of the default entry. This value should
be a file path. This path likely points to a location
that does not exist. Simply delete this key, and
now when the COM interface attempts to locate the
latest TypeLib it will find one that does indeed
exist, and will hopefully run error free.
SOLUTION #4 (TYPE_E_CANTLOADLIBRARY)
1. Access the registry via Start, Run, Cmd,
RegEdt32, enter.
2. Locate the key HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}
and expand it.
3. Rename the the "9.4" key to "DoNotUse9.4"
SOLUTION #5
Try having
Outlook automatically diagnose and repair this issue.
Outlook 2003
1. From Outlook click Help -> Detect
& Repair ...
Outlook 2007
2. From Outlook
click Help -> Office Diagnostics ...
SOLUTION
#6
In some instances,
rather than reinstalling Microsoft Office, users
have reported some success installing the Microsoft
Primary Interop Assemblies which can downloaded
from the link below.
Use the Microsoft Installation
Cleanup Utility to remove the installation.
This download is available here: Microsoft Installer
Cleanup Utility
1) Download and unzip the
utility to a temporary folder
2) Run Microsoft Installation
Cleanup "msicuu.exe"
3) Select and remove gSyncit
(make sure Outlook and gSyncit are not running)
4) Delete the C:\Program
Files\gSyncit or
C:\Program Files (x86)\gSyncit
directories using the Windows File Explorer.
5) Reinstall gSyncit
SOLUTION:
This error indicates that
Google requires you to re-authenticate your
Google account.
To correct this log into
www.google.com/calendar
and follow the instructions after logging in.
Once you have access logged into your Google
account gSyncit should now be able to access your calendar.
SOLUTION:
This error if you exceed
the number allowable updates/requests to Google
services per day. This "quota" is
consists of 10,000 Google API calls per day per
account.
When you encounter this error you need to wait 24 hours for Google to allow
updates and you may also want to reduce the amount of data
and/or sync frequency
of your calendar sync.
Users have reported that if they delete and
recreate a Google calendar this "limitation" can
be corrected immediately rather than waiting for
the quota to be removed from a calendar but this
is not always possible.
SOLUTION:
NOTE: This information
applies to syncing tasks with a Google calendar.
When syncing tasks it is
possible to update Outlook task properties using
the task properties populated in message body
of a Google calendar event by gSyncit. To enable
syncing Task properties to Google events set
the option "Sync Outlook task properties in
the Google event description" as shown below.
Outlook task properties stored
in Google events are synced back to Outlook
to update the corresponding Outlook task properties.
Shown below is an example of a Google calendar
event with these extended Outlook task properties.
Updating these properties
stored in the Google calendar event description
will sync back to Outlook tasks.
Using the above screen shot,
setting "Completed: True" will cause the Outlook
task to be marked as completed. Setting "Importance:
High" will set the Outlook task priority to
"High". Setting "Status: InProgress" will set
the Outlook task status to "In Progress". The
other numeric values match to their corresponding
equivalents in the Outlook task.
Here are all the available
values for these properties
Complete = True
or False
Importance = Normal
or High or Low
Status = NotStarted,
InProgress, Deferred, Waiting,
Completed
SOLUTION:
Setting up gSyncit to sync
all Outlook contacts with Gmail's "My Contacts"
group is very simple. Simply open the contact
mapping and change the "Google Gmail Contact
Group" setting to "System Group: My Contacts".
Shown below is an example of what this configuration
looks like.
SOLUTION:
This is a fairly common request
and it is amazing that Google has yet to offer
this option in Gmail. Outlook allows contact
names to be "displayed" as last, first while
they are stored as "first last". Gmail has yet
to make such an option possible and such a feature
seems quite logical and useful when someone
is searching for contacts.
gSyncit allows for syncing
Outlook contacts to Gmail so that contacts are
listed in Gmail as last, first.
To accomplish this gSyncit
uses the Outlook Contact "FileAs" value when
writing Gmail contact full names. To turn on
this sync option select the "Sync Options" tab
for a contact mapping and check the option "Use
Outlook contact 'FileAs' value for Gmail contact
names. During the sync process gSyncit will
use the FileAs value to populate the Gmail contact
full name. When syncing back to Outlook gSyncit
will convert the Gmail contact name back into
to correctly formatted Outlook contact full
name.
Below is the contact mapping
option for enabling this functionality:
Below is the Outlook FileAs display setting
that nneeds be set to "last, first" to sync
Outlook contact names to Gmail contacts names
as "last, first".
SOLUTION:
Calendar mappings can be configured
to sync Outlook categorized events to different
Google calendars and Google accounts. For example,
one calendar mapping can be configured to sync "Personal"
categorized events to your "personal" Google calendar
and "Work" categorized events with your "work" Google
calendar.
Additionally, many users like
the concept where the Google calendar can show multiple
calendars at the same time in a single view. Outlook
does not support this natively but a similar view
can be achieved by assigning items from different
Google calendars to categories of varying colors.
These categories are are then used to filter which
events in an Outlook calendar will be synced with
the Google calendar associated with the mapping.
As a quick, all items in an Outlook
calendar with the category "Personal" can be synced
with Google calendar 1. All items in the Outlook
calendar with the category "Work" can be synced
with Google calendar 2.
How do you do this ...
Create a calendar mapping for
EACH category that you would like to sync.
On EACH calendar feed select the category
tab and assign each feed a unique category name
either by selecting it from the drop down or manually
entering in a name.
Then, select the radio button
that says "Only write appointments to Google that
contain any of these categories" AND check
the box that says "assign these categories to entries
imported from the Google calendar". This is an important
step. If you don't do this you'll end up with all
appointments in all calendars.
What this configuration is doing
is telling gSyncit to link your Outlook and Google
calendars together and to only sync items that match
the specified category.
Below is a screen shot of a simple
configuration that filters events in a calendar
assigned to the Outlook "Personal Events" category.
A product license key can be moved between
computers as needed.
To move your license to a new computer first unregister
a license from your
current computer using the "Unregister" button
found on the gSyncit settings / register panel
(shown below). Once your license has been
released you can now apply
your license to the new computer. On the new
computer open the same "Register" panel and
click the "Register" button to register the
software.
SOLUTION:
From the windows system tray
right-click the gSyncit tray icon and select "Auto
Start". This will unselect this option which disable
gSyncit from loading up when a user logs in.
Optionally, if you are using
the latest release of gSyncit you can change this
setting from the gSyncit settings "Sync Options"
panel
In gSyncit v2.0 You can import/export
your settings by selecting the export/import
buttons on the settings menu.
SOLUTION:
Syncing Google Gmail Groups
with Outlook contact categories:
Configuring gSyncit sync Outlook
categories with Gmail groups is very simple and
takes just a few configuration steps. There are
various configuration options for syncing Gmail
groups and Outlook categories but the more typical
and recommended setup is to use the option to automatically
sync Gmail groups with Outlook categories.
Here's how to sync Outlook categories
with Gmail groups automatically...
1) On the contact
mapping dialog on the "Contact Mapping" tab select
the "System Group: My Contacts" groups. By setting
this option you are telling gSyncit to use the "My
Contacts" list as your main contact list vs. the
"All Contacts" list. This does two thing: first,
it eliminates the "My Contacts" group from appearing
in the Outlook categories and allows for your contacts
to appear on most mobile devices which use this
same group.
2) On the "Gmail Groups" select the option "Automatically
sync Gmail groups with Outlook categories." When
this option is selected gSyncit will match existing
Gmail groups with Outlook categories and create
any Gmail groups to match with Outlook categories.
SOLUTION:
You can sync your outlook notes
assigned to different categories with different
Google document folders. This is done by creating
a notes mappings for each category that linking
your outlook notes folder to different Google document
folder and then use the category tab on each mapping
to filter items by a specific category.
For example, if you want to sync Outlook Notes assigned
to the "red category" with the Google documents
folder called "red folder" simply create a mapping
that links your Outlook notes folder with your Google
documents "red folder" AND on the category tab set
the mapping to only sync items assigned to the "red
category" and to assigned items to this category
that are imported from Google. Repeat the above
for each category/Google folder combination.
Below is an example showing how to setting up a
notes mapping that only syncs Outlook notes assigned
to the "Red Category".
SOLUTION:
Open the folder list
view in Outlook by clicking on "View/Folder
List". For a folder list view sample click
here.
Highlight one of the
folders (Calendar, Contacts, Tasks, or Notes)
where you suspect the problem exists, and
change its view to ‘By Category'. To do
this click on "View/Current View/By Category".
Sort the records ‘By
icon’. To do this, click the folded page
icon in the title bar above the category
heading.)
Click on the "+" sign
next to the "Category" heading and scroll
down until you find one or more items with
a crossed swords icon. Click here to see
a picture of a "crossed sword" icon.
Double-click on the item
with crossed-swords and from the "Conflict
Resolution" window select to keep the item
with the most recent date.
Synchronize.
SOLUTION:
1. Check that the Google Account type is
set correctly. If you are using a hosted account
then set the account type to HOSTED. Otherwise,
set the account type to DEFAULT.
2. Try creating a task in the Google task
list and then remove the task from the task
list. After this try using the gSyncit task
sync.
3. Check that you have the Microsoft .Net
v3.5 framework installed which is a required
component for gSyncit to work properly. The
Microsoft .Net Framework v3.5 SP1 can be
installed from the following link ...
This error appears when updating an Outlook
recurring event with a Google recurring event
and Outlook cannot apply the Google recurring
event changes to the current Outlook recurring
event structure.
To resolve this issue
you can recreate the Google event in your Google
calendar, delete the original event, and then
re-sync.
SOLUTION:
This error indicates that the internal gSyncit
sync database is corrupt. To resolve this issue
delete one of the following file and then restart
Outlook...
C:\Documents and Settings\(current user)\Application
Data\Local Settings\gSyncit\syncdata6.db
SOLUTION:
Resolving duplicates can be a complex and
frustrating process.
If duplicates are occurring when setting up
gSyncit it may make sense to simply clear out
the Google destination and do a clean sync from
Outlook to Google. If this path is taken it
is recommended that the repair feature be used
on the gSyncit settings dialog after clearing
the Google destination before syncing.
Here are some common issues related to duplicates
and why they may occur...
CALENDAR: When syncing calendar events
if you see duplicates during the sync this may
indicate one of the following...
gSyncit was unable to match existing
items between Outlook/Google calendar and
created a new calendar entry. Events are
matched based on start date/time and subject.
If there is no exact match then gSyncit
will create a new entry.
There is a time zone mismatch between
Outlook and the Google calendar which can
cause a date/time mismatch when attempting
to pair items between Outlook and the
Google calendar based on the event start
date/time.
If the duplicate items are recurring
birthday events it is possible that Outlook
has auto created birthday events as part
of the contact sync which has added additional
items to the calendar unexpectedly. When
a contact is added to Outlook or a birthday
is set on an Outlook contact then Outlook
will auto create a birthday event in the
users calendar. This can result in two birthday
events appearing for the same event.
You can work around this by un-checking
the option on the contact mapping to "Sync
contact birthdays and anniversaries" which
will prevent Outlook from auto creating
events related to these dates.
CONTACT: When syncing contacts duplicates
can occur for the following reasons...
gSyncit was unable to match exiting
items between Outlook/Gmail and created
a new contact entry. Contacts are matched
based on full name, company name, and primary
email address. If there is no exact match
then gSyncit will create a new entry.
The contact exists multiple times in
the user's contact list. This issue appears
more often with users that have thousands
of contacts where spotting a duplicate is
much harder.
SOLUTION:
The root cause of the issue is that the request
contains invalid data that was rejected by Google
services. This error most frequently appears
during a contact sync.
When gSyncit is set to use gzip compression
for faster communications with Google this will
hide any additional details that may help diagnose
this issue. If this error occurs it is recommended
that the g-zip compression option found on the
connection/general panel on the gSyncit settings
dialog be unchecked. Then run the sync
operation again to see the additional error
details that may be helpful to diagnosing the
cause of the error.
Reference to a foreign...
If you receive the error that states "Reference
to a foreign group..." then open your contact
mapping and reselect your Gmail Group.
Missing attribute: 'key'
If you receive an error indicating "Missing
attribute: 'key' this indicates that your Gmail
contact contains a user defined field that does
not contain a label. To resolve this issue provide
a label value for any user defined fields in
your gmail contact. The Google contact service
currently returns an error when attempting to
update a Gmail contact that contains a user
defined field with a "Label" that is not set
for a user defined "Custom Value".
If the error does not contain any additional
details for contact record sync failure, you
can often work around this issue by simply recreating
the contact record and deleting the old contact.
If you are unable to determine the cause
of the issue please report the error to product
support for assistance.
The 403 error can occur as a result of an
attempt access Google data that you do not have
access to or Google rejecting your request as
a result of an authentication related failure
(Google does not trust the request). A 403 error
can occur for a number of other reasons but
these are the most common.
CALENDAR SYNC / 403
If this error notes "User has modified too many
events today. Please try again tomorrow" it
indicates you've exceeded the maximum allowed
updates to your Google calendar by Google. You
need to wait 24 hours to clear this issue. It
is recommended to sync less frequently and to
sync using the day range to reduce the frequency
and the amount of data being synchronized with
a Google calendar.
This error can also indicate an attempt to
update a read-only calendar. This can easily
be corrected by setting the gSyncit calendar
mapping to sync from Google to Outlook only.
In the latest releases of gSyncit the option
to sync from Outlook to Google for read-only
mappings is automatically de-selected when configuring
a new calendar mapping.
CONTACT SYNC / 403
When this error occurs related to contact
entries the following items should be reviewed
to resolve this error.
SOLUTION #1
Check that your gSyncit mapping Google username
is your full email address (e.g. username@gmail.com)
and that the Google account type is set to 'default'.
SOLUTION #2
Try reselecting the Gmail Group associated
with the gSyncit contact mapping.
Additional Causes
Beyond the scope of calendar and contact
events a 403 error can also appear when the
user has exceeded the maximum number of requests
Google allows per day or attempts to update
or access a resource/item that has been deleted.
If you have exceeded the number of allowed
updates then you may need to wait between 24
hours and a week for this to be reset by Google.
Here's more information on Google having a max
on the number of updates allowed to calendar
in a given week:
Starting in v2.0 the sync
interval logic was updated such that the next
sync is determined by the last sync and does
not factor in when Outlook was started. For
example, if the sync interval is every 30 minutes
then the next sync will be 30 minutes after
the last sync. If Outlook is closed for 24 hours
then when Outlook starts up the next sync time
be "past due" and, if the current time is within
the allowable sync time frame, will trigger
gSyncit to start the sync process. This behavior
is by design.
The primary source for a
mapping tells which direction (Google to Outlook
or Outlook to Google) to sync first data when
performing a two-way sync. This option only affects
the very first sync that is performed for a
mapping.
The reason this is option is important is when
the first sync is performed the source will
overwrite the destinations data. Selecting
the primary source tells the sync process which
data takes priority over the other.
For example, if you primarily update your Google
calendar and it contains the most up-to-date
information then when you perform your first
sync you'll want your Google data to replace
your Outlook data first so that Outlook has
the most current information. After this initial
sync the primary source selection no longer
affects the sync process.
Solution:
Check the Gmail contact group
you are viewing in Gmail and syncing with using
gSyncit. gSyncit, by default, will sync with the
Gmail "All Contacts" list which means that not all
contacts will be in the "My Contacts" group. Many
third party mobile sync applications sync with the
"My Contacts" Gmail group so it may be necessary
to set the main Gmail group on the gSyncit contact
mapping to "My Contacts" instead of "All Contacts".
If you'd like your Outlook contacts
to sync to the "My Contacts" group by default and
enable mobile sync products to see your Gmail contacts
then simple change the "Google Gmail Contact Group"
on the gSyncit contact mapping to "System Group:
My Contacts" as shown below.
Solution:
It's difficult to say what the
exact cause of this issue is but it's recommended
that the Outlook scanpst.exe utility be used to
repair the local outlook .pst file. In many cases
this resolves these types of issues.
You can locate scanpst.exe by searching your 'C:\Program
Files' directory for "scanpst.exe"
Solution:
This error can happens for a
number of reasons but typically occurs when their
is a communications failure with an exchange server.
Since the error is occurring outside the scope of
gSyncit and typically occurs when attempting to
read information from an Outlook folder the suggested
resolution to this issue is to retry the sync.
Solution:
If you are using a version older than
v1.15.10 then this issue is caused by an invalid
time zone setting on the gSyncit settings dialog.
When the time zone is not configured properly then
events will appear as all day events in the Google
calendar.
Starting with v1.15.10 and higher
time zone information used to create recurring events
in the Google calendar is taken directly from the
Google calendar settings. Below is an example of
what this configuration looks like. If this information
is not configured properly then this can caused
events in the Google calendar to appear with incorrect
times.
Solution:
When syncing contacts gSyncit
attempts to resolve/match contacts between the
two lists to prevent duplicate events. The logic
is very simple. When a contact is inserted into
either Outlook or Gmail then gSyncit will do
search for a similar contact by full name/company
name and email address.
This matching logic is also
a reason why the sync process is slightly slower
than other sync applications. This matching
logic is applied when syncing a new entry so
typically after the initial sync the sync process
runs much faster.
When syncing from Gmail to
Outlook duplicate items can appear in the Outlook
contact list if the above matching logic fails.
One reason the matching logic can fail is if
the Gmail contact full name is stored as first
last and the Outlook contact full name is stored
as last, first. In some instances gSyncit will
not be able to properly match these entries
causing a duplicate item to appear in Outlook.
Another case would be where both the Gmail and
the Outlook contact information matches up except
either the Gmail or Outlook contact does not
contain an email address or matching/different
company name.
When syncing from Outlook
to Gmail the Gmail contact list supports storing
a single email address once within the entire
Gmail contact list while Outlook does not have
such a limitation. This can cause issues where
two or more Outlook contacts in outlook with
the same email address/full name can end up
being mapped to the same Gmail contact. When
this happens the total number of contacts in
Outlook and Gmail will be different since gSyncit
ends up resolving the duplicate Outlook contacts
to the same Gmail contact.
Solution:
Entries marked as private
will appear with no appointment details and
the subject will appear as "(no subject)".
Solution:
Disable the 'Assist Outlook
exit/shutdown process to prevent it from running
in the background' found on the General Settings
panel on the gSyncit settings dialog.
Solution:
"Cannot
access the calendar you requested" is a
Google calendar service error that occurs
when the calendars service hosted on
Google's servers cannot access the specified
calendar. This is an internal and
intermittent Google calendar service issue
and the way to resolve this is to retry your
request.
This this issue happens frequently consider
setting the automatic sync option to sync
less frequently (1 time per hour) or
increase the Google retry count to 5 on the
gSyncit settings / general panel.
Solution:
The error "...
does not have read privileges on the
calendar owned by ... " occurs when
attempting to sync or access a Google
calendar where the current Google account
associated with the gSyncit calendar mapping
does not have read access to the Google
calendar.
To correct this try reselecting the Google
calendar associated with your gSyncit
calendar mapping.
Solution:
When connection to Google servers there are
two accounts types that can be associated
with a Google username: GOOGLE and HOSTED.
The account type tells gSyncit how you want
you account to be viewed when logging into
Google.
In general if you are using a stndard
gmail.com account then the account type
should be set to DEFAULT. If you are using a
Google Apps for Domains account then the
account type should be HOSTED. There is
little reason to use the GOOGLE account
type.
Solution:
note: This information applies to
syncing with the Google task lists only.
To configure the task sync process to sync
Outlook categorized tasks with different
Google task lists you need to start by
creating a Google task list for each
corresponding Outlook category that you want
to sync. Then you need to create a gSyncit
task mapping for EACH Outlook
Category/Google Task Group pair. On each of
these mappings you configure them to sync
your Outlook task list with a specific
Google task list. Then on the categories tab
you select the category you want to use to
sync Outlook tasks with the selected Google
task list using the option to only sync
items assigned to the specified category.
For example, if the Outlook task list
contained a category called "Work Tasks" and
there was a Google task list called "Work
Tasks" then to sync this category with the
Google task list a task mapping would need
to be created that has the Google task list
"Work Tasks" selected and on the category
there the option to only sync items assigned
to the "Work Tasks" category is selected.
Solution:
This error indicates that the Gmail contact
contains a user defined field that overlaps
and/or conflicts with a standard field name
already used by an Outlook contact field.
For example, the field name "Account" is an
internally used Outlook field.
Solution:
The error "Missing Outlook ... folder
setting for ... mapping" indicates that one
of your gSyncit sync mappings is missing or
has an invalid Outlook folder selection.
Edit the appropriate sync mapping and
reselect your Outlook folder used for the
sync mapping.
Solution:
The error "Font ‘Arial’ does not support
style ‘Regular’" indicates that the standard
Windows 'Arial' font is missing from the
local system. To correct this issue you need
to repair your location Windows installation
or restore this font to the Windows
installed fonts list.
Solution:
The error
"The server threw an exception. (Exception from HRESULT:
0x80010105 (RPC_E_SERVERFAULT))" indicates
an internal Outlook error. This error might
indicate an issue with the Outlook .pst file
or an issue with the Outlook installation.
To resolve this issue try restarting Outlook or repairing your
Outlook .pst file using the "scanpst"
utility found in the Microsoft Office
program files directory.
Solution:
The error "Account disabled" indicates that
the specified Google account has be
disabled. You need to contact Google to
resolve this account related issue.
Solution:
After installing gSyncit if the gSyncit Outlook
add-in does not appear on the Outlook
add-ins list as inactive or disabled and
does not appear on the Outlook toolbar/ribbon
then this may indicate a registry permission
issue encountered during the installation of gSyncit.
When installing gSyncit the gSyncit Outlook
add-in is installed by writing several
entries to the windows registry. If there
are any permissions issues during the
installation these entries are not written
and the gSyncit add-in will not appear in
Outlook.
At the windows command line (run the cmd.exe
command in Windows) go to the gSyncit
program files directory (C:\Program Files\Fieldston
Software\gSyncit\) and run "regsvr32
gsyncit.addinshim.dll". If this returns an
error code like 0x8007005 you have a
registry permissions issue which is
preventing you from adding entries to the
windows registry.
To correct this issue we direct you to a
utility from tweaking.com to correct
registry permissions issues.
http://www.tweaking.com/content/page/reset_registry_permissions.html IMPORTANT: This solution involves
changes to your Windows registry to correct
a permissions issue with your baseWindows
installation. The steps are provided as-is
and performed at your own risk. You
can optionally choose to contact
Microsoft Support for assistance
correcting permissions issues with your
Windows registry.
Answer:
To sync Outlook tasks using the Franklin
Covey approach to prioritizing tasks you
simply prefix the Outlook task with a
priority identifier as follows...
{letter}{nummner}:{task subject}
For example, if you set the subject of your
Outlook task as "A1: Delivery TFP reports"
then this will sync with Pocket Informant
Online and set the "fcPriority" fields
available on your tasks. In the opposite
direction if the "fcPriority" field is
populated then gSyncit will automatically
assign this information to the task subject
field.
This approach only works when syncing using
the Pocket Informant Online service.