Funambol Clients Interoperability

From Sw

Jump to: navigation, search

Contents

[edit] Only 7.0.* Clients Are Supported

Please do not use any other Funambol client. All Funambol clients have bugs (as does all software) but the 7.0.* client bugs are known and worked around. If you don't follow this advice you will lose data.

You can find 7.0.* clients in the Configuration And Basic Usage section: http://wiki.scheduleworld.com/wiki/

[edit] Time Zone Problems

It's possible that your sync will create events that start at the wrong time. This can happen if there is a time zone mismatch. You need to make sure the following timezones are all the same:

  1. Microsoft Windows time zone.
  2. ScheduleWorld general preferences time zone - found on the [preferences] page.
  3. ScheduleWorld device-specific preferences time zone. You can find this by going to the [preferences page] and clicking the 'Edit Settings' button next to your Funambol client.

Making sure all of these are the same will ensure a consistent correct behaviour.

[edit] Windows 98, 2000, ME Specific Time Zone Problems

Windows XP and Vista receive the new time zone definitions during the Windows update procedure. Unfortunately 98, 2000 and ME do not. There is an unofficial time zone update program you can use to fix this problem found here.

[edit] Conflicting redmption.dll Files

If you have an older conflicting redemption.dll on your computer you will have timezone and many other problems. Follow these steps to determine if you have this problem and resolve it:

  1. search C:\ for the file: redemption.dll
  2. if there is more than one you have a problem and you need to uninstall or update the application that installed the older DLL. Google desktop search is often the source of this problem - so is other synchronization software or any Outlook add-ons/extensions.

[edit] Google Desktop

  1. Remove the Funambol 7.x SyncML Client for Outlook.
  2. Install Google Desktop.
  3. Re-install the Funambol 7.x SyncML Client for Outlook.

This will help you avoid error codes 502 / 183 (which you will see in the log files).

[edit] Recover Mode Problems

Sometimes the Funambol 'recover' mode (from ScheduleWorld, replace Outlook data) doesn't properly delete items in Outlook and replace them with data from ScheduleWorld. If this is happening to you you'll see a few recurring events are not appearing on their start date, but every instance after that looks fine.

To guarantee a perfect recover sync follow these steps:

  1. delete all items in Outlook. For example, if you are recovering calendar events, you don't have to delete your Outlook contacts just your Outlook events. The category view works best for this as this view allows you to bulk select and delete events.
  2. perform a recover sync.

[edit] Summer Time / Daylight Savings Events or Todos (Tasks) Off By One Hour

If your events or todos (tasks) have their start/end times wrong by the daylight savings offset (usually one hour) you can fix this by enabling the 'Ignores DST' option like this:

  1. Go to the ScheduleWorld preferences page (you may be asked to log in).
  2. Click 'Edit Settings' for your Funambol client device.
  3. Enable 'Ignores DST' and click 'Save'.

[edit] Second Tuesday and Thursday Event Syncs Correctly

You can have:

  1. yearly events that specify a particular month and (first/second/third/fourth) week day.
  2. monthly events that specify a (first/second/third/fourth) week day.
  3. weekly events that can specify up to 7 days of the week.

All of these sync perfectly and have no issues with time zones.

[edit] Wacky Categories Issue

It is easy to mistake the Outlook Event 'Label' setting as the category setting. The real categories are found at the bottom of the window.

Further, some localized versions of Outlook translate 'Label' into 'Category' which is doubly confusing.

saintgermain (ScheduleWorld forums) posted this neat tip on how to assign categories to labels:

http://www.uwec.edu/help/Outlook03/CAL-color.htm

Original post: http://www.scheduleworld.com/jforum/posts/list/783.page

[edit] Broken Proxy Compression

Funambol compression mechanism is based on the exchange of standard HTTP headers (Accept-Encoding, Content-Encoding, Uncompressed-Content-Length), as it is recently specified by OMA. For more information you can refer to the Funambol DS Server Architecture Design Document, par. 1.2.1.

It's been reported that, on some network, the compressed stream is corrupted when received by the client. That has been verified with some operator using a WAP gateway, while it works with a web connection.

Since version 6.5 of the Funambol clients, in case of error during the decompression of the data, the sync is automatically retried with compression disabled. This is transparent to the user, apart the loss of performance.

[edit] Broken Recurrence Exceptions

Funambol 6.x clients now can support EXDATEs. For example, you have swimming lessons every Saturday at 10:00AM _except_ for next Saturday.

However, 6.x clients badly break iCalendar RecurrenceId support. For example, you have swimming lessons every Saturday at 10:00AM _except_ next Saturday is at 11:00AM. The Funambol Outlook client will delete the 'next Saturday' instance using an EXDATE, then create a copy of the event and change the start date to 11:00AM.

This is bad because now the new event does not have a link to the original. You can no longer delete all occurrences of your swimming lessons in one operation. Also, this scheme makes it impossible to use the Funambol client to interoperate correctly with any other scheduling server in this regard. This means that servers that have the capability of properly handling recurring instances changing properties will not (and can not) sync the data properly into Outlook when the Funambol Outlook client is used.

