Pre-ReleaseNotification of new iAnywhere Mobile Office iPhone Client

 

iAnywhereMobile Office 5.7 (5.7.2010.0714) EBF Release for iPhone

The latestiAnywhere Mobile Office iPhone clienthas been submitted to the App Store.

 

What'sNew?

 

MobileOffice databases moved to Caches folder

Mobile Office now stores itsunderlying encrypted databases in the Caches folder rather than the Documentsfolder. This enhances security as this folder is not backed up by iTunes.During an upgrade installation to this newer Mobile Office client, if databasesused by the previous version of the Mobile Office client exist in the Documentsfolder, they will get seamlessly moved to the Caches folder.

 

iPhoneiOS 4.0 support

There are issues that have beenfixed that were discovered when running the Mobile Office client on an iPhone4, iPhone 3GS, iPhone 3G, and second- and third-generation iPod touch updatedwith iOS 4.0.

 

iPadsupported in compatibility mode

The iPad is now officiallysupported with the Mobile Office client running in compatibility mode.

 

This EBF will generally becomeavailable on the App Store as early as 3 days and up to 3 weeks after ithas been submitted. 

 

Published by michael Auerbach 

Hot Fixes: 65AfariaFx49.exe - Afaria 6.5 Server Feature Pack 2 System
Hot Fixes Release Version: 6.50.4698.0
July 14, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support   

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.5 server and are experiencing the following issue:

• Encountered timeouts on file transfers containing many files (using wildcards) at 8 minutes. [REF 33925*]

Rolled Hot Fix Information: NA

Affected Client Types: Java Clients

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 65AfariaFx49.exe-Apply this Hot Fix to an Afaria 6.5 Feature Pack 2 Server system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site at http://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy the Hot Fix file, 65AfariaFx49.exe to temporary directory on the hard drive. Browse to the temporary directory and run the Hot Fix file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Notes - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

• This hot fix goes on a system with Afaria 6.5 Feature Pack 2 already installed on it.

Known Issues - NA

Uninstalling the Hot Fixes

This function is not present in this hot fix.

What the Hot Fix Provides

Afaria Server

<Afaria Server>\ClientESD\Java
06/28/2010 11:19 AM 323,537 Afaria.jar
05/24/2010 04:07 PM 8,998 ResourceStrings.properties

<Afaria Server>\ClientInstall\Java
06/28/2010 11:19 AM 358,400 JavaClient.tar

Published by Michael Auerbach 

Hot Fixes: 65AfariaFx45.exe - Afaria 6.5 Feature Pack 2 Administrator System
Hot Fixes Release Version: 6.50.4693.0
July 13, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support  

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.5 and are experiencing the following issues:

• When using a MfE task to apply settings to an E72 device and specifying the Access Point as ‘DM Account Activation IAP’, the MfE settings failed to deploy with a failure to find ServerId target. [REF 33603*]

• OMA DM SCM task failed to deploy software on subsequent connections, if the session did not succeed on the first connection. [REF 33638*]

Rolled Hot Fix Information: NA

Affected Client Types:

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 65AfariaFx45.exe-Apply this Hot Fix to an Afaria 6.5 Feature Pack 2 Administrator system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site at http://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy these files, 65AfariaFx45.exe to a temporary directory on the hard drive. Browse to the temporary directory and run this file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Notes - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

• This hot fix is to be installed on a Afaria 6.5 Feature Pack 2 system.

Known Issue - NA

Uninstalling the Hot Fixes

This functionality is not present in these hotfix.

What the Hot Fix Provides

Afaria Administrator

<Afaria Administrator>\Client-bin
06/10/2010 07:10 PM 401,408 PolicyOmaDM.dll

Published by Michael Auerbach 

Hot Fixes: 65AfariaFx50Svr.exe and 65AfariaFx50Admin.exe - Afaria 6.5 Feature Pack 2 Administrator and Server System
Hot Fixes Release Version: 6.50.4700.0
July 8, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support  
 

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.5 and are experiencing the following issues:

• On a Afaria 6.5 Feature Pack 2 system, when launching the Afaria Administrator link for a Slave server from the Master server, when the Afaria Administrator was installed on the Afaria master server, and both servers were defined in Access policies; the error message, “an unrecoverable error has occurred”, was encountered. [REF 33770*]

• Afaria Administrator unable to add any Replication (Slave) Servers to Access Policies when servers were in a Windows WORKGROUP configuration. Only the server that resided on the same machine as the Afaria Administrator installation could be added. [REF 33948*]

• New properties and methods were added to the API’s for creating iPhone clients on the server. A type library was not included in the Afaria 6.5 Feature Pack 2,so these properties and methods were not exposed for use with vbscript. [REF 34178*]

Rolled Hot Fix Information: 65AfariaFx41

Affected Client Types: NA

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 65AfariaFx50Admin.exe-Apply this Hot Fix to an Afaria 6.5 Feature Pack 2 Administrator system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site at http://frontline.sybase.com/support/downloads.aspx.

• For 65AfariaFx50Svr.exe-Apply this Hot Fix to an Afaria 6.5 Feature Pack 2 Server system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site

Installing the Hot Fix

Copy these files, 65AfariaFx50Admin.exe and 65AfariaFx50Svr.exe to temporary directories on the hard drive. Browse to the temporary directories and run these files. Once the setup has begun, follow the installation prompts until the installation has completed.

Back to top

Special Notes - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

• This hot fix is to be installed on a Afaria 6.5 Feature Pack 2 system.

Known Issue - NA

Uninstalling the Hot Fixes

This functionality is not present in these hotfixes.

What the Hot Fix Provides

Afaria Server

<Afaria Server>\Bin 
07/01/2010 02:56 PM 180,224 XsAuto.dll
07/01/2010 02:56 PM 159,744 Afaria.dll
07/01/2010 02:58 PM 236,032 XsChannelItemsAuto.dll
07/01/2010 03:15 PM 538,624 XsClientAuto.dll
07/01/2010 02:58 PM 64,512 XsConnectionsAuto.dll
07/01/2010 02:57 PM 773,120 XsPlatformAuto.dll
07/01/2010 03:20 PM 514,048 XsProfileAuto.dll

