|
|
§
Device
Pack 2 New Feature List
o
Windows
Mobile 5 and Windows Mobile 6
§
Attachments will be downloaded immediately when “Mark
for Download” is selected. The message “download in progress…” will appear in
the status bar.
§
Emails will be sent immediately
once the user selects “Send”, if Live Connect is enabled.
§
Vista OS support for Desktop
Connector, Client Deployment Wizard, and Client Installer
§
Push notifications on the device
will occur for incoming inbox emails only (not calendar, contacts, tasks,
etc.).
§
Added support for syncing email
priority flags
o
Windows
Mobile 6
§
Viewing meeting attendee status
(accepted/tentative/declined and required/optional) with Exchange and Notes
§
Cradled device support (i.e., support with Desktop
Connector, Client Deployment Wizard, and Client Installer)
o
Symbian
OS 9
§
Canceled meeting requests (Nokia S60 3rd
Edition and UIQ3)
·
Email subject and icon reflects that the meeting
has been canceled
·
MRID and GUID information is hidden from the email
body when viewed on the device
·
Option to “Remove” cancelled meeting request from
the calendar
§
Rescheduled meeting requests (Nokia S60 3rd
Edition and UIQ3)
·
Email subject reflects meeting has been rescheduled
·
Options to Accept, Decline or Tentative accept
rescheduled meeting
·
Sync Meeting Request “Chair” and list of Attendees
to calendar but not Attendee status (UIQ3 only)
§
Add OneBridge Mail to list of application shortcuts
listed in “Active Stand-by Mode” if no conflicting Mail application is already
listed (Nokia Eseries)
§
Improved Inbox scrolling speed (Nokia 80 and Series
60 3rd Edition)
§
OneBridge client layout compatible with user
selected Nokia Series 60 3rd Edition themes
§
Meeting requests: syncing list of
meeting attendees to calendar (UIQ3 only)
§
Display the time of the meeting in
the body of all types of Notes meeting request emails (invitation, rescheduled,
canceled) in the device’s local time zone and not the server time zone (both
Eseries and UIQ3)
o
Palm OS
§
Display the time of the meeting in
the body of all types of Notes meeting request emails (invitation, rescheduled,
canceled) in the device’s local time zone and not the server time zone.
o
Live Connect usability and stability improvements
§
When coming out of flight mode
with Live Connect enabled, sync will be initiated immediately (Windows Mobile 5
and Windows
§
When going into flight mode, the
Live Connect icon will change immediately to disabled (Windows Mobile 5 and
Windows Mobile 6 devices).
§
The 5-minute Live Connect
green-to-red icon waiting period is now approximately one minute to quickly
adjust the Live Connect status (Windows Mobile and Palm OS devices)
o
Corporate Directory
§
Added support on Windows Mobile 5
Smartphone and Windows Mobile 6 Standard (formerly known as Windows Mobile 6
Smartphone) devices
§
Characters typed in new email
attendee list get imported into the Corporate Directory “Find” text box after
Corporate Directory is launched.
§
A new email “To”, “Cc”, or “Bcc”
field is automatically populated with the name selected from the list of names
after the user presses the center button or Select. Which recipient field (To,
Cc, or Bcc) gets populated depends upon which field was active when Corporate
Directory was launched.
NOTE: To apply a patch update, run the
Corporate Directory Wizard to copy the files automatically and distribute the
new software to users. Or, manually copy the updated files to the <Data
Folder>\User Data\Software Distribution\CorpDir folder from the <Program
Files>\OneBridge Sync Server\Bin\Clients\CorpDir\<platform> folder to
distribute the new software.
o
Mobile Data Suite
§
OneBridge client database sync support
with SQL Mobile database (only) on Windows Mobile 5 Smartphone and Windows
Mobile 6 Standard (formerly known as Windows Mobile 6 Smartphone)
§
Satellite Forms database sync
support for Windows Mobile 5 Pocket PC devices
§
UltraLite 10 support with Mobile
Objects
§
ASA 10 support with Mobile Objects
on Pocket PC devices
§
ASA 10 database sync support on
the server
o
Miscellaneous
§
Added battery efficient network
selection during OneBridge installation on selected HTC Windows Mobile devices
§
Disabled ActiveSync functionality
on Windows Mobile 5 and Windows Mobile 6 devices
·
This keeps ActiveSync from
actively trying to sync PIM databases while OneBridge is installed on the
device.
·
This disables older Windows Mobile
devices from doing over-the-air (OTA) syncs.
§
Clean and Maintain Users (CAMU)
utility
·
This utility was added to allow
administrators to remove users who have left the company, who are having Live
Connect issues and would like a fresh start, etc.
§
Documentation files have been
updated to provide additional details about the new features
§
Orange
clients for OneBridge and Corporate Directory
o
OneBridge
§
Clients are located in the following directories.
·
Clients\Orange\Windows Mobile\SETUP.ARM.CAB
·
Clients\Orange\Smartphone\SETUP.SPARM.CAB
NOTE: Client
Deployment Wizard (CDW) is not supported with this release.
o
Corporate
Directory
§
Using Corporate Directory Wizard with
·
In order to use the Corporate Directory Wizard with
Orange devices, you will need to update the following .CAB files with the
signed
·
Clients are located in the following directories.
NOTE: Corporate
Directory is not supported for Windows Mobile 2003 devices.
NOTE: Client
Deployment Wizard (CDW) is not supported with this release.
|
Signed |
Location used by Corporate
Directory Wizard |
|
Clients\Orange\Windows
Mobile\CorpDir.ARM.CAB |
Clients\CorpDir\Pocket
PC\WM5\ |
|
Clients\Orange\Windows
Mobile\moClientNet_PPC.arm.cab |
|
|
Clients\Orange\Windows
Mobile\CorpDir.ARM.CAB |
Clients\CorpDir\Pocket
PC\WM6\ |
|
Clients\Orange\Windows
Mobile\moClientNet_PPC.arm.cab |
|
|
Clients\Orange\Smartphone\CorpDirSP.ARM.CAB |
Clients\CorpDir\Smartphone\WM5\ |
|
Clients\Orange\Windows
Mobile\moClientNet_SPWM.arm.cab |
|
|
Clients\Orange\Smartphone\CorpDirSP.ARM.CAB |
Clients\CorpDir\Smartphone\WM6\ |
|
Clients\Orange\Windows
Mobile\moClientNet_SPWM.arm.cab |
NOTE: The
Clients directory can be found at \Program Files\Extended Systems\OneBridge
Sync Server\Bin\Clients
§
Multiple product improvements
§
Initial
support of Windows Mobile 6 with the T-Mobile Dash
OneBridge is now supported with
this updated client with wireless connectivity only.
§
Cingular
Blackjack added to the supported device list
§
Nokia
9300/9500 now support user signatures
§
Symbian
Device Pack new features
o
OneBridge
UIQ3 clients
§
OneBridge Mail Application
·
Improved management of meeting invitation requests
and rescheduled meeting requests
·
Easier downloading of truncated email messages and
attachments
·
Mark message as read/unread
·
“Get and send”
o
OneBridge
Live Connect Status and UIQ3 status bar integration
§
Visibility of Live Connect status at all times
§
Short cut to Live Connect Settings
§
Short cut to enable/disable Live Connect
§
“Sync now”
o
OneBridge
and UIQ3 “Today” screen integration
§
Notification of new email messages
§
Short cut to new email messages
o
Nokia
Series 60 3rd edition clients
§
Improvement to OneBridge Mail Application
§
Mark message as read/unread
§
Support for URL, phone number and email address hypertext
links
§
OneBridge Message Viewer
§
Improved message viewer scrolling speed
o
Client
Deployment Wizard for Symbian devices
§
Deployment of UIQ3 SIS files
§
Extraction of UIQ3 SIS files and Nokia S60 3rd
edition SIS files
§
Containing CUSTOMISED SETTINGS for OTA deployment
via, say, Web
§
Pacific,
Mountain, and
As of b5.5.2007.0307, updates
are included in the OneBridge patch to address the 2007 Daylight Saving Time (DST)
and time zone updates that affect the Pacific, Mountain, and Mexico Time Zones.
more…
§
Daylight
Saving Time and Time Zone Updates for 2007
As of b5.5.2007.0201, updates are included in the
OneBridge patch to address the 2007 Daylight Saving Time (DST) and time
zone updates for Microsoft Windows operating systems. more…
§
UltraLite
(version 9 and 10) data driver support
Pacific, Mountain, and Mexico Time Zone Updates
Daylight Saving Time and Time Zone Updates for 2007
Client Meeting Request
Functionality
Pacific,
Mountain, and
As of b5.5.2007.0307, updates are included in the
OneBridge patch to address the 2007 Daylight Saving Time (DST) and time zone
updates that affect the Pacific, Mountain, and Mexico Time Zones.
Following are general instructions to be followed:
§
Users should verify their time zone setting on the
device after upgrading.
§
CDW packages created with pre-5.5.2007.0201 and
5.5.2007.0201 should be rebuilt using the b5.5.2007.0307 patch or later.
§
The Admin group time zone selection should be
verified after upgrading.
Following are details about specific scenarios:
1.
Updating OneBridge from pre-5.5.2007.0201 to the
5.5.2007.0201 patch:
§
Mexican time zones (
§
All other time zones should work correctly for
CDW. Mexican time zones will not appear in the time zone list in CDW or Admin.
2.
Updating from pre-5.5.2007.0201 to the
5.5.2007.0307 patch:
§
Users in the Pacific and Mountain time zones must
manually change the time zone on the device. Until the device is manually
updated, Pacific users will run in the
§
Pre-5.5.2007.0201 CDW installations must be
recreated for Pacific and Mountain time zones. The CDW time zone needs to be
re-selected for Pacific and Mountain time zones. Otherwise, Mexican time zones
will be used by default for Pacific and Mountain time zones.
3.
Updating from pre-5.5.2007.0201 to the
5.5.2007.0201 to the 5.5.2007.0307 patch:
§
If the client was run using 5.5.2007.0201, the
Pacific and Mountain time zones should be correctly changed to the new time
zones.
§
CDW installations built with pre-5.5.2007.0201 or
5.5.2007.0201 for Pacific and Mountain should not be used and should be rebuilt
using 5.5.2007.0307.
For the
latest information about Microsoft updates and tools to address the 2007 DST
and time zone changes, please go to http://support.microsoft.com/kb/931836
Daylight Saving Time and Time Zone Updates for 2007
As of b5.5.2007.0201, updates are included in the
OneBridge patch to address the 2007 Daylight Saving Time (DST) and time
zone updates for Microsoft Windows operating systems.
Following is our recommendation for the order in
which to apply the OneBridge DST patch, Microsoft DST updates, Notes updates,
and mobile device updates. Please research the Microsoft and IBM DST web sites
mentioned later for information and specific details on applying the updates
and using the tools supplied by those vendors. Read through and understand all
steps before beginning, and follow these steps in this exact order to ensure
best chances of a successful upgrade.
1.
Apply
the OneBridge DST patch (b5.5.2007.0201 or later) to OneBridge servers,
adapters, and listeners.
Note: The OneBridge patch must be applied before
performing the steps below, otherwise if a OneBridge sync is performed after
Windows OS DST updates are in place but prior to the OneBridge patch being in
place, device calendar entries within the extended DST period may be off by one
hour.
2.
Apply
the Microsoft Windows OS DST update on the servers running the OneBridge
server, adapters, and listeners.
3.
In
OneBridge environments running against Exchange:
1.
Apply
the Microsoft Exchange CDO update on the server running the OneBridge Exchange
adapter/listener.
i.
iAnywhere
testing has found that if a previous version of CDO was installed via the
ExchangeMapiCdo.exe download, it must be uninstalled before the latest version
of CDO will successfully install (via ExchangeMapiCdo.exe)
ii.
A
bug exists in the version 06.05.7888 version of ExchangeMapiCdo.exe that may
cause OneBridge customers to receive an 0x8004011d error. Until Microsoft has a
fix for the bug, this problem can be worked around by replacing the v06.05.7888
of emsmdb32.dll with the older v06.05.7830 of that DLL. See OneBridge Knowledge
Base item 2943 for details (http://frontline.sybase.com/support/resolutionDetails.aspx?c=1&KBID=2943)
2.
Apply
the Microsoft Windows OS DST update on the server running Exchange. This update
is primarily needed for users running Outlook Web Access that are creating
calendar entries.
3.
Apply
the Microsoft Exchange update on the server running Exchange. This update is
primarily needed for users running Outlook Web Access that are creating
calendar entries.
4.
In
OneBridge environments running against Notes/Domino:
1.
Verify “UseNotesTimeZone = 1” is
NOT in the notes.ini file on the server running the OneBridge Notes adapter/listener.
2.
On
the server running Domino:
i.
Stop the Domino server
ii.
Apply
the Microsoft Windows OS DST update
iii.
Verify “UseNotesTimeZone = 1” is
NOT in the notes.ini file
iv.
Reboot
the server
v.
If there are iNotes or Domino Web Access users, apply
updates to the web access forms files by applying a Domino server fix pack or
manually making the edits. As of February 14, 2007, the fix packs are available
for Domino 7.0.1, 7.0.2, and 6.5.5. The fix for 6.5.4 is coming afterwards.
vi.
Run the applicable LotusScript agents to update the Domino
Web Access databases, the calendar and scheduling entries for users, and the
reservations and reservations database.
5.
Install
the updated OneBridge clients (b5.5.2007.0202 or later) to all devices
6.
Install
mobile device updates as provided OS vendors
1.
Deploy
the Microsoft Windows Mobile CAB that exists for Windows Mobile 2003 and
Windows Mobile 5 Pocket PC and Smartphone devices
2.
No
known Palm OS updates exist as of
3.
No
known Symbian OS updates exist as of
7.
In
OneBridge environments using Outlook on desktop PCs:
1.
Apply
the Microsoft Windows OS DST update to all PCs running Outlook. Note: Windows
2.
To
update existing calendar entries that are affected by the new DST rules:
i.
The
Exchange administrator should run the Microsoft Exchange Calendar Update Tool
(msextmz.exe) against the
Exchange server
ii.
Every
end-user should run the Time Zone Data Update Tool for Microsoft Office Outlook
(tzmove.exe) from each PC running Outlook
8.
In
OneBridge environments running Notes on desktop PCs:
1.
Apply the Microsoft Windows OS DST update to all PCs running
Notes. Note: Windows
2.
Reboot the PC
3.
Verify “UseNotesTimeZone = 1” is
NOT in the notes.ini file
4.
Run the applicable LotusScript agents that will update any existing Notes calendar
entries and resource reservations to conform to the new DST rules.
Following are additional important details
regarding the DST patches and updates:
1.
Calendaring
times shown on the device may be incorrect if the patches, updates, and
utilities discussed above are either not all run, or they are not run in the
order specified.
2.
In
order for Notes/Domino to work as expected, it is necessary for the operating
system to be restarted after the Microsoft Windows OS DST update has been
installed. The Notes client or Domino server should be shut down while the
Microsoft Windows OS DST update is being applied.
3.
At
this time, Microsoft has not made the Windows DST update available for Windows
2000 and older Windows operating systems. For those environments, Microsoft
provides the TZEdit.exe tool that can modify time zone DST rules. After running
the TZEdit.exe tool, the time zone must
be changed to a different time zone and then changed back to the correct time
zone in order for Windows to reset the current time zone to abide by
updated DST rules. From the Windows Taskbar, select Start -> Settings ->
Control Panel -> Date/Time -> Time Zone (tab) -> select another time
zone -> click Apply -> reset to your time one -> click Apply ->
click OK.
4.
After
installing the Microsoft update for Windows Mobile devices, the time zone must be changed to a
different time zone and then changed back to the correct time zone in order
for Windows Mobile to reset the current time zone to abide by the updated DST
rules:
a.
For
Pocket PC: Select Start -> Settings -> System tab -> Clock &
Alarms -> select another time zone -> select OK and Yes (to save it)
-> reselect your time zone -> select OK and Yes.
b.
For
Smartphone: Select Start -> Settings > Clock & Alarms -> Date and
Time -> select another time zone -> select Done (to save it) ->
reselect your time zone > select Done
For the
latest information about Microsoft updates and tools to address the 2007 DST
and time zone changes, please go to http://support.microsoft.com/gp/dst_overview
For the
latest information about Lotus Notes/Domino updates and agents to address the
2007 DST and time zone changes, please go to http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21254624
Client Meeting Request Functionality
The ability to enable or
disable client side creation of meeting requests/reschedules/cancellations has
been implemented.
Following are
instructions on how to implement for Exchange or Notes.
Exchange
To disable, add the following
setting to the exchangesettings.xml file in the OneBridge Sync Server\Bin
directory:
<EnableClientMeetings>false</EnableClientMeetings>
Notes
To disable, add the following
setting to the notessettings.xml file in the OneBridge Sync Server\Bin
directory:
<X_NotesEnableClientMeetings>false</X_NotesEnableClientMeetings>
The
patch installer requires that OneBridge be shutdown before applying the patch
in both single-node and multi-node configurations.
When using Advantage
Data Architect on a OneBridge server it is important not to recollate any
OneBridge tables to a different language. All tables must use Engl(Amer) as
their collation sequence. When installing Advantage Data Architect on a
OneBridge server, it is recommended that you update the adslocal.cfg file in
the installation directory to use "ANSI_CHAR_SET=Engl(Amer)". This
will avoid accidentally changing the collation sequence when viewing tables.
In some cases while
using Advantage Remote Server and after shutting down the OneBridge service,
the OneBridge tables will still be unavailable for exclusive access. In this
case you must restart the Advantage Remote Server to free the tables.
The dbupgrade.exe
program located in the OneBridge Bin folder can be used to upgrade OneBridge
tables. This program uses the upgrade functionality in upgrdhelper.dll. The
patch installer also uses upgrdhelper.dll to upgrade OneBridge tables. For
standard installations, the patch installer should perform all necessary table
upgrades. For cloned installations, the customer must run dbupgrade.exe on each
cloned installation. The command syntax in this case is dbupgrade.exe clone
"Bin-Path". DbUpgrade looks in the Bin folder for the exchange and
notes settings files to locate the data folder.
NOTE: Clone upgrades can't be performed while using ADS
remote server on the cloned node. Also, the table schema for cloned
installations is not currently verified.
The schema checker
validates that all OneBridge tables are configured properly. The schema checker
has been moved from the OneBridge service into the patch installer. If the
patch installer detects a schema issue, the tables are listed and the specific
issues are logged to the NT event log.
The Patch Delivery
installer does not support rollback. The
Remove option in the Windows Add/Remove programs applet will remove the entry
from Add/Remove programs, but should not change the installed file
versions. The Remove option is provided
only to allow this removal from Add/Remove programs if you are uninstalling
OneBridge or Client Deployment Wizard.
If you are uninstalling OneBridge or Client Deployment Wizard, you
should remove the Patch entry first, because it will report errors if you
attempt to remove it after the OneBridge or Client Deployment Wizard files are
removed. The current functionality
limits are due to Windows Installer limitations.
In the custom install,
the patch files are divided into installer features, described below, to allow
flexibility in applying the patch. For example, an administrator may choose to
patch the server software but to delay patching the client software until a
later date. In this case the
administrator can decline the installation of the Sync Server Device Files and
allow the installation of the Sync Server Files. At a later time, the patch can be run again,
this time choosing only the Sync Server Device Files. Likewise, an
administrator may wish to patch the Client Deployment Wizard on a server, but
not the Sync Server on the same machine.
In this case, the administrator can choose the Client Deployment Wizard
Server Files, but decline the Sync Server Files.
NOTE: The Patch Installer must be run
directly on the server or via VNC. Terminal Sessions are not currently
supported.
Sync Server Files
These are files used by the
running Synchronization Server. They are
typically installed under the OneBridge Sync Server \bin directory. If you are patching to fix a problem with the
Sync Server, you should install this feature.
Sync Server Device Files
These are files used by
clients of the synchronization server and do not actually run on the server;
they are mobile device-specific files.
They are typically installed under the OneBridge Sync Server\bin\clients
directory, and may be synchronized to client devices. If you are patching to fix a problem with
OneBridge client software, you should install this feature.
Client Deployment Wizard Server Files
These are files used by
the running Client Deployment Wizard.
They are typically installed under the OneBridge Client Wizard
directory. If you are patching to fix a
problem with the Client Deployment Wizard, you should install this feature.
Client Deployment Wizard Device Files
These are files packaged
for client devices by the Client Deployment Wizard and are not part of the
running Client Deployment Wizard application; they are mobile device-specific
files. They are typically installed
under the OneBridge Client Wizard\setup directory. These are typically the same set of files
that are included in the Sync Server Device Files feature, but are installed
under the Client Deployment Wizard product directory. If you are patching to fix a problem with
OneBridge client software, and use the Client Deployment Wizard, you should
install this feature.
| File Version | File Name | Date | Time | Size |
|---|
| 5.5.2007.0702 | ClientInstallRsrcEN.dll | 7/02/2007 | 7:02 | 323685 |
| 5.5.2007.0702 | ClientWiz.exe | 7/02/2007 | 7:02 | 843847 |
| 5.5.2007.0702 | ClientWizardRsrcEN.dll | 7/02/2007 | 7:02 | 307200 |
| 5.5.2007.0702 | InstallMon.exe | 7/02/2007 | 7:02 | 8248 |
| 5.5.2007.0702 | setup.exe | 7/02/2007 | 7:02 | 860160 |
| 5.5.2007.0702 | CorpDirSP.ARM.cab | 7/12/2007 | 9:24 | 355585 |
| 5.5.2007.0702 | moClientNet_SPWM.ARM.cab | 7/12/2007 | 9:26 | 578670 |
| 5.5.2007.0702 | setup.sparm.cab | 7/11/2007 | 9:32 | 1144981 |
| 5.5.2007.0702 | CorpDir.ARM.cab | 7/12/2007 | 9:24 | 358939 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.cab | 7/12/2007 | 9:25 | 600226 |
| 5.5.2007.0702 | setup.arm.cab | 7/11/2007 | 9:31 | 1052268 |
| 5.5.2007.0702 | MailPlus.prc | 7/02/2007 | 7:02 | 235528 |
| 5.5.2007.0702 | OBC.prc | 7/02/2007 | 7:02 | 1231427 |
| 5.5.2007.0702 | OBCPush.prc | 7/02/2007 | 7:02 | 129224 |
| 5.5.2007.0702 | setup.sparm.cab | 7/06/2007 | 12:19 | 1151137 |
| 5.5.2007.0702 | OneBridge.sis | 7/02/2007 | 7:02 | 652231 |
| 5.5.2007.0618 | OneBridge.sis | 7/04/2007 | 9:14 | 849820 |
| 5.5.2007.0702 | OneBridge.sis | 7/02/2007 | 7:02 | 800196 |
| 4.5.2006.0209 | OneBridge.sis | 3/15/2007 | 3:15 | 600585 |
| 5.5.2007.0702 | OneBridge.sis | 7/02/2007 | 7:02 | 673254 |
| 5.5.2007.0618 | OneBridge.sis | 7/04/2007 | 10:57 | 794008 |
| 5.5.2007.0315 | makekeys.exe | 3/15/2007 | 3:15 | 331776 |
| 5.5.2007.0315 | makesis.exe | 3/15/2007 | 3:15 | 712704 |
| 5.5.2007.0315 | signsis.exe | 3/15/2007 | 3:15 | 1200128 |
| 5.5.2007.0315 | untrusted.cer | 3/15/2007 | 3:15 | 1042 |
| 5.5.2007.0315 | untrusted.key | 3/15/2007 | 3:15 | 736 |
| 5.5.2007.0702 | setup.ARM.CAB | 7/02/2007 | 7:02 | 2536809 |
| 5.5.2007.0702 | ConnectApp.ini | 7/02/2007 | 7:02 | 343 |
| 5.5.2007.0702 | setup.arm.cab | 7/06/2007 | 12:23 | 2566849 |
| 5.5.2007.0702 | ConnectApp.ini | 7/02/2007 | 7:02 | 343 |
| 5.5.2007.0702 | setup.ARM.CAB | 7/06/2007 | 12:23 | 2566849 |
| 5.5.2007.0702 | CAMU.exe | 7/02/2007 | 7:02 | 36864 |
| 5.5.2007.0702 | CAMU.xml | 7/02/2007 | 7:02 | 23419 |
| 5.5.2007.0702 | clocksync.dll | 7/02/2007 | 7:02 | 151632 |
| 5.5.2007.0702 | config.dll | 7/02/2007 | 7:02 | 950346 |
| 5.5.2007.0702 | ConnectAdmin.exe | 7/02/2007 | 7:02 | 1937465 |
| 5.5.2007.0702 | CorpDir.BaseProvider.dll | 7/02/2007 | 7:02 | 28672 |
| 5.5.2007.0702 | CorpDir.Common.dll | 7/02/2007 | 7:02 | 36864 |
| 5.5.2007.0702 | CorpDir.dll | 7/02/2007 | 7:02 | 24576 |
| 5.5.2007.0702 | CorpDir.DominoProvider.dll | 7/02/2007 | 7:02 | 24576 |
| 5.5.2007.0702 | CorpDir.ExchangeProvider.dll | 7/02/2007 | 7:02 | 32768 |
| 5.5.2007.0702 | CorpDirDominoProviderHelper.dll | 7/02/2007 | 7:02 | 192512 |
| 5.5.2007.0702 | CustomPushListener.dll | 7/02/2007 | 7:02 | 512092 |
| 5.5.2007.0702 | DBAdapter.dll | 7/02/2007 | 7:02 | 1114174 |
| 5.5.2007.0702 | DBListener.dll | 7/02/2007 | 7:02 | 868428 |
| 5.5.2007.0702 | DBSyncActionPlugin.dll | 7/02/2007 | 7:02 | 1642496 |
| 5.5.2007.0702 | DBSyncWizardPlugin.dll | 7/02/2007 | 7:02 | 1712128 |
| 5.5.2007.0702 | DBtoPimProxy.dll | 7/02/2007 | 7:02 | 716800 |
| 5.5.2007.0702 | DesktopConnector.exe | 7/02/2007 | 7:02 | 323584 |
| 5.5.2007.0702 | DominoProviderSettings.xml | 7/02/2007 | 7:02 | 3821 |
| 5.5.2007.0702 | epocconv.dll | 7/02/2007 | 7:02 | 303202 |
| 5.5.2007.0702 | EpocFTConverter.dll | 7/02/2007 | 7:02 | 233582 |
| 5.5.2007.0702 | esisynceng.dll | 7/02/2007 | 7:02 | 1409100 |
| 5.5.2007.0702 | ExchangeAdapter.dll | 7/02/2007 | 7:02 | 1990730 |
| 5.5.2007.0702 | ExchangeListener.dll | 7/02/2007 | 7:02 | 2130004 |
| 5.5.2007.0702 | filetransfer.dll | 7/02/2007 | 7:02 | 286806 |
| 5.5.2007.0702 | httpcsync.dll | 7/02/2007 | 7:02 | 213068 |
| 5.5.2007.0702 | httpdsync.dll | 7/02/2007 | 7:02 | 753740 |
| 5.5.2007.0702 | licensemgr.dll | 7/02/2007 | 7:02 | 581706 |
| 5.5.2007.0702 | ListenerManager.dll | 7/02/2007 | 7:02 | 307286 |
| 5.5.2007.0702 | log.dll | 7/02/2007 | 7:02 | 561220 |
| 5.5.2007.0702 | logviewer.dll | 7/02/2007 | 7:02 | 225280 |
| 5.5.2007.0702 | MO.dll | 7/02/2007 | 7:02 | 1167420 |
| 5.5.2007.0702 | MonitorLib.dll | 7/02/2007 | 7:02 | 122880 |
| 5.5.2007.0702 | MsgOfTheDay.dll | 7/02/2007 | 7:02 | 163918 |
| 5.5.2007.0702 | NotesAdapter.dll | 7/10/2007 | 14:59 | 1691715 |
| 5.5.2007.0702 | NotesAddon.dll | 7/02/2007 | 7:02 | 159820 |
| 5.5.2007.0702 | NotesListener.dll | 7/02/2007 | 7:02 | 1044561 |
| 5.5.2007.0702 | nrecover.exe | 7/02/2007 | 7:02 | 127059 |
| 5.5.2007.0702 | nsession.dll | 7/02/2007 | 7:02 | 49224 |
| 5.5.2007.0702 | obrestart.exe | 7/02/2007 | 7:02 | 516169 |
| 5.5.2007.0702 | OneBridge.exe | 7/02/2007 | 7:02 | 315468 |
| 5.5.2007.0702 | palmconv.dll | 7/02/2007 | 7:02 | 303202 |
| 5.5.2007.0702 | PalmFTConverter.dll | 7/02/2007 | 7:02 | 241774 |
| 5.5.2007.0702 | playlistmgr.dll | 7/02/2007 | 7:02 | 315470 |
| 5.5.2007.0702 | printlog.exe | 7/02/2007 | 7:02 | 434264 |
| 5.5.2007.0702 | ProxySettings.exe | 7/02/2007 | 7:02 | 585728 |
| 5.5.2007.0702 | pushcfg.dll | 7/02/2007 | 7:02 | 475212 |
| 5.5.2007.0702 | pushmgr.dll | 7/02/2007 | 7:02 | 565324 |
| 5.5.2007.0702 | radiusacm.dll | 7/02/2007 | 7:02 | 639066 |
| 5.5.2007.0702 | router.dll | 7/02/2007 | 7:02 | 196668 |
| 5.5.2007.0702 | routercgi.exe | 7/02/2007 | 7:02 | 73814 |
| 5.5.2007.0702 | securidacm.dll | 7/02/2007 | 7:02 | 188508 |
| 5.5.2007.0702 | ServerIO.dll | 7/02/2007 | 7:02 | 327752 |
| 5.5.2007.0702 | ServiceMonitor.dll | 7/02/2007 | 7:02 | 254042 |
| 5.5.2007.0702 | SEventHandler.dll | 7/02/2007 | 7:02 | 553045 |
| 5.5.2007.0702 | SoftwareDistWizardPlugin.dll | 7/02/2007 | 7:02 | 741376 |
| 5.5.2007.0702 | SupportLib.dll | 7/02/2007 | 7:02 | 532555 |
| 5.5.2007.0702 | SupportLib.xml | 7/02/2007 | 7:02 | 5046 |
| 5.5.2007.0702 | SyncActionPlugin.dll | 7/02/2007 | 7:02 | 1503232 |
| 5.5.2007.0702 | tm.dll | 7/02/2007 | 7:02 | 847938 |
| 5.5.2007.0702 | Uninstall.exe | 7/02/2007 | 7:02 | 20480 |
| 5.5.2007.0702 | UpgrdHelper.dll | 7/02/2007 | 7:02 | 458752 |
| 5.5.2007.0702 | xcsmmc.dll | 7/02/2007 | 7:02 | 540672 |
| 5.5.2007.0307 | MobileDeviceInfo.dll | 3/07/2007 | 3:07 | 163928 |
| 5.5.2007.0307 | ServiceControl.dll | 12/04/2006 | 12:02 | 20480 |
| 5.5.2006.1217 | exchangeacm.dll | 12/18/2006 | 12:17 | 516190 |
| 5.5.2006.1217 | HttpSettings.exe | 12/18/2006 | 12:17 | 704512 |
| 5.5.2006.1202 | LDAPAuthPlugin.dll | 12/04/2006 | 12:02 | 528467 |
| 5.5.2007.0702 | DataConv.dll | 7/02/2007 | 7:02 | 381018 |
| 5.5.2007.0702 | ErcnConv.dll | 7/02/2007 | 7:02 | 340058 |
| 5.5.2007.0702 | Nokia6021Conv.dll | 7/02/2007 | 7:02 | 364644 |
| 5.5.2007.0702 | Nokia6230iConv.dll | 7/02/2007 | 7:02 | 364646 |
| 5.5.2007.0702 | Nokia6600Conv.dll | 7/02/2007 | 7:02 | 331776 |
| 5.5.2007.0702 | Nokia6800Conv.dll | 7/02/2007 | 7:02 | 340068 |
| 5.5.2007.0702 | Nokia6810Conv.dll | 7/02/2007 | 7:02 | 249856 |
| 5.5.2007.0702 | Nokia7250iConv.dll | 7/02/2007 | 7:02 | 253952 |
| 5.5.2007.0702 | Nokia7610Conv.dll | 7/02/2007 | 7:02 | 335872 |
| 5.5.2007.0702 | NokiaConv.dll | 7/02/2007 | 7:02 | 340060 |
| 5.5.2007.0702 | SeK700iConv.dll | 7/02/2007 | 7:02 | 344160 |
| 5.5.2007.0702 | SeK750iConv.dll | 7/02/2007 | 7:02 | 364640 |
| 5.5.2007.0702 | SeK800iConv.dll | 7/02/2007 | 7:02 | 364640 |
| 5.5.2007.0702 | SiemensConv.dll | 7/02/2007 | 7:02 | 340064 |
| 5.5.2007.0702 | SiemensSx1Conv.dll | 7/02/2007 | 7:02 | 344166 |
| 5.5.2007.0702 | SyncML.dll | 7/02/2007 | 7:02 | 987204 |
| 5.5.2007.0702 | MobileDataDrivers.dat | 7/02/2007 | 7:02 | 24277 |
| 5.5.2007.0702 | MonitorLib.dll | 7/02/2007 | 7:02 | 122880 |
| 5.5.2007.0702 | WindowsClient.exe | 7/02/2007 | 7:02 | 2326604 |
| 5.5.2007.0307 | XDBOleCE.dll | 3/07/2007 | 3:07 | 197632 |
| 5.5.2007.0201 | XDBULTRALITE9.dll | 1/29/2007 | 2:01 | 160080 |
| 5.5.2007.0201 | XDBULTRALITE10.dll | 1/29/2007 | 2:01 | 163840 |
| 5.5.2007.0702 | XDBSatForms7PDB.dll | 7/03/2007 | 10:42 | 127536 |
| 5.5.2007.0307 | XDBOleCE.dll | 3/13/2007 | 9:29 | 200760 |
| 5.5.2007.0202 | XDBULTRALITE9.dll | 2/02/2007 | 17:09 | 161848 |
| 5.5.2007.0202 | XDBULTRALITE10.dll | 2/02/2007 | 17:11 | 166968 |
| 5.5.2007.0702 | XDBDB2ECE.dll | 7/03/2007 | 10:44 | 40496 |
| 5.5.2007.0702 | XDBObjectStore.dll | 7/03/2007 | 10:44 | 27184 |
| 5.5.2007.0307 | XDBOleCE.dll | 3/13/2007 | 9:29 | 200760 |
| 5.5.2007.0202 | XDBULTRALITE9.dll | 2/02/2007 | 17:09 | 161848 |
| 5.5.2007.0202 | XDBULTRALITE10.dll | 2/02/2007 | 17:11 | 166968 |
| 5.5.2007.0307 | XDBSatForms.prc | 3/07/2007 | 3:07 | 12574 |
| 5.5.2007.0702 | MOCF20Client.dll | 7/02/2007 | 7:02 | 178688 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.CAB | 7/02/2007 | 7:02 | 1503834 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.ini | 7/02/2007 | 7:02 | 160 |
| 5.5.2007.0329 | MOCFClient.dll | 3/29/2007 | 3:29 | 212992 |
| 5.5.2007.0702 | MOCF20Client.dll | 7/03/2007 | 11:11 | 181808 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.CAB | 7/03/2007 | 13:40 | 1522398 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.ini | 7/02/2007 | 7:02 | 160 |
| 5.5.2007.0329 | MOCFClient.dll | 3/29/2007 | 3:29 | 216128 |
| 5.5.2007.0702 | MOCF20Client.dll | 7/03/2007 | 11:11 | 181808 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.CAB | 7/03/2007 | 13:40 | 1522398 |
| 5.5.2007.0702 | moClientNet_PPC.ARM.ini | 7/02/2007 | 7:02 | 160 |
| 5.5.2007.0702 | moClientNet_SPWM.ARM.CAB | 7/03/2007 | 13:33 | 583168 |
| 5.5.2007.0329 | moClientNet_SP2003.ARM.CAB | 3/29/2007 | 3:29 | 1040357 |
| 5.5.2007.0329 | moClientNetSP.dll | 3/29/2007 | 3:29 | 138304 |
| 5.5.2007.0702 | MOFX20WinClient.dll | 7/02/2007 | 7:02 | 188416 |
| 5.5.2007.0702 | MOWinClient.dll | 7/02/2007 | 7:02 | 208896 |
| 5.5.2007.0702 | TravelerLib.dll | 7/02/2007 | 7:02 | 86016 |
| 5.5.2007.0329 | moClientLib.dll | 3/29/2007 | 3:29 | 905216 |
| 5.5.2007.0307 | com_extendedsys_mo.cod | 3/07/2007 | 3:07 | 63424 |
| 5.5.2007.0307 | com_extendedsys_mo.debug | 3/07/2007 | 3:07 | 200918 |
| 5.5.2007.0307 | com_extendedsys_mo.jad | 3/07/2007 | 3:07 | 606 |
| 5.5.2007.0307 | com_extendedsys_mo.jar | 3/07/2007 | 3:07 | 100700 |
| 5.5.2007.0307 | com_extendedsys_mo_liveconnect.cod | 3/07/2007 | 3:07 | 13188 |
| 5.5.2007.0307 | com_extendedsys_mo_liveconnect.debug | 3/07/2007 | 3:07 | 36468 |
| 5.5.2007.0307 | com_extendedsys_mo_liveconnect.jad | 3/07/2007 | 3:07 | 670 |
| 5.5.2007.0307 | com_extendedsys_mo_liveconnect.jar | 3/07/2007 | 3:07 | 22756 |
| 5.5.2007.0702 | contents.txt | 7/02/2007 | 7:02 | 861 |
| 5.5.2007.0702 | errors.h | 7/02/2007 | 7:02 | 5697 |
| 5.5.2007.0702 | OBSyncTest.sfa | 7/02/2007 | 7:02 | 5072 |
| 5.5.2007.0702 | ReadMe.txt | 7/02/2007 | 7:02 | 3406 |
| 5.5.2007.0702 | SatFormsSyncAgent.cpp | 7/02/2007 | 7:02 | 16790 |
| 5.5.2007.0702 | SatFormsSyncAgent.vcproj | 7/02/2007 | 7:02 | 5705 |
| 5.5.2007.0702 | stdafx.cpp | 7/02/2007 | 7:02 | 308 |
| 5.5.2007.0702 | stdafx.h | 7/02/2007 | 7:02 | 1366 |
| 5.5.2007.0702 | DBName10.db | 7/02/2007 | 7:02 | 1916928 |
| 5.5.2007.0702 | MOCFClient_ASA.dll | 7/03/2007 | 10:45 | 19504 |
| 5.5.2007.0702 | DBName10.db | 7/02/2007 | 7:02 | 1916928 |
| 5.5.2007.0702 | MOFXClient_ASA.dll | 7/02/2007 | 7:02 | 28672 |
| 5.5.2007.0702 | DBName.db | 7/02/2007 | 7:02 | 1356800 |
| 5.5.2007.0702 | SyncLog.db | 7/02/2007 | 7:02 | 1356800 |
| 5.5.2007.0702 | DBName.db | 7/02/2007 | 7:02 | 1356800 |
| 5.5.2007.0702 | MOCFClient_ASA.dll | 7/03/2007 | 10:45 | 18992 |
| 5.5.2007.0702 | DBName.db | 7/02/2007 | 7:02 | 1361920 |
| 5.5.2007.0702 | MOFXClient_ASA.dll | 7/02/2007 | 7:02 | 28672 |
| 5.5.2007.0702 | MOFXClient_ACCESS.dll | 7/02/2007 | 7:02 | 28672 |
| 5.5.2007.0702 | MOFXClient_MSSQL.dll | 7/02/2007 | 7:02 | 24576 |
| 5.5.2007.0702 | MOCFClient_SQLCE.dll | 7/03/2007 | 10:46 | 18992 |
| 5.5.2007.0702 | MOCFClient_UL.dll | 7/03/2007 | 10:46 | 23088 |
| 5.5.2007.0702 | CorpDir.ARM.CAB | 7/10/2007 | 15:30 | 898125 |
| 5.5.2007.0702 | CorpDir.ARM.CAB | 7/10/2007 | 15:17 | 941997 |
| 5.5.2007.0702 | CorpDir.ARM.CAB | 7/10/2007 | 15:17 | 941997 |
| 5.5.2007.0702 | CorpDir.ARM.ini | 7/02/2007 | 7:02 | 128 |
| 5.5.2007.0702 | CorpDirSP.ARM.CAB | 7/10/2007 | 15:18 | 361356 |
| 5.5.2007.0702 | CorpDirSP.ARM.ini | 7/02/2007 | 7:02 | 136 |
| 5.5.2007.0702 | moClientNet_SPWM.ARM.ini | 7/02/2007 | 7:02 | 164 |
| 5.5.2007.0702 | NETCFv2.wm.armv4i.cab | 6/26/2006 | 11:51 | 2222897 |
| 5.5.2007.0702 | NETCFv2.wm.armv4i.ini | 9/29/2006 | 14:56 | 152 |
| 5.5.2007.0702 | CorpDirSP.ARM.CAB | 7/10/2007 | 15:18 | 361356 |
| 5.5.2007.0702 | CorpDirSP.ARM.ini | 7/02/2007 | 7:02 | 136 |
| 5.5.2007.0702 | moClientNet_SPWM.ARM.ini | 7/02/2007 | 7:02 | 164 |
| 5.5.2007.0702 | Admin.chm | 7/02/2007 | 7:02 | 7917701 |
| 5.5.2007.0702 | ClientWiz.chm | 7/02/2007 | 7:02 | 2534080 |
| 5.5.2007.0702 | Getting Started Guide Administrator.pdf | 7/02/2007 | 7:02 | 479677 |
| 5.5.2007.0702 | Getting Started Guide End User.pdf | 7/02/2007 | 7:02 | 230846 |
| 5.5.2007.0702 | MobileClient.chm | 7/02/2007 | 7:02 | 1774091 |
| 5.5.2007.0702 | MobileDataSuite.chm | 7/02/2007 | 7:02 | 4265247 |
| 5.5.2007.0702 | OneBridge Clean and Maintain Users (CAMU).pdf | 7/02/2007 | 7:02 | 79561 |
| 5.5.2007.0702 | WindowsClient.chm | 7/02/2007 | 7:02 | 743891 |
The About box was brought to the foreground so it can be dismissed.
A close message is sent to the application before starting the uninstall process.
This fix is specific to HTC devices. The client install
now specifically checks for the presence of the HTC.home.xml file and if it’s
present, it parses the file for the HTC home screen plug-in that causes the
problem. If it’s found, the install will replace the HTC plug-in with a
standard Microsoft plug-in and save the screen to a renamed file. The new home
screen title will have "(w/
The Mail key on the side of the device is now mapped to the OneBridge transport.
Pre-WM6.0 devices do not have a field to support optional
invitees for meetings. The client was modified to not display or modify the
optional invitees since they are not supported by these devices. Additionally
support for the optional invitee field has been added for WM6.0 devices.
The time zone code was modified to default to a time zone with at least the correct bias if it’s unable to find an actual match.
The "ReplyTo" field is now set with the current user info when forwarding on the device.
The Pocket PC and Windows Mobile clients were modified to only show the Windows hourglass when the client is in the foreground.
Menus are now only added if the main dialog is visible.
IM field support was added to the data store file.
A more detailed error message is now displayed if the
connection fails very early in the connection process. The user will check if the
offline profile is selected or the device is in flight mode.
Separate Live Connect updates were made that addressed
this issue so that Live Connect now recovers after being disabled due to the
battery level.
For Pocket PC and Smartphone, the push client was never allowing the device to sleep if the device was in always-on mode for Live Connect. Now the client allows the device to go to sleep according to the device power settings when the device is out of coverage.
Dynamic battery change detection was added for PocketPC
and Smartphone to force push to disable when battery is too low
There were two problems encountered with older
Palm devices. The first was an error when opening MailPlus that caused the
device to reset. The second was an error when replying to an email. Both issues
have been addressed.
HTC S620 device has a landscape screen. All controls in that dialog now fit into the different device screen, including the scroll bar.
The U.S. Central time zone and Mexico Central time zone
are now distinguished in the time zone index code.
The server name is now resolved prior to opening
tables in InitializeAdvantage at OneBridge server startup.
The data directory was modified to match Pocket PC
(<AppPath>\Data).
Corporate Directory was modified to work with usernames
longer than 32 digits.
A periodic socket "keep alive" is sent
during lengthy client side processing.
Updates were made to the Symbian calendar adapter to
synchronize the meeting chair, required/optional attendees and their statuses
from the server to the device's calendar. This code is used for all Symbian OS 9
devices, but only UIQ3 devices currently display meeting request attendee
information, and even they do not display status information.
Modifications were made to move subfolder mail on the
device into the subfolder on the server.
Modifications were made to the function for converting time
for EKA2 devices when saving the sent time.
The center button of the Navi Key will display the recipient
list when selected in the To field.
Modifications were made to have initial sync run after
clear all settings.
The defect was caused by the call to GetSubDirs. This added the root folder to the list of subdirectories as well as the contained subdirectory folder tree. The net result was that the root folder was included in the list twice. This had the effect of making the client think that the server was instructing the client to EXCLUDE all files in the root folder. The fix was to replace the unconditional addition of the root folder to the folder list with a conditional such that it is only added IF GetSubDirs is not called.
Corner case found where code path caused the service to stop. Issue has now been fixed.
In 5.5, database sync contract info is stored in configstore xml file. When OneBridge server config changed, the Mobile Objects client will delete the existing config store xml file and create a new one. As a result, it removes all the contract info and lead a initial sync for all contracts.
With the Mobile Objects re-factoring, the contract info is no longer stored in configstore.xml. All database types use a shared xml file to store syncinfo data.
The language code was hard-coded to "EN" in the Palm Mobile Info Adapter. The fix was made to get the device's configured language and report that in the Mobile Info action.
When the Mobile Objects connection object tries to connect to the server, it is first checking whether another instance is already connected to server.
For Symbian devices, the subfolders checkbox in the Inbox Filtering options dialog is how hidden, since this feature is not available.
Modifications were made to not re-encrypt a password that is already encrypted.
The OneBridge MTM client code was updated to use 'From' address for Inbox items.
The record is set as private only if the status in the calendar entry is private.
Changes were made in Monitor to report a failure if it can’t contact the Monitor agent.
During an initial sync if there is no current mailbox assigned to the active standby screen, OneBridge is now added as an inbox folder to the active standby screen. There is also a new setting in the OneBridge email settings accessed via the MTM that enables the user to easily switch the OneBridge inbox folder on in the active standby screen.
When the xml file is being read from the server to get the table field definitions, an attempt is made to allocate an array of the field definition structures that is larger than a hard coded limit for dynamic allocations. The memory needed is allocated in the Data Manager heap rather than the dynamic Memory Manager heap.
The item is now left in the change log until the outbox item is deleted from the folder. The push change detection code has also been modified so that if there is any item in the change log it will trigger one push on that item.
This scenario happens when the service restart routine took awhile. A deadlock case was removed.
Palm devices were allowed to go into deep sleep, which can cause the data channel to pause for wireless synchronization. This behavior only manifested with large datasets. Code has been added to support staying in REM sleep during synchronization. This allows the device to shut off the screen and go into partial sleep while still processing data.
Various optimizations were made to speed up loading of OneBridge MTM, including only loading bitmap images on demand (subsequently cached).
The data type mapping has been modified.
All dialog and container code has been updated to set the item list in the right place and handle size change events appropriately.
Optimizations were made to improve scrolling.
A correction was made for a missing parameter used in
creation of the response e-mail.
The definition of the issue is if an email
address returned from the m_NotesApi.GetStringField() call was actually a
string of email addresses (probably either ';' or ',' delimited), and the
string was greater than 512 characters long, memory could be overwritten and
cause a crash or other strange behavior. This was fixed by guaranteeing that
the list that is processed only has one email address per element.
A check was put in place to assure that the new e-mail message can be fully created.
A check is now in place to verify to eliminate the cause of the error.
A change was made to the client proxy code to check for an
active sync session before attempting to start a 'Sync Now' session.
The decision was made to limit the number of UI change.
The assumption is port 80 if 443 is returned from discovery and assume port
5001 if port 6001 is returned. Also,
references to Port were changed to be
The errors were fixed from parsing the SQL
statement. The change was made by mo.dll sending the table schema to the device
even if the SQL statement is used to create client side table.
A change has been made so the described screen no longer displays.
Forwarded POP3 e-mail from the device sent to the wrong address will now send the return e-mail back to the actual sender.
Reading and writing Notes recurring all day events were changed to handle the time zone properly when the target client is in different time zone than the one adapter is running on.
Sync server only allows each device has one session to connect to server, in order to let a device accept and ACK the push notification while a sync is in progress, mo application need to set the device id to a different value when sending requests to server, so that, although the requests are from the same device, sync server will regard these requests are from the different devices.
The fix is to set the Notes field "ExcludeFromView" to include the Drafts folder for the return receipt. This prevents the extra copies from being generated.
1. Wrap ASA mo db sync in transaction
2. Replace raw SQL statement calls with SQL parameter binding
3. Replace dataadapter with datareader and resultset to avoid load all records into memory when detecting client side update
4. Change the obguid column type from char(32) to BigInt, (only apply to init sync)
5. Fire MoConnection status events only if status message changed or a predefined interval reached
6. Change the way in SQL for finding deleted records to avoid sub queries. (Replace "not exist" with "left outer join")
The OneBridge status screen has been modified to indicate the proper mode.
The UI has been modified to allow the letters to display correctly.
The UI has been modified to allow the letters to display correctly.
The code to look up GMT -3
Recurring appointment expansion and time adjustment logic is changed to work correctly if one of the target time zones is from the southern hemisphere. (In southern hemisphere the DST start time in a year is greater than DST end time.)
DB settings in the preferences dialog have now been implemented.
Device side modifications will now sync if a soft reset has been done before the next sync.
PushMgr startup code was fixed to protect the internal variable.
The code now looks to see which browsers are installed and uses the best one for the device. File changed: OBMsgViewAppUi.cpp.
This file has now been added into the .cab file.
Updated the EPOC client mail adapter to recognize cancelled meeting requests and set a bit in iMtmData2 field of message's TMsvEntry.
Added distinctive icons for cancelled meeting requests (in all possible states) to Series 80, S60 3rd edition and UIQ 3 MTMs. Updated MTM UI data implementations of ContextIconL() method to choose the new icons when the relevant iMtmData2 bit is set.
Change was to save the value of the field and re-populate it after a buffer resize.
The problem was that MailPlus did not correctly handle emails with the format "name" <email> where there is a space between the closing " and the < characters. Code has been added to handle this scenario.
Now OneBridge honors the skip and report error vs. skip file transfer drop down box within the file transfer config. Implemented for backup, restore, copy, and install. Other actions (i.e. move, delete, etc) were tested and either already worked or did not have an applicable need.
The Symbian push engine used to loop and check whether the PushsettingsDB had been created and Live Connect registered. It now registers for a notification of changes to the PushSettingsDB and then checks the state of the database when a change has been made. This means the ActiveScheduler is started straight away in the push engine and other observers that are not directly linked to push registration e.g. Pointsec observer can be started before Live Connect registration has been run.
Files changed: XCEPushMgr.cpp/.h, PushStartup.cpp/.h, XCEPush.cpp, XCEPush.mmp
The SyncStatusView is now initialized when the application
is started. This prevents the screen from being blanked out during a sync.
Time zone modifications for new Daylight Saving Time
support have now been fully propagated into the client install.
The problem was caused by how the Smart Text Engine was used. Updates were made to the initialization code and rendering code. This eliminated the cause of the problem, which was improper initialization of the STE. A secondary benefit of this change is that the screen flicker that was visible in the MailPlus List View Preview Field when navigating is eliminated.
Nokia Series 80 OneBridge client now uses LafEnv::GetDefaultPath() API to retrieve localized default root documents folder to report back to OneBridge server for its substitution of %FT_DOCSPATH%.
The problem was caused by how events were passed to the Smart Text Engine regardless of whether the Preview field was visible. The right combination of events seemed to trigger a reset. The fix was to not allow events to be processed by the Smart Text Engine when the Preview field is closed.
The fix was to directly copy the subject text for the e-mail message editor/viewer from the iDescription field of the entry rather than recalculating it.
Symbian OS 9 devices seem to have a Asia/Hong Kong time zone rule with zero start and end dates. The zero dates caused us to ignore the rule. The fix (to \Pioneer\PLATFORM\EPOC\timeFunctions.cpp) uses the rule as a fallback if no rule is found with a valid start/end date.
RunFormula function was fixed to return proper error code after NotesAPI call fails.
There are cases where perfmon tests fail and then succeed later. This is one case where a success email was being sent. Also, Live Connect end-to-end tests were doing a similar thing. For perfmon a notification will never be sent for a success or a failure. For Live Connect end-to-end test a notification will be sent for success and failure based upon configuration.
The OneBridge e-mail viewer application now opens most attachment types as embedded applications. This conforms to preferred S60 practice and works better with the E50's QuickOffice application. SIS files are opened in the Installer application non-embedded - Attempting to run the Installer embedded causes OneBridge upgrades to fail since the installation attempts to kill the e-mail viewer and hence the embedded installer.
We now use the ConvertUTCTTimeToECDateTime function for EKA2 devices when saving the sent time.
We now handle the Nav button for the To field. It will now display recipient list when selected.
S60 3rd edition MTM: Copy e-mail header details from
temporary stub e-mail given to e-mail editor before it gets deleted.
Root Key:
HKEY_LOCAL_MACHINE
Sub Key:
Software\Extended Systems\AppReg\Gen
Value:
ImmediateDisconnect
Data Type:
DWORD
Data Value:
1
Behavior:
Setting ImmediateDisconnect equal to 1 closes the connection immediately, if the value is missing or has a value not equal to 1, the connection is cached and not closed immediately.
Comments:
It is not recommended to use Live Connect (Always On Mode) in an environment where the connection is closed immediately.
The order of the entries in the package file has been changed so that the recognizer does not try to start push prior to push being installed.
An issue with CE db API change handling was addressed.
The OneBridge sync server only allows each device to have one session to connect to the serve. In order to let a device accept and acknowledge the push notification while a sync is in progress, a Mobile Objects application needs to set the device ID to a different value when sending requests to the server, so that, although the requests are from the same device, the sync server will regard these requests from the different devices.
When the connection manager establishes connection, some
devices and carriers may return a connection status that has not seen before,
plus, some new connection status codes were introduced in the Window Mobile 5.0
SDK. This fix handles the new status code properly when establishing a
connection.
The problem was that the names of the groupware actions were hard coded in the preferences dialog. Because of this, it would fail to find the corresponding configuration and would not display the changed name. The code was modified to use the Contract Type field rather than the Display Name to find the correct configuration. the display code was also changed to load the configured name rather than the hard coded default.
A code change was made to initialize the buffer length to
0 when a corresponding value is pointer is freed.
The custom DLL was added for Nokia 6230i SyncML support.
In order have the sync engine convert zero length strings to
NULLs you need to set/add the following to your registry:
This was happening by default from 5.0.2006.0818 through
5.0.2007.0302. Depending on the customer’s setup, they may or
may not want this
functionality. Starting with 5.0.2007.0330, default behavior will be to not do
any conversion. Default behavior after this change is to not manipulate empty
strings in the sync engine.
HKLM\Software\Extended Systems\OneBridge Sync Server\Sync:
(DWORD)ConvertZeroLengthStringsToNULLs = 1
All email items are now deleted from the inbox, outbox, and sent items folder on uninstall of OneBridge. This results in the email notification getting deleted by the system.
Now the code will attempt the registry update up to 15
times before reporting the failure alert. Also, a discrepancy was found with
the error messages for CE and Smartphone setup messages. A duplicate message
was removed.
The problem is that the folder delete operation in syncs
is not supported. Due to the subfolder implementation in v5.5, it is now
feasible to allow this type of “not found” error to be ignored, since the list
of subfolders is gathered from the server, and the user is presented with this
list which includes checkboxes to select them.
The code is using the function AknsUtils instead of AknIconUtils to create the logo bitmap (and mask). This also has the effect of rendering the logo with smoothed edges.
Calls to COBMtmUi::EditL() on a message now create a new message from scratch (complete with signature) rather than editing the totally empty message provided by the calling framework. Note that this should not break editing an existing message because that uses the COBMtmUi::OpenL() call - not COBMtmUi::EditL().
The exception dates array is now only set if it contains 1
or more entries.
When trying to delete the db sync tables sometimes the delete would fail. The index file deletions would succeed. Later this would cause an issue when trying to create the tables, and the tables already existed. Delete error was 32 - file in use. A retry was added on deletions.
Due to the way fields were set in the PocketPC calendar fields,
a corner case bug was being his in POOM/Mapi API. When Notes reminders were
synced, the Start Time and End Time were set as the same value. For some
reason, this was causing that buggy behavior. It is now changed so that Start
time and Duration are set (=0). This works correctly.
Additional CDO array elements were added to support new time zones.
The implementation of SoftReset()has been updated to use a different API on Nokia S60 2nd and 3rd edition devices.
A different kind dialog is used to display the invalid server message. This seems to result in the screen redrawing itself correctly.
Signature support was ported from Symbian OS 9 to Series
80.
The implementation of GetAttachmentInfo() in
AttTruncGenerator.cpp does not process such malformed meta text well. The
example given causes an attempt to allocate a large number (0xfffffff6) of
bytes of memory - which fails.
HandleForegroundEventL function was added to the message watcher application.
The OneBridge client now re-queries the OS for time zone information at the beginning of each sync.
We now check the state of the Pointsec application via publish and subscribe values when we are attempting to restart the Calendar observer in the PimMonitor. If the device is in the locked state the observer start request is ignored.
Added additional safeguards in the Notes adapter to check for invalid meeting requests sent from the device.
1. Ignore any requests where the chair is also an attendee.
2. Ignore any requests where a matching record GUID is found when the device is indicating a new meeting record should be created.
§
17043 Extended sessions never
appear to expire
The extended sessions had a concept of extended
authentication as well. The extended authentication implementation had an issue
which could potentially never expire authentication results under certain
conditions. This is fixed. Additionally, when a wrong password is used, the
previous successful authentication cached results are expired. Next time when
the user tries with correct password, a new authentication will be carried out
instead of using cached information.
The Symbian data store was updated to use FLDID_PHONE_CAR instead of FLDID_PHONE_WORK2.
The command name was abbreviated from "Yes to All" to "Yes - All". This now allows space for 3 buttons in the dialog.
SVG icons used by OneBridge MTM Message Editor (OBMsgEd) and Viewer (OBMsgVw) were changed.
Predictive text entry support for signature text field was
enabled.
The custom DLL was added for Nokia 6021 SyncML support.
The OneBridge Message Editor has been given a new UID (0x200072B3 instead of 0x20001D6B).
The Embedded MTM component has been renamed from "OneBridge" to "OneBridge Mail" to visibly distinguish it from the OneBridge client application in the Uninstall screen. Unfortunately, this has the side effect of preventing upgrades from previous UIQ3 MTM versions (in the field to beta customers). Beta customers will need to uninstall their OneBridge client before installing this release version.
Buffer now works for Unicode and non-Unicode data.
For ASA 9 CE database, EBF rev3396 has broken the function of MO database sync. Changes were also made on the server side (DBAdapter.dll).
Iterate through other device configured connection if admin configured connection does not connect.
OneBridge now uses the new commsdat API to extract the group information from the AccessPointGroup table. OneBridge passes an object of type TCommSnapPref to the RConnection::Start().
OneBridge now clears down the iMailPreview flag when it handles an UPDATE_UI event that doesn't contain any info. This means OneBridge can end normally on the LAST_UI event when running a filtered mail sync.
OneBridge was reading a 2 byte value for the image size out of the pdb record into a signed 4 byte variable. The problem is that this value was read into the upper 2 bytes of the variable and we were attempting to right shift the value into the bottom 2 bytes. The error is that the right shift was back-filling the upper bytes with 1's. This results in a hugely negative number. We now read the value into an unsigned 16-bit variable then copy this to the 32-bit signed variable. This way we don't have to mess with right shifting the value to get it in the right place.
File transfer of certain .prc files could hang when the version info was being examined.
Field data is written differently for exceptions.
OneBridge now checks whether the moRequestResponse object is null before sending any error information to client. If it is null, then only log the error on server side.
Merge data during every database initial sync if admin has
set "Data merge" option and if
"MergeOnSubsequentDBInitialSync" registry value is set to 1.
OneBridge now sends the device ID from proxy to server
when the socket goes bad. The proxy did not have access to TM session ID for
Live Connect sessions.
On UIQ3 OneBridge now skips any %PREF field mappings so
that we still get an exact match when mapping the VCard mappings to the
OneBridge fields.
The compact call has been removed on the contacts database for UIQ3 devices. The contacts application itself should compact the database during normal operation.
The “To” field is now displayed in the sent list view.
WriteDeviceData capability was added to XCEPush and PIMMonitor exes.
When the dialog appears by opening the flip, the dialog is canceled and the current sync session is immediately terminated. This allows the user to enter the correct credentials and retry the sync manually.
Observe when Live Connect triggered that OneBridge credentials dialog is brought to the foreground obscuring the active phone call UI.
The fix is to handle both PersPager (Home Cell) and
CarPhone (
Changes are limited to
The subfolder index was incorrectly calculated and
accidentally always changed the subfolder to the first subfolder category. It
didn't matter what the name of the subfolder was; just the order in the index.
Subfolder changes in 5.5 were failing, because an additional filter field was mistakenly being added to the filters array.
The problem was fixed by searching for the End-Of-Line
character on each device platform. Since each filename is listed in the
email body on a separate line, this made the most sense. Once the end of
the line is found, the logic is to navigate back to the start of the file size
string to get the complete filename.
A database access contention was fixed.
ObjectGroup.expandGroup API made a copy of a record when the API was used. A manual copy was also being made of the record. This has been fixed.
Corruption to the playlist has been resolved.
The GPF has been fixed. The Log Viewer has minor changes. The tags notifications (and all other notifications) are now viewable within the log viewer.
Implemented and optimized the
COBMsgTextBodyControl::CEditor::Draw() method.
Fix time zone droplists in Admin,
CDW, and Client Installer by inserting two new time zones (new Pacific and new
Mountain)
User confirmation was added to disable all ports code.
The error is logged if the tag
data is not supplied in the URL argument. Also an error is sent in the response
back to the caller.
Access to a null pointer has been
fixed.
The merge checkbox was incorrectly
set to true regardless of the contract setting.
Change to httpdsync.cpp, parsing change for httpconfig.xml and change to how many threads and protocol server objects are used.
Update the time zone table and
Palm specific TZ display code for
Windows Mobile 5 devices can now
do authentication
New restart behavior:
- This behavior is based on "No Restart" value under registry
key HKEY_LOCAL_MACHINE\Software\Extended Systems\OneBridge Sync Server\Server
- If "No Restart" value doesn't exist then service must be
restarted (for backward compatibility)
- If "No Restart" value exists and it has a value of 0 then
restart the service
- If "No Restart" value exists and it has a value of 1 then do
not restart the service
§
16291 Autostart not working on
later UIQ3 devices
Build change to work for new ROM
updated devices.
The problem was that Outlook 2000
and 2003 require the appointment item to be updated in order for the changes to
take effect.
Issues have been addressed for
support of SyncML on the Sony Ericsson K800i.
The problem is that the Motorola Q is listening on an unexpected IP address. To solve this OneBridge now broadcasts on 255.255.255.255. The downside of this is that the broadcast also goes out over the NIC card. It will not go past the local router, and Smartphone devices do not connect directly to an Ethernet connection. Also note that the RNDIS miniport adapter only allows one device to be addressed to it at a time.
The password was removed from the
network config trace log.
When a request is cancelled or the
client side timeout happens, MO SDK will first call CancelRequest to close the
current socket and open a new socket for the following request, so that the
remaining response from the cancelled request will not go into the new
request.
Changes were made to resolve to
the SMTP address for attendees not found in the Notes GAL.
§
16471 GSM Connection is not
working with Symbian Devices
Missing check was causing the
connection to drop.
This fix involved adding data to some fields that Notes expected to be filled out in order to process the cancellation message.
The problem was that we were
clearing the "Remove record after successful sync" value regardless
of whether it was legal or not. I
changed the logic to allow this value to remain selected in the case described,
One-way client to server syncs, and cleared it for all others.
Smartphone can now use special
OneBridge transport to enhance email.
See
the complete details listed above.
§
UltraLite (version 9 and 10) data
driver support
See new documentation included in
the patch installer located after installation on
\Extended Systems\OneBridge Sync
Server\Docs\Windows Mobile UltraLite Data Drivers.pdf
<b5.5.2006.1217>
The reachable state has a tolerance of
150 seconds before switching states.
Fix for first part requires removing unwanted logging to event log.
Instructions: Apply the OneBridge 5.5 patch. Run the monitor agent service in the OneBridge server machine with “service account” (instead of “local system account”). Basically monitor agent service should be run with same account as OneBridge service.
The PPC cab files were changed to
have the option to skip the transport installation and subsequent deletion of
inbox items. This functionality can be invoked by adding the described
registry key to the device before the cab installation. If this setting
is not on the device, there should be no changes in cab file installation.
Notes cannot parse bad characters
(tab delimiters in this case) out of email addresses. When we called
another Notes API to resolve this email to a user is when the server crashes.
Transport was added for Windows Mobile
5.0 Smartphone. For Smartphone 2003, there is still a problem. In the CE Setup
DLL, a call is made to DMProcessConfigXML (in aygshell.dll) to process the
provisioning doc. This works fine with the test app or stand-alone exe, but
when run from the CAB file (wceload), the call is infinitely blocked. Thus far
have not been able to determine what the cause of this is.
Code was disabled that regenerates
NodeUniqueID when the specific attribute is not found. In this case the new
XCSID_ScriptFile tag was added in 4.5 and not found in 4.2 or earlier
configurations which caused the NodeUniqueID to get regenerated and cause
configuration issues.
On Pocket PC installs, dialog boxes called “Installation” are now detected and destroyed so that additional software distribution actions or file transfers with installations can now be subsequently installed.
A fix was made to the Admin group
properties, CDW, Client Install, and Palm time zone form to not display that
last two entries in the time zone table which are special cases.
A fix was made to the ECDateTime class
to handle the timepart and datepart separation correctly.
Security Manager uses the registry key
to save the data fading flag. The OneBridge client was modified to read it from
registry and remove it as it's done.
Previous bug 23900 rolled forward to
v5.5.
An extra timestamp was removed from the
RouteTimes field when responding to meeting requests. This brings the OneBridge
client behavior inline with the Notes client functionality.
The registry value was changed to
OBC_DisablePartership. A fix was applied to the corner case when the OneBridge
client is actively running in the background and the user unlocks the device.
A fix was applied to the upgrade code to
only rebuild the folder list when upgrading from preference version 3 and 4.
Release 5.5 uses preference version 5.
A failure was occurring after the
mail had sent, and the client didn’t receive a message to delete the item from
the outbox.
Relative to the path for the install,
the client could hang. This issue has been addressed.