[edit] COM Pointer Errors

There seems to be a number of possible causes and solutions for this. Ultimately they all seem to boil down to a corrupted Outlook PST file, or something is interfering with access to the PST file (via the redemption.dll).

[edit] Possible Solutions

  1. You have a corrupt Outlook PST file. Simply use Outlook to repair the PST file.
  2. This might be an issue with the older redemption.dll. If so, installing the newer DLL should resolve this. Some instructions about this can be found on the Outlook (Configuration) page.
  3. One person reported that they had contacts in the calendar folder. Once they fixed this the problem went away.
  4. Another person reported that this was caused by having nested folders. Once they stopped doing that this problem went away.
  5. It's been reported that the Funambol client may fail after creating a recurring event exception. The solution here was to delete the newly created recurrence exception(s) (leaving the original recurring event alone) and then sync again.
  6. Another person reported that the solution was to uninstall the Funambol client, then re-install it again.
  7. Re-install Office 2003. One person reported that their .pst file was corrupted. Unfortunately it seems the .pst file could not be repaired while Office SP3 was installed so the only option was to re-install.
  8. It seems the Google desktop search is conflicting and uninstalling and re-installing Google desktop search resolves the issue. More info here: http://forge.objectweb.org/tracker/index.php?func=detail&aid=308658&group_id=96&atid=100096.
  9. A message posted to the Funambol mailing list might provide some help:
Probably it's a specific Windows update (KB939683, for Window Media 11 http://support.microsoft.com/kb/939683) that is causing the COM pointer error. Some other users have experienced the same issue after installing this Windows update patch... it seems breaking the Outlook API. Unfortunately so far we didn't have much time to investigate on it, I'll let you know for updates. You could try to uninstall KB939683, then Outlook plugin should work again.

[edit] Outlook 2007 Notes Fail To Sync (Color / Categories)

Microsoft changed Color to Categories. Funambol mentions they have fixed this and the next client version will have the fix: http://forge.objectweb.org/tracker/index.php?func=detail&aid=307104&group_id=96&atid=100096

[edit] Outlook 2007 Duplicates or Strange Behaviour

A number of fixes are in the latest redemption.dll for Outlook 2007. You'll have to download the new redemption.dll from here: http://www.dimastr.com/redemption/Redemption.zip and replace your existing redemption.dll.

You should be able to find your existing redemption.dll by right-clicking on your computer's C:\ drive and using the 'Search' feature.


[edit] Redemption License Popups

dubwise posted in the forums a solution that worked for him: http://www.scheduleworld.com/jforum/posts/list/91.page

In a nutshell, the issue seems to be that you have multiple copies of the redemption.dll on your system. It doesn't matter if they are used with other applications. The solution seems to be just to delete them all and install the latest redemption.dll.

[edit] Howto Enable Logging

Type this from the BlackBerry home screen (not from the Funambol client)

alt + lglg

Using this global event log can help a lot with debugging sync problems using the Funambol client.

[edit] Encryption Is Not Supported

If you enable the encryption option of the Funambol client you will not be able to sync.

[edit] Item #0 in folder "Calendar" is not a appointment item.

If your syncs are failing and you notice this log statement in your Funambol client logs:

Item #0 in folder "Calendar" is not a appointment item. Please check if Outlook is working properly.

then the following may help:

  1. Ensure that you are syncing an Outlook folder that only contains calendar events.
  2. Remember that sub-folders are included in the sync by default. You must disable this if you have sub-folders that contain non-event items.

The Funambol clients have a panel that allows you to adjust both of the above. You can find it in the Funambol client under Tools -> Options -> click the 'Details' button across from Calendar.

[edit] Changing The Device ID

If you run multiple instances of the Funambol client in copies of the same virtual machine then both Funambol instances will have the same Device ID - which will not work correctly if you are also using the same user name. To change the Device ID into something else you can use regedit and modify the devID value found with the key:

HKEY_CURRENT_USER\Software\Funambol\OutlookClient\spds\syncml\DevInfo

[edit] General Funambol Configuration Settings

Funambol clients come configured correctly except for the URL, username and password.

  • URL - http://sync.scheduleworld.com/funambol/ds
  • username - This is your ScheduleWorld account ID (number). You must not use your email address. Your ScheduleWorld account ID was emailed to you when you signed up, and can also be found on your preferences page (General Preferences for <account ID>). You need to log in to see this page.
  • password - the same password you use to login to the ScheduleWorld web site.

The following settings are the default settings:

  • contacts URI - scard
  • calendar event URI - scal
  • calendar todo/task URI - stask
  • notes - snote
  • encryption - no
  • v-card - no
  • i-cal no

Please do not set the scheduler to sync more often than once every 30 minutes. This helps keep the load on the server down.


[edit] Funambol 3.x

Works with Windows 2000 and Outlook 2000.

  • Warning this version can not be used to sync more than one computer with the same username. For example, if you want to keep your work and home machine in sync you must use a different username on each machine. This means signing up for two separate ScheduleWorld accounts, and then sharing your calendar between the two users.
Personal tools
Advertisement
Advertisement