Afaria Administrator

<Afaria Administrator>\AfariaBridge
07/01/2010 02:56 PM 180,224 XsAuto.dll

<Afaria Administrator>\Bin 
07/01/2010 02:56 PM 159,744 Afaria.dll

 Published by Michael Auerbach 

Hot Fixes: 60Sp1AfariaFx26.exe - Afaria 6.0 Service Pack 1 Server
Hot Fixes Release Version: 6.00.4248.0
July 8, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support  

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.0 Service Pack 1 server system and are encountering the following issue:

Fixed Issue:

• When the Afaria Server that was the Alerts Lead went down, no Alert was ever raised by the Server, that was then elected as the new Alerts Lead. [REF 33566]

Rolled Hot Fix Information: NA

Affected Client Types: NA

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 60Sp1AfariaFx26.exe-Apply this Hot Fix to an Afaria 6.0 Service Pack 1 Server system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.0 Notes and System Requirements link located on our Technical Support site athttp://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy the Hot Fix file, 60Sp1AfariaFx26.exe, to temporary directory on the hard drive. Browse to the temporary directory and run the Hot Fix file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Note - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

Known Issues - NA

Uninstalling the Hot Fixes

This functionality is not present in this hot fix.

What the Hot Fix Provides

Afaria Server

<Afaria Server> (These temporary files are deleted once run)
04/27/2010 12:55 PM 703 4665_ASA.sql
04/27/2010 12:43 PM 852 4665_Ora.sql
04/27/2010 12:55 PM 675 4665_SQL.sql
04/27/2010 05:31 PM 227 hotfix.ini

<Afaria Server>\Bin
06/17/2010 10:26 AM 506,368 XSAlertsServer.exe

Technical Support

For online support go to our Technical Support site at www.ianywhere.com/support/support.html.
Contact your Account Manager for information on products and services at accountmanagement@ianywhere.com
Phone support: 
800-669-1211 (toll free) 
678-585-7320 (if you are in the Atlanta, GA, USA area) 
+44 (0) 1628 50 5321 (if you are in Europe, the Middle East, or Africa) 

Revision History

Fixed Issue:

• When the Afaria Server that was the Alerts Lead went down, no Alert was ever raised by the Server, that was then elected as the new Alerts Lead. [REF 33566]

Fixed Internal Issues:

NA

Rollup List:

These fixed issues (not internal fixed issues) should be listed in the comprehensive list of fixed issues mentioned in the "Who Should Use The Hot Fix" section as well.

NA

Published by Michael Auerbach 

Hot Fixes: 60Sp1AfariaFx25.exe - Afaria 6.0 Service Pack 1 Server
Hot Fixes Release Version: 6.00.4247.0
July 6, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support  

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.0 Service Pack 1 server system and are encountering the following issue:

Fixed Issue:

• When there were multiple Document Manager channels associated with a channel set, where that channel set is set as the default channel for the profile, only the very first Document Manager channel would display in the Client UI for Documents. [REF 33578*]

Rolled Hot Fix Information: NA

Affected Client Types: Windows Professional, Windows PPC 2005, Pocket PC 2003, Pocket PC 2005, Windows Professional, and WinCE.4x Clients

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 60Sp1AfariaFx25.exe-Apply this Hot Fix to an Afaria 6.0 Service Pack 1 Server system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.0 Notes and System Requirements link located on our Technical Support site athttp://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy the Hot Fix file, 60Sp1AfariaFx25.exe, to temporary directory on the hard drive. Browse to the temporary directory and run the Hot Fix file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Note - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

Known Issues - NA

Uninstalling the Hot Fixes

To uninstall a hot fix, go to the Add/Remove Programs and run the hot fix entry. For example, if the hot fix is named "60Sp1AfariaFx25," the hot fix entry would be "Afaria Hot Fix - 60Sp1AfariaFx25." A message box confirming the action will be displayed. When the rollback is complete, another message box will notify you of its success. The actions taken by rolling back a hot fix are listed below:
-The original product files will be restored to the state they were in, prior to installing the hot fix.
-The registry key for the hot fix will no longer be listed under the Afaria\Afaria\Patch registry key.
-The registry key for the hot fix will no longer be listed under the Afaria\Server\Setup key.
-The entry in the CPR.INI file will change from "Installed" to "Rolled Back."

Note: Rollback only affects the server, so any client that has already been updated, will continue to have the newer code. This is because the newer file has already been pushed to the client. Any additional connections to the client does not replace the newer file on the client with the older file on the server.

If you rollback a hot fix, please remember to restart the Afaria Services manually.

What the Hot Fix Provides

Afaria Server

<Afaria Server>\ClientESD\WinCE\WinCE.WM6Pro\M2MPrivileged\DocMgr\StrongARM
06/10/2010 08:48 PM 245,816 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.PPC2005\M2MPrivileged\DocMgr\StrongARM
06/10/2010 08:48 PM 245,816 XcDocMgr.exe

<Afaria Server>ClientESD\WinCE\WinCE.PPC2003\Unrestricted\DocMgr\StrongARM
06/10/2010 08:40 PM 242,688 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.4x\Unrestricted\DocMgr\StrongARM
06/10/2010 08:39 PM 252,416 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.4x\Unrestricted\DocMgr\ARMV4T
06/10/2010 08:39 PM 202,240 XcDocMgr.exe

 Published by Michael Auerbach 

Hot Fixes: 65AfariaFx43.exe - Afaria 6.5 Server
Hot Fixes Release Version: 6.50.4692.0
July 6, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support  

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.5 server and are experiencing the following issue:

• When there were multiple Document Manager channels associated with a channel set, with that channel set as the default Channel for the Profile, only the very first Document Manager Channel was displayed in the Client UI for Documents. [REF 33575]

