Meeting Maker Synchronization
From Provider Wiki
Windows Mobile 5.0 and Intellisync
Windows Mobile 5 devices require Active Sync 4.x and higher to sync with desktop machines. Microsoft has made significant changes to this version, and as a result this version is NOT compatible with the current version of Intellisync for Meeting Maker. Users of the newer devices (such as the Dell X51v) may get the following error message when attempting to sync:
Unable to find required program module (DLL)
The current workaround is to use Intellisync to sync with Outlook, then use Active Sync to sync the Windows Mobile Device. Please see the instructions here for specific steps.
This article will be updated as more information becomes available
--Bob DeSilets 09:26, 12 January 2006 (EST)
Pocket PC or Outlook and Intellisync
The first time you synchronize with Meeting Maker 8.5 using Intellisync for Meeting Maker, it may take an hour or more to complete the synchronization process (depending on the size of your calendar) as it builds an index file for the Meeting Maker calendar (regardless of the number of days selected). The progress window may appear to have frozen, and the Windows Task Manager will list the Intellisync application as Not Responging. This is normal behavior. Subsequent synchronizations appear to proceed much faster (within 5 min). Bob DeSilets
Troubleshooting Intellisync connection
If you suspect that there is a problem connecting to the Intellisync servlet, you can verify that the connection is valid by putting the URL of the servlet into a web browser. If you do not recall what the IP address of your Intellisync servelet is, you can find out by going to:
Control Panel --> Add/Remove Programs --> Intellisync for meetingmaker Configuration Wizard
Click "Change/Remove" and select "Reconfigure" when prompted. Copy the entire url, and be sure to note the port number that your application uses to connect to the server. You will need to append this information manually into your browser. For example, if your application is configured as follows:
Then you would place the following url in your browser:
http://server ip address here:8080/is4mm/is4mm
You should get a response from the server with today's date and time as well as the message "Intellisync for MeetingMaker Servlet". If your browser query does not return a result, then there may be a problem on the server side. Contact your server administrator for additional assistance.
One way syncing does not function as expected
From Meeting Maker KNOWLEDGE BASE ARTICLE #3106
TOPIC: Desktop overwrite Handheld or Handheld Overwrites Desktop does not overwrite data PRODUCT: Meeting Maker - LAST UPDATED: 04/01/2003 - VERSIONS: 6.x - current PLATFORM: All Platforms - CATEGORY: PDA's Palm - ARTICLE TYPE: Tech Note
Problem: When syncing with a Palm PDA, setting the Meeting Maker conduits to "Desktop overwrite Handheld" or "Handheld Overwrites Desktop" never overwrites any data.
Explanation: What will happen is that the data will only sync in one direction.
- In the case of "Desktop overwrite Handheld", data will only sync from Meeting Maker to the Palm PDA, adding to data that is already on the Palm PDA.
- In the case of "Handheld Overwrites Desktop", data will only sync from the Palm PDA to Meeting Maker, adding to the data that is already in Meeting Maker.
- Additionally, if you set a one way sync for the very first time you sync your Palm PDA, the ID files that are created on the Palm PDA will only reference the data in one direction and not reference all data for a proper full sync. This means if you choose to set the conduit to "synchronize" later on, you could potentially duplicate or lose data.
Always set the conduits to synchronize on the first sync.
Hotsync Crashes when using Palm Desktop 4.1.4
KNOWLEDGE BASE ARTICLE #2797 TOPIC: Hotsync crashes when using Palm Desktop 4.1.4 PRODUCT: Meeting Maker - LAST UPDATED: 10/26/2004 - VERSIONS: 6.x - 8.x PLATFORM: Win All - CATEGORY: PDA's Palm - ARTICLE TYPE: Tech Note
Up until Palm Desktop 4.1.4, all versions of the Palm desktop installed to the c:\Program Files\Palm or c:\Palm directory. A new install of Palm Desktop 4.1.4 installs to c:\Program Files\palmone. If you upgraded from palm Desktop 4.0 or higher then you would still be installed to c:\Program Files\Palm and would experience no issues with Palm Desktop 4.1.4.
If you have done a fresh install of Palm Desktop 4.1.4, you should either:
- Rename the c:\Program Files\palmone to c:\Program Files\Palm
- Right click the Hotsync manager and select Custom
- Go to the Meeting Maker Datebook and add your Meeting Maker password.
- Rename the c:\Program Files\palm directory back to c:\Program Files\palmone
OR
- simply reinstall Palm Desktop 4.1.4 to c:\Program Files\Palm and reinstall the Meeting Make Client to install the conduits if necessary.
log4cplus error in log file
KNOWLEDGE BASE ARTICLE #3192 TOPIC: log4cplus error when syncing with a Palm PDA PRODUCT: Meeting Maker - LAST UPDATED: 12/02/2005 - VERSIONS: 8.x - 8.5.x PLATFORM: All Platforms - CATEGORY: PDA's Palm - ARTICLE TYPE: Tech Note
You may receive a log4cplus error when syncing with your Palm device if your device is low on memory or your hard drive is running low on space. The temporary files that get created during the syncing process are not able to complete or get created. You must make additional room on your PDA or desktop computer's hard drive.
Preventing Duplications on Palm OS devices
from: Meeting Maker Palm Sync FAQ's
Error Code 0x30 – 0x3c
- These error codes are caused by problems with the id file. The id files are used to keep track of what has been transferred between the PDA and Meeting Maker. Corruption in these files can cause duplicate entries, bad syncing, and a host of other problems. The most reliable fix is a hard reset on the PDA. A third party file level tool for the PDA can be used to remove the individual id files. Make sure to clear the database on the PDA associated with the id file otherwise duplication will occur.
Double Modify Error, Mac and Windows
- A Double Modify refers to a condition in which an entry was modified differently on both the Palm Handheld Device and in the Meeting Maker Client. When a HotSync Action is performed, the HotSync Log will report a Double Modify. The entry that was "double modified" will appear to be duplicated. Each "duplicate" entry contains one of the modifications. The duplicate entries are actually different
Duplicate Entries, Mac and Windows
- In certain situations, a user will get duplicate entries in either Meeting Maker, on the Palm, or in both. The duplicates are caused by the id files getting out of sync with the data being transferred. The easiest solution is to remove the duplicates from Meeting Maker, clear the id files, do a hard reset on the Palm, and then sync wih Meeting Maker.
Other ways to prevent duplication:
- If a user moves up to a later version of the conduit(s) without removing the ID files associated with each conduit and/or doing a reset on the Palm, or tries to synchronize the Palm with multiple computers they may get duplicate meetings, addresses, or todo's on thier Palm devices. The user documentation states that the user should not do this. If a Palm device is synchronized to computer 1, ID files are created on that computer to map events. If the same Palm is synchronized to PC2 (the one without .ID files mapping events), all items are considered new. All items are now duplicated because the first time synchronization process on PC2 creates new set of unique IDs, that are different from the IDs that already exist on the Palm.
- If you change the computer from which you are synchronizing Meeting Maker and the Palm devices you must delete the .id files and perform a hard reset on the Palm Device.
Removing Duplicate Entries from Palm device
Legacy information on Meeting Maker's support page indicates that you should use DBCleaner and/or DBManager to clean out the individual databases on the Palm OS unit. These utilities are no longer available for download. Our suggesion is to use Undupe by Stevens Creek Software. This $10 piece of software does what it advertises, and is more than worth the minimal cost.
Meeting Maker and new Palm OS pdas
Overview:
Newer Palm OS pdas like the Tungsten T5, T3, E, Treo 650s, and Zire 31 will intermittently fail when syncing large amounts of data. This is due to the newer memory and OS architecture of these devices not being 100% backward compatible with older 3rd party Palm conduits. Recently Palm has released OS patches for many of these pdas to help with this problem.
What to do:
Before calling Meeting Maker support make sure that you have downloaded and installed the latest update for your Palm pdas OS. The patches are available at:
http://www.palm.com/us/support/downloads/
This seems to fix the issues with most Tungstons. for Treos:
Limit the date range in the Meeting Maker datebook as much as you can, never use ALL for a date range.
Unfortunately most of the time once this error occurs, syncing again may not happen until you do a hard reset of the device. After the hard reset, you should be able to sync if you have now limited the data that can sync ans updated the Palm.
Palm is still working on this issue.
Synchronizing Two Calendars to One Palm
As a proof of concept, two Meeting Maker calendars synched to one Palm device. Two different Palm calendar applications are used to view the calendars on the Palm.
- One Meeting Maker calendar synchronized to the built-in Palm Date Book via the Meeting Maker DateBook conduit.
- The second Meeting Maker calendar synchronized to the Palm through a two step process - Meeting Maker synchronized via Intellisync for Meeting Maker to Outlook; Outlook synchronized to a third party calendar application installed on the Palm via that application's calendar conduit. KeyDates from Chapura is the third party application used for this test.
BlackBerry
For calendaring options, there are a couple of scenarios we explored with version 8.5 of Meeting Maker:
1. User who wants to use Outlook as their calendar front end:
- requires installation of Meeting Maker Outlook Connector (MMCO) and BlackBerry desktop. This will allow
Outlook to act as the user's Meeting Maker front end.
- Flow of information: MeetingMaker --> MMCO --> Outlook --> BlackBerry Desktop --> BlackBerry
2. User who want to use Meeting Maker as their calendar front end:
- Requires installation of IntelliSync for Meeting Maker
- Flow of information: MeetingMaker --> IntelliSync for MeetingMaker --> BlackBerry Desktop (v. 4.0.0) -->
BlackBerry.
- For later models of BlackBerry, such as the 7130, which are more fully supported in later versions of the
BlackBerry Desktop it appears that you need to decide which is more important, MeetingMaker or such
functionality as adding and removing applications via BlackBerry Desktop Manager. Versions of the
BlackBerry Desktop Manager later than 4.0.0 do not support this version of Intellisync.
Currently there isn't a way for us to wirelessly synchronize a user's calendar with a BlackBerry device. Perhaps after RIM and PumaTech settle their legal dispute, IntelliSync Mobility Suite (IMS) will support wireless MeetingMaker (8.5) synchronization, but we don't know how that is going to shake out.
NOTE: If you do use MMCO with Outlook, do not use any other method of accessing your Meeting Maker calendar. From the People Cube knowledge base:
IMPORTANT NOTE: Do not use any other Meeting Maker client to make any changes, such as the native client, the HTML client, etc. It is highly recommended that none of your proxies have read-write access to your calendar. If you use the MMCO client and you or a proxy makes changes to your calendar from another Meeting Maker client, unpredictable behavior will occur.
This statement from the MMCO readme appears to be regarding synchronization timing. Both the HTML client and the MMCO client update with a synchronization. The native client is designed to be a "real time" client. The risk's include double booking, decline/accept confusion, etc...
Meeting Maker Connector for Outlook (MMCO)
For users that would like to use their Outlook 2003/2007 calendar as a front-end for Meeting Maker, there is a Meeting Maker Connector for Outlook plug-in available. This will allow users to manually synchronize their Meeting Maker calendar with Outlook, but will not allow for full Meeting Maker functionality (such as proposing meetings). Please contact lan@isc.upenn.edu for more information about this product.
MMCO troubleshooting
If MMCO will not enable for some reason after installation, the following steps have proven helpful:
- Start Outlook
- Go to Menu-->Help
- Select About Microsoft Office
- Select Disabled Items
- Enable the MMCO COM add in
That should take care of it.
Macintosh Issues
***THIS TIP IS NOW OBSOLETE WITH THE UPGRADE TO MEETING MAKER 8.5***
Norton AntiVirus 9.x interferes with the 7.2.1 Meeting Maker synchronization process on Mac OS 10.3x. The only current solution is to disable NAV to allow synchronization to complete. We will be testing NAV 10 to see if the problem has been addressed in the later version.--Bob D. 13:57, 14 Jun 2005 (EDT)