Rolled Hot Fix Information: NA

Affected Client Types: NA

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 65AfariaFx43.exe-Apply this Hot Fix to an Afaria 6.5 Server system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site at http://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy the Hot Fix file, 65AfariaFx43.exe to temporary directory on the hard drive. Browse to the temporary directory and run the Hot Fix file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Notes - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

Known Issues - NA

Uninstalling the Hot Fixes

To uninstall a hot fix, go to the Add/Remove Programs and run the hot fix entry. For example, if the hot fix is named "65AfariaFx43," the hot fix entry would be "Afaria Hot Fix - 65AfariaFx43." A message box confirming the action will be displayed. When the rollback is complete, another message box will notify you of its success. The actions taken by rolling back a hot fix are listed below:
-The original product files will be restored to the state they were in, prior to installing the hot fix.
-The registry key for the hot fix will no longer be listed under the Afaria\Afaria\Patch registry key.
-The registry key for the hot fix will no longer be listed under the Afaria\Server\Setup key.
-The entry in the CPR.INI file will change from "Installed" to "Rolled Back."

Note: Rollback only affects the server, so any client that has already been updated, will continue to have the newer code. This is because the newer file has already been pushed to the client. Any additional connections to the client does not replace the newer file on the client with the older file on the server.

If you rollback a hot fix, please remember to restart the Afaria Services manually.

What the Hot Fix Provides

Afaria Server

<Afaria Server>\ClientESD\WinCE\WinCE.WM6Pro\M2MPrivileged\DocMgr\StrongARM
06/10/2010 06:48 PM 288,312 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.PPC2005\M2MPrivileged\DocMgr\StrongARM
06/10/2010 06:48 PM 288,312 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.PPC2003\Unrestricted\DocMgr\StrongARM
06/10/2010 06:40 PM 285,184 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.4x\Unrestricted\DocMgr\StrongARM
06/10/2010 06:40 PM 253,952 XcDocMgr.exe

<Afaria Server>\ClientESD\WinCE\WinCE.4x\Unrestricted\DocMgr\ARMV4T
06/10/2010 06:40 PM 203,776 XcDocMgr.exe

 Published by Michael Auerbach 

v5.7 iAnywhere Mobile Office

EBF Release 5.7.2010.0610

As of June 30, 2010

Contents

What’s New?

Important Notes

Patch Installer Files

Issues Fixed by EBF Builds

What’s New?

<5.7.2010.0610>

§  New utility, PackTool, for packing iAnywhere Mobile Office database tables

Name

PackTool.exe

Synopsis

packtool.exe [-backup "backup_folder"]

[-log "log_folder"]

[-timeout seconds]

Description

Tool used for packing all the iAnywhere Mobile Office database tables. This action requires exclusive access to the tables.

Runtime steps:

o    Stop iAnywhere Mobile Office Admin console

o    and LogViewer if running

o    Shutdown iAnywhere Mobile Office services

o    Shutdown Advantage Database Server service

o    Backup ADS error tables to the backup folder

o    Start Advantage Database Server service

o    Pack all iAnywhere Mobile Office database tables

o    Start iAnywhere Mobile Office services

The tool will not run if the Admin console is open. Errors are logged in the Application Event Log. Application progress is logged in a *PackTable.log file.

Options

-backup

o    Specify backup folder for ADS error logs. Defaults to the current folder.

-log Specify folder where this tool saves its logs.

o    Defaults to C:\Program Files\Sybase Messaging Server\Bin

-timeout

o    Specify the number of seconds to wait for processes to start/stop. Defaults to 60 seconds.

§  Kinetic Scrolling for Mobile Office Email Editor and Viewer

Navigation of the body of a Mobile Office email message has been improved with the implementation of kinetic scrolling in Mobile Office Mail for Nokia Series 60 5^th edition touch screen devices such as N97.

§  Meeting Request Invitation Creation on Nokia S60 Devices

Mobile Office Meeting Request editor is integrated into the device’s native Calendar application.

o    Required and optional participants can be added to the Meeting Request invitation.

o    Meeting participants can be selected from the device’s address book or Mobile Office Corporate Directory.

o    Meeting Request invitations are mailed to required and optional participants.

Known Issue: On S60 FP0 devices, such as E61, the newly created Meeting Request does not immediately appear in the invitation organizer’s calendar. The meeting will appear when the calendar application is restarted.

<5.7.2010.0216>

§  Scheduled Sync automatic Get More/Outbox send

If the device has Scheduled Sync enabled, any outbox item will be automatically sent.  Also any Get More requests of attachments or mail bodies will happen automatically without user interaction.

§  Symbian Standalone Security Manager 6.5 Update

§  Support for S60 3rd Edition FP2 devices such as E75, E52 and E72

§  Support for S60 5th Edition devices such as N97

§  Encryption for S60 3rd Edition (FP0, FP1, FP2) and 5th Edition i.e. encryption supported on all E-Series devices.

§  Windows Mobile Standalone Security Manager 6.5 Update

§  Known Issues

§  Cannot use password that is 20 characters long with Medium 6.5 Standalone Security Manager; requires hard reset

After locking a device with a 20-character password with medium security, the device will fail to unlock by typing in the 20-character password.  The device must be hard reset.

§  Device restarts again if device power save shutoff occurs after initial Standalone Security Manager client restart

After installing Standalone Security Manager (High) on a Windows Mobile Professional device, the device will restart and once booted, the Data Security Manager will prompt for password entry. If the device goes into power save shutoff after this initial restart, the device will restart again and come back to the password creation screen. After this second restart, no further restart activity occurs and the device does not enter power save shut off which may also be negative behavior assuming that the device should be able to power save with this screen up.

§  Device does not enter power save after client restart following Standalone Security Manager installation

If the device power save shut down is set to 1 minute, after installing Standalone Security Manager on Windows Mobile Professional device, the device will go through two restarts. Following the second restart, the device will sit on the password creation screen indefinitely without entering power save mode.

§  Upgrades for Configuration Files

When performing an upgrade, the routerconfig.xml, MoAdapterSettings.xml, and web.config configuration files are renamed to filename.<timestamp>.extension. If these files have been customized, merge the changes into the new files.

<5.7.2009.1206>

§  Scheduled Sync feature

Windows Mobile and Symbian clients now have the option to set Scheduled Sync to enable synchronizations according to a schedule that is set on your server. The feature overcomes network issues with always-on connectivity and battery life consumption on 3G networks. The client (iAnywhere Office Enabled setting) must be enabled for the Scheduled Sync to work.

§  File download retries to Windows Mobile devices will be limited for initial user registration with security enabled and for client upgrade.

This feature provides a way for file download retries to Windows Mobile devices to be limited for initial user registration with security enabled and for client upgrades.

If a client encounters an error during Security Manager installation or Mobile Office client upgrade, the error is logged on the server and an email message is sent to the Administrator. The "Email From" field of the User Registration settings is used as the Administrator email address. This must be a valid, monitored email address in order to receive these error messages.

The security software can be prevented from installing on Windows Mobile devices when the device's native security password feature is enabled. If security is configured at the time of registration, users will not receive any data until the installation issue is resolved.

When the client detects that a device password may be preventing the security software installation, the client notifies the server, triggering email messages to both the administrator and the user. The client then shuts down to prevent unnecessary data usage. The client retries the installation whenever the client engine restarts, at either the nightly maintenance restart or when the Settings application is run. However, the engine will continue to shut down after one installation attempt until the device password is disabled and the security software is allowed to install successfully.

Important Notes

Installing the EBF

Advantage Data Architect

Advantage Remote Server

Rollback Limitations

Installing the EBF

The patch installer requires that Mobile Office be shutdown before applying the patch in both single-node and multi-node configurations.

1.     Shutdown all Mobile Office services and applications on all server nodes.

2.     Run the EBF executable and follow the installation prompts as presented on every server node.

3.     Start up all Mobile Office services and applications on all server nodes.

Advantage Data Architect

When using Advantage Data Architect on a Mobile Office server, it is important not to re-collate any Mobile Office tables to a different language. All tables must use Engl(Amer) as their collation sequence. When installing Advantage Data Architect on a Mobile Office 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.

Advantage Remote Server

In some cases while using Advantage Remote Server and after shutting down the Mobile Office service, the Mobile Office tables will still be unavailable for exclusive access. In this case you must restart the Advantage Remote Server to free the tables.

Mobile Office Client files for OTA deployment

If you have a web site used for over the air deployment of the Mobile Office client, be certain to keep client files up to date on the web server. The sample \Tools\OTA files are not modified by this installer. The new clients are installed to the \bin\clients directory, and may be manually deployed to your web server.

PATCH INSTALLER FILES

All times Mountain Time Zone

Client Files

Client Files

Smartphone

Windows Mobile

Symbian

Server Files

ISSUES FIXED BY EBF BUILDS

<5.7.2010.0610>

§  31569 Hosted DMZ Proxy Server rejects new connections and throws GetFreeChannel error

The connection issue has been fixed by upgrading to OpenSSL version 0.9.8m.

§  32103 Unable to install iMO 5.7.2009.0914 or 5.7.2009.1206 on a Nokia E62-1 even after hard resetting the device.

Install was failing when reading the phone model due to the guaranteed Nokia file being unavailable. A phone model array is now used as first try when looking for phone model.

§  32128 iMO client on PPC device is unable to establish a VPN connection

There are now two methods for trying the connection to the network.

§  32513 Device settings are missed

The change monitor algorithm was updated so changes that occur during the same second as the scan are not lost.

§  32531 Client does not sync or install High SM cab when changing from Med to High Security in Admin with auto upgrade enabled

Security Manager cab is now delivered when security changes from medium to high with auto upgrade enabled.

§  32541 Users were no longer syncing and new registrations were failing

Calendar items with repeating instances of 10 years plus are now disregarded.

§  32597 Reply or forward a regular email on WM6.5 device also change its icon to something that looks like an iMO AMP icon.

The Outlook form provider's icon is now used to display the regular email's icon.

§  32598 HTC HD2: OBEngine.exe crashes when downloading a large amount of emails and the email notifications are set to On.

Due to a limitation of this device, notifications are disabled for this device type.

§  32668 Switching the automatic find off then back on in the email viewer causes the viewer to crash on the Nokia N97.

The message is not completed reloaded when switching the automatic find option on or off.

§  32718 Connection lock on the settings coming from the Admin template is not working during initial connection.

The locked connection settings are now queued when the device is registered.

§  32748 APNS notifications for Mobile Office not working

The User_Device_ID field is used to link the Device_Connection table when making the push query.

§  32780 Need more detail logged during crash recovery if the code cannot read the bin directory path from the registry

Logging of the Windows error code and registry path has been added to the event log when the errors occur in ecexceptions.cpp..

§  32782 The OBEListener crashes a few times per day.

§  33055 The OBEListener crashes a few times per day

There were many changes made to Listener to increase the stability.

1) The listener and agent were integrated into a single module, as tests have proven that CDO running in a single .exe is more stable. Now only OBEListener.exe will be running. Even though we install OBEAgent.exe, it won't be launched.

2) Internally the reloading of a mailbox happens only when interested properties are updated. This reduces the possibility of contention.

3) The service won't restart every time an Exchange server connection is reloaded. Instead, it will try to re-establish a connection to existing stores.

4) Exchange service monitors the Listener. If it doesn't have any messages queued in a given time, default 30 minutes, it will restart the Listener automatically.

5) Every day the Listener will be restarted.

§  33125 Most of the users get 8004010f error messages and were unable to sync. Restart OneBridge services solved the issue for awhile.

The main fix for the 8004010f is downgrading CDO to 6.5.8069.0. Along the way many stability fixes have been made including integrating Agent and Listener functionality into a single module. The tests we are doing here is general verification for Exchange changes as there is no specific fix for the 8004010f issue.

§  33248 Sony Ericsson Xperia X2: iMO unable to get the device's device ID

A new API is used to get the unique device ID for this device.

§  33272 The AdminWebConsole sample application crashes when Mobile Office Admin is used at the same time

Logic was added to handle a session timeout error in the sample web application to avoid access invalid session objects.

§  33513 APNS token will not be removed by re-register or cloning

The copy of the APNS Device Token during clone and reregister has been suppressed.

§  33559 New proxy connection issue exists in EBF 5.7.2010.0522

Error codes being raised due to code removal no longer occur.

§  33560 Public Key failure occurs when trying to do an "Import Keys" from license information window in Admin.

Error codes being raised due to code removal no longer occur.

<5.7.2010.0216>

§  30235 iAnywhere Mobile Office installer overwrites web.config file during upgrade

When performing an upgrade, the routerconfig.xml, MoAdapterSettings.xml, and web.config configuration files are renamed to filename.<timestamp>.extension. If these files have been customized, merge the changes into the new files.

§  30779 Notes Calendar entries created between the 3/23/09 and 9/27/09 will be synced with +1 hour offset to the device in Jerusalem time zone

The Jerusalem time zone was updated to include daylight savings information.

§  31070 Auto upgrade for the Mobile Office client and Standalone Security Manager does not work some Windows Mobile 6.1 devices.

A redundant parameter for backward compatibility was causing a conflict. This parameter has since been removed.

§  31071 In the documentation when searching for "Apple Push", the topic for "Apple Push Notification Service" is mislabeled as "Exchange Service Configuration"

The topic returned at the top of the “Select topic to display" list now shows the title as "Apple Push Notification Service Configuration" instead of "Exchange Service Configuration"

§  31449 Chair gets "unread deleted" messages from invitees accepting meeting requests with read receipts on Nokia devices

A delayed delete function is now invoked when an e-mail is deleted from within the e-mail viewer, whether explicitly or as a result of responding to a meeting request.

§  31460 Registration email is sent to the wrong user, if two users have the same alias in Active Directory.

The Exchange modules are changed to use SMTP address as the key in registration. Also, the administrator will show the SMTP address for Exchange installation. The registration dialog was also changed to show the SMTP address.

§  31527 When a user creates a new meeting with invitees in the Notes client, save and send, and opens afterwards directly another meeting in the calendar, the Notes client freezes for about 20 seconds.

An optimization has been made on the client to prevent users’ Lotus Notes desktop from freezing up for a few seconds as soon as a meeting is created.

§  31570 iPhone client corrupts Exchange Contacts during Sync

The Exchange agent no longer clears the CDOFIELD_EMAILENTRYNUM_S property, which caused the contact to get removed from the Personal Address Book (PAB).

§  31744 Using the * key on the phone touchpad in numeric mode causes the Symbian Sybase Settings application to crash.

The key map function has been changed for fields that allow text and numeric input.

§  31750 Server system requirements differ in Admin online help and Getting Started Admin PDF

The details of the iAnywhere Mobile Office server system requirements in these comparable sections of the two documents are now the same.

§  31768 Additional German and Japanese translation changes

Additional updates to resource strings have been made for German and Japanese.

§  31821 The OBEListener crashes a few times per day. OBEListener caused an EXCEPTION_ACCESS_VIOLATION in module OBEListener.

The call to get the server activation code during startup fails sometimes during restarts due to access failure. This may make the agent and listener continuously restart over an extended period of time. The change to only require access to once in a lifetime avoids the service interruption.

§  31834 In Exchange, a declined meeting request, which is later cancelled by the chair, will send a cancellation notice which can be accepted.

The meeting flag is no longer incorrectly sent for cancelled meetings.

§  31837 On second attempt to download an attachment when iAnywhere Mobile Office is disabled, device reports that the previous Get Mail is still in progress.

Due to the changes for the 'offline' Get Mail functionality, this is no longer a bug. When Mobile Office runs Get Mail in disabled mode, it actively makes a connection with the server and downloads the attachment. This means that the message displayed, 'GetMail is still in progress', is now valid, if you do go back into the email and attempt to download the attachment again before it has completed..

§  31895 When setting email to unread via the email list view, the change does not always get synced back to the server.

Additional state information, including a copy of the 'Unread' state in the e-mail's index entry, is now stored. If on processing a record change, a discrepancy is found between the actual unread state of the e-mail and the client version of the email, then we update the client version of the email and unset the 'Ignore change' flag on the e-mail. This then allows the change to be propagated to the server.

§  32006 In Admin, when registering a widget, if the Display Name is written using Japanese, ADS throws Error 7200: AQE Error

The error message has been improved for situations when multi-byte character strings are rejected. The error message is produced by the server, so it should apply to Admin and Web Services calls.

§  32022 Admin Guide CHM Template Property Tables: copy No Groupware Security Manager Level and Custom changes to other tables

The "Template Property Table for Domino and Exchange" and "Template Property Table for IMAP/POP3" topics no longer say the Security Manager Level doesn't apply to Windows Mobile and now mention the Custom settings.

§  32023 Admin Guide CHM: add index entry for Scheduled Sync

Entries for "scheduled sync" now appear in the Index list.

§  32024 A contact created in Outlook which is saved as lastname, firstname (company) gets synced as lastname, firstname [][] company to the device.

The device will no longer try and make a “file as” string.

§  32056 Can't launch Corporate Directory on the Nokia 5800

When adding a new record to the Corporate Directory contacts cache, the record is now checked for uniqueness. If it does exist, then the record is updated instead.

§  32100 Getting Started Device User PDF: add same scheduled sync updates included in Device User CHM

Getting Started Device Guide PDF now contains same "scheduled sync" coverage as Device Guide CHM online help file.

§  32101 All iAnywhere Mobile Office 5.7 PDFs updated for Q1-2010 EBF: set last mod date to February 2010; copyright year to 2010

Last Revised date on all of these documents is now "February 2010" and all copyright year references are set to 2010.

§  32113 Email Injection Dev Guide: Remove Reference to Matching Rules on BCC Field

The following sentence has been removed from the description (was at the end): "Since the BCC line is not visible on the device, the most likely use for this field is for server processing, such as if you are using it in matching rules for Mobile Office Business Process Workflow packages."

§  32121 SMTPOriginator is filled with wrong chair SMTP address for meetings from a 3rd party outside the company that are accepted on the PDA

The problem field has been removed from the outgoing email.

§  32127 During the registration process, an error message occurs, if “Send SMS activation message” is enabled and a SMS address is used in the format 123@dom

SMS has been changed to allow almost any text with an '@' in the middle to be treated as an email address rather than a phone number. The error mentioned in the bug is caused by not having an SMS activation provider and is inappropriate in this case. The simpler email test should keep them in the correct code path, and avoid the error message. Registration was succeeding, regardless of the SMS problem.

§  32175 DMZ Proxy Guide: Change "Last Revised" Date from "month year" to "September 2009"

The "Last Revised" date entry has been changed from "month year" to "September 2009".

§  32176 Device Guide CHM: Remove Duplicate Entries for Symbian Advanced iAnywhere Mobile Office Settings

“Refresh All Data", "Restart Client", and "Keep Alive Time" entries are no longer duplicated and all bullets at top (from "iAnywhere Office Enabled" down thru "Keep Alive Time") are no longer indented an extra level.

§  32189 The OBEListener crashes a few times per day. OBEListener.exe caused an EXCEPTION_ACCESS_VIOLATION in module exmapi32.dll

When the status of device changes, it results in the device being removed from the list of devices that are being watched. There is a small timing interval where the notifications that have arrived but are not yet processed by the MAPI subsystem cause the crash. This has been fixed.

§  32194 Personal files will be deleted after removing iAnywhere Mobile Office on the device

Personal files will not be deleted after removing Mobile Office from the device.

§  32247 Intermittent Communication Error and ClientEngine KERN-EXEC 0 on Nokia E75 when using Wi-Fi connection

A connection is verified before getting the settings to alleviate this error.

§  32323 The file C:\system\temp\CorpDir.sis remains on the device after uninstall on the Nokia E71.

Code has been added to remove the sis file on uninstall if it present.

§  32359 Support capture tool does not collect the selected data correctly.

Code has been fixed to correctly gather the selected data in the support capture tool.

<5.7.2009.1206>

§  29535 On the Symbian Series 60 5^th Edition devices, no tone is sounded when a new email arrives on the device with 'New e-mail alerts' on

This has been updated to be done on initial creation even if the email is read when it comes down to the server.

§  30689 Can't deploy widget to device when it has "Workflow" as the opening and / or ending tag in the widget XML

The widget parsing code has been updated to accept <workflow>..</workflow> or <widget>..</widget>.

§  30759 Nokia E71 - selecting "Get Mail" in the MTM when the device is in Offline mode gives the user the impression that the device is attempting to form a connection

The connection status is now checked before returning to the UI. If the device is in the offline profile, the UI is sent the notification.

§  30789 24 hour client engine auto restart is not getting fired every 24 hours on the N97

The original calculated restart time is now saved and used to decide whether the client engine needs to restart, even if there is an error on the timer. When the time has passed the original time, a new restart time is recalculated.

§  30804 Sending emails from a mobile device, the username is displayed in the "To" field or "To" field is empty instead of displaying the display name

A change has been made so CDO can resolve the names properly.

§  30805 Meetings are 1 hour off from the end of September through October with servers and devices in GMT+1 German time zone

The recurring appointment is now updated with the correct information.

§  30867 German translation requires improvement

Symbian resource strings and some resources describing string component ordering for longer strings have been updated.

§  30868 From address is blank or missing for select emails while synchronizing against Domino

The code was dropping email addresses when the email address contained unsupported characters. Now the unsupported characters will be stripped.

§  30882 Security.dll is not deleted on upgrade

Ssecurity.dll is now removed from the bin directory on upgrade.

§  30888 Sending Microsoft Office 2007 docx files via a https proxy connection will never finish

On a Windows Mobile 6.1 device, a small .docx file will be about 8.5 KB. We read in 4KB chunks, and SSL was buffering the small remainder such that it was not detected. The SSL code has been changed to dynamically allocate proper size and read entire decrypted chunk.

§  30891 Nokia N93 - The searching progress bar cannot be correctly displayed after switching the test device between UI modes.

Updates were made to allow the operating system control the display.

§  30910 OBEListener.exe crash dump created few times a day

Special exception handling code is added during CDO logon and logoff. This will not log to the event viewer.

§  30938 Large email attachments fail to sync from client to server

The message queues and memory file have been changed to use the mass storage drive if it is available.

§  31006 Imported Notes holidays and anniversaries are shifted by one day on Symbian devices

The recurring part of the calendar item now adjusts appropriately.

§  31067 Notes usernames with ß produce errors in the logs although they can sync

The database call now works with ß in the username.

§  31071 When searching in the documentation for "Apple Push", the topic for "Apple Push Notification Service" is mislabeled as "Exchange Service Configuration"

The incorrect title ("Exchange Service Configuration") has been replaced with "Apple Push Notification Service Configuration" to match <h1> title displayed on page

§  31116 Unable to access all of db files during capture file creation

Admin is now updated to use a different tag in the supportlib config, so it won't try to copy the DB files anymore. A new tag was added to SupportLib.xml to allow conditional capture of DB files.

§  31126 E2E monitor service does not start the E2E test

The build scripts are fixed to copy the correct file.

§  31134 Accepting a meeting request for one occurrence in the middle of a recurring meeting puts the item on the calendar but does not remove the acceptance from the Inbox of the device.

When the exact steps in recreation are executed, the listener filtered an Inbox event that had same note id as a calendar event. This caused the Inbox Meeting Request stay as MR instead of ordinary mail. This bug is fixed in the listener. Now listener lets through the Inbox event and filters only Calendar event.

§  31145 Disabled roaming option on Symbian devices doesn't work for all carriers

A reconnect of the client with the server is now forced when a notification is received that the client is roaming and the settings state that roaming is not allowed. The device then goes into a state waiting for the client to not be roaming before establishing the connection.

§  31177 Symbian S60 client is not always detecting the correct state of paused data connections which pushes the client into the back-off procedure. This is causing delays in delivering data to the device.

A phone call monitor was added that starts when the device is in 'back-off' mode. When the call finishes the device will automatically get notified and Mobile Office will attempt to connect regardless of the current retry back off time.

§  31238 Nokia E52: Attempting to connect to server with bad client settings crashes the client engine on a German device

A buffer size has been fixed when running with language set to German.

§  31256 Exchange Listener can't open mailboxes

The logon failure reported when server is down and CDO crashed had the same return code causing the services to restart when the Exchange server was down. The return codes were changed so that restart only happens when CDO crash occurs.

§  31265 Apple push stopped working

§  31763 Apple push (APNS) stopped working

The SMS and APNS push query method are now wrapped in a try/catch block to avoid the query thread exiting due to exceptions. The connection retrying logic has also been changed.

§  31287 PDF and WAV files cannot be opened from the Mobile Office mail inbox on Nokia E51 and E71 devices

A different method is used to open the document as an embedded document, allowing more file types to open correctly.

§  31326 Admin times out when modifying a setting for a large number of users.

The timeout has been increased to 5 minutes and a registry override has been added.

§  31450 Using the GetLicenseInfo WS API with a production serial number will crash with an error.

The issue caused by parsing the license expiration data when the data was not available has been fixed.

§  31473 Very long meeting title will cause Symbian devices to stop syncing

The subject string is now truncated before converting for logging purposes.

§  31487 The menu displays incorrectly the first time the menu soft key is selected after entering the Messaging app (regardless the transport)

The old menu hook registry key was removed to avoid conflict with the new key.

§  31491 N97: Incorrect model being displayed in Admin after v20.0.019 ROM upgrade

A second 'default' model name is now checked. Nokia appears to now use 'N00' and 'S60'.

Hot Fixes: 65AfariaFx44.exe - Afaria 6.5 Administrator
Hot Fixes Release Version: 6.50.4696.0
June 28, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support  
 

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.5 administrator and are experiencing the following issue:

• If a freshly attached worklist was copied, the contents of the worklist were not copied; instead, instead a blank worklist was created. [REF 33376*]

Rolled Hot Fix Information: NA

Affected Client Types: NA

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

System Requirements

• For 65AfariaFx44.exe-Apply this Hot Fix to an Afaria 6.5 Administrator system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site at http://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy the Hot Fix file, 65AfariaFx44.exe to temporary directory on the hard drive. Browse to the temporary directory and run the Hot Fix file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Notes - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

Known Issues - NA

Uninstalling the Hot Fixes

This functionality is not present in this hot fix.

What the Hot Fix Provides

Afaria Server

<Afaria Administrator>\Client-Bin:
06/17/2010 10:39 AM 90,112 SessionManagerWizEdit.dll

 Published by Michael 

Hot Fixes: 65AfariaFx42.exe - Afaria 6.5 Server Feature Pack 2 System
Hot Fixes Release Version: 6.50.4691.0
June 28, 2010

Contents

Who should use the Hot Fix 
System Requirements
Installing the Hot Fix
Special Notes
Implementation Notes
Known Issue
Uninstalling the Hot Fixes
What the Hot Fix Provides
Technical Support 

Who Should Use the Hot Fix?

This Hot Fix should be used if you are running Afaria 6.5 server system and are experiencing the following issues:

• Remote wipe did not work on the HTC HD2 device. [REF 32970*]

• When using SSL to the load balancer and then http to the server with the certificate in the format of *.domain.com, a direct hit of the server name worked, but going through the load balancer failed. Note: The client failed on the common name resolution. [REF 31710*]

• Load balancer/firewall threw out packets that did not conform to the HTTP 1.1 standard and were reported as the packet being incorrect. [REF 31842*]

• Afaria 6.5 Client could not connect to the Afaria using XNETS (SSL) after an upgrade. [REF 32119*]

• When uninstalling the Afaria client from a Windows Mobile device, using the “Remove programs” User Interface (UI) on the device, it did not remove the Afaria registry entries or the Program Files\Afaria folder and files. [REF 31793*]

Rolled Hot Fix Information: 65AfariaFx2, 65AfariaFx16, 65AfariaFx31, and 65AfariaFx33.

Affected Client Types: Win32 Clients, WinCE.4x, Pocket PCs 2005, Smartphones 2005, Windows Mobile 6 Standard, and Windows Mobile 6 Professional clients

*Documentation convention for issue reference numbers: Each issue item is suffixed with a reference number, e.g., "[REF 99999]", when applicable. Sybase iAnywhere uses this internal reference number to track issues and enhancements. Note that this reference number does not correspond to knowledgebase articles or the case numbers used by Technical Support for problem resolution, enhancement requests, etc.

Back to top

System Requirements

• For 65AfariaFx42.exe-Apply this Hot Fix to an Afaria 6.5 Feature Pack 2 Server system on Windows Server 2003 Standard Edition R2, Windows Server 2003 Standard Edition with Service Pack 2, Windows Server 2003 Standard Edition with Service Pack 1, Windows Server 2003 Enterprise Edition R2, Windows Server 2003 Enterprise Edition with Service Pack 2, or Windows Server 2003 Enterprise Edition with Service Pack 1. For further system requirements, see the Afaria 6.5 link located on our Technical Support site at http://frontline.sybase.com/support/downloads.aspx.

Installing the Hot Fix

Copy the Hot Fix file, 65AfariaFx42.exe to temporary directory on the hard drive. Browse to the temporary directory and run the Hot Fix file. Once the setup has begun, follow the installation prompts until the installation has completed.

Special Notes - NA

Implementation Notes

• It is important to shut down and upgrade all Afaria components to the same version, at the same time. Do not operate an Afaria environment with different Afaria versions or patch levels.

• This hot fix goes on a system with Afaria 6.5 Feature Pack 2 already installed on it.

Known Issues - NA

Uninstalling the Hot Fixes

To uninstall a hot fix, go to the Add/Remove Programs and run the hot fix entry. For example, if the hot fix is named "65AfariaFx42," the hot fix entry would be "Afaria Hot Fix - 65AfariaFx42." A message box confirming the action will be displayed. When the rollback is complete, another message box will notify you of its success. The actions taken by rolling back a hot fix are listed below:
-The original product files will be restored to the state they were in, prior to installing the hot fix.
-The registry key for the hot fix will no longer be listed under the Afaria\Afaria\Patch registry key.
-The registry key for the hot fix will no longer be listed under the Afaria\Server\Setup key.
-The entry in the CPR.INI file will change from "Installed" to "Rolled Back."

Note: Rollback only affects the server, so any client that has already been updated, will continue to have the newer code. This is because the newer file has already been pushed to the client. Any additional connections to the client does not replace the newer file on the client with the older file on the server.

If you rollback a hot fix, please remember to restart the Afaria Services manually.

What the Hot Fix Provides

Afaria Server

<Afaria Server>\ClientESD\Palm\Proxy
06/20/2007 09:12 AM 1,064,960 sbgse2.dll
04/30/2010 12:35 PM 444,928 XCSSL.dll
04/30/2010 12:13 PM 487,424 XeClientConduit.dll

<Afaria Server>\ClientESD\Win32\Core
06/20/2007 09:12 AM 1,064,960 sbgse2.dll
04/30/2010 12:35 PM 444,928 XCSSL.dll
04/30/2010 12:28 PM 478,208 XeClient.exe

<Afaria Server>\ClientESD\WinCE\WinCE.4x\Unrestricted\Core\StrongARM
12/04/2009 03:28 PM 959,488 XeClient.exe
06/10/2010 05:55 PM 163,328 XeSetup.dll

<Afaria Server>\ClientESD\WinCE\WinCE.PPC2003\Unrestricted\Core\StrongARM
12/04/2009 03:22 PM 1,085,952 XeClient.exe
06/10/2010 05:55 PM 163,328 XeSetup.dll

<Afaria Server>\ClientESD\WinCE\WinCE.PPC2005\M2MPrivileged\Core\StrongARM
04/25/2010 09:30 PM 147,000 XcListenerCE.exe
05/28/2010 12:36 AM 1,090,104 XeClient.exe
06/10/2010 05:59 PM 166,456 XeSetup.dll

<Afaria Server>\ClientESD\WinCE\WinCE.SP2005\M2MPrivileged\Core\StrongARM
04/25/2010 09:30 PM 147,000 XcListenerCE.exe
05/28/2010 12:38 AM 1,080,376 XeClient.exe
06/10/2010 05:59 PM 166,456 XeSetup.dll

<Afaria Server>\ClientESD\WinCE\WinCE.WM6Pro\M2MPrivileged\Core\StrongARM
04/25/2010 09:30 PM 147,000 XcListenerCE.exe
05/28/2010 12:36 AM 1,090,104 XeClient.exe
06/10/2010 05:59 PM 166,456 XeSetup.dll

<Afaria Server>\ClientESD\WinCE\WinCE.WM6Std\M2MPrivileged\Core\StrongARM
04/25/2010 09:30 PM 147,000 XcListenerCE.exe
05/28/2010 12:38 AM 1,080,376 XeClient.exe
06/10/2010 05:59 PM 166,456 XeSetup.dll

<Afaria Server>\ClientInstall\WinCE\WinCE.PPC2005\M2MPrivileged
06/10/2010 06:04 PM 1,897,036 Afaria.2577.CAB

<Afaria Server>\ClientInstall\WinCE\WinCE.SP2005\M2MPrivileged
06/10/2010 06:03 PM 1,874,317 Afaria.2577.CAB

<Afaria Server>\ClientInstall\WinCE\WinCE.WM6Pro\M2MPrivileged
06/10/2010 06:04 PM 1,897,036 Afaria.2577.CAB

<Afaria Server>\ClientInstall\WinCE\WinCE.WM6Std\M2MPrivileged
06/10/2010 06:03 PM 1,874,317 Afaria.2577.CAB

<Afaria Server>\TestHTML\Bin
06/20/2007 09:12 AM 1,064,960 sbgse2.dll
04/30/2010 12:35 PM 444,928 XCSSL.dll
04/30/2010 12:28 PM 478,208 XeClient.exe

 Published by Michael Auerbach 

 Afaria for iOS 4

Sybase Afaria delivers market-leading and proven functionality to empower enterprise IT to effectively manage the proliferation of both personally-liable and corporate-liable mobile devices, while providing a high degree of security to meet the strictest corporate standards. This upcoming release, which will be available in Beta in July, extends Sybase’s expansive list of device types supported by Afaria which include iPhone, iPad, Android, BlackBerry, Symbian and Windows Mobile. Read the press release announcing Sybase/Afaria support for Apple iOS 4. Afaria for iOS 4 Features New features of the Afaria release support both on-premise and multi-tenant, managed mobility service models, delivering significant customer benefits including: Simplified delivery of enterprise applications Separation of personal and enterprise information on the iPhone Simplified iPhone management Improved transparency and control Read more about Afaria for iOS 4. Register for the Webcast to learn more about the new features. Thursday July 15th 2:00pm EDT. Register now. Apply for the iOS 4 Beta I am a current Afaria customer on active support I am not a current Afaria customer

 Published by Michael Auerbach

Published by Michael Auerbach