Description of the Duet 1.5 for Microsoft Office and SAP Service Pack 1

This article describes the Duet for Microsoft Office and SAP issues that are fixed in the Duet for Microsoft Office and SAP hotfix package that is dated December 18, 2008.

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix packages.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issues that this hotfix package fixes

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

• The sender name of large reports that arrive may be the Duet RequestHandler account instead of the account that is configured as the "Duet Reporting" account.
• The body text of a bound appointment may not be sent to the back-end server if it contains the initial CREATE Web service call. However, it is sent when the sweeper triggers the next UPDATE call.
• In the Outlook calendar, the first drag-and-drop operation of a bound appointment to a new time may not trigger an update to the back-end server.
  
  Note This hotfix addresses the first drag-and-drop operation for an appointment. However, later drag-and-drop operations for the same appointment during the same Outlook session may still not trigger an update.
• On some standard Outlook items, the Duet buttons may not be displayed. Therefore, you cannot make the item into a Duet bound item.
• For messages that are sent through the RequestHandler, characters in attachment file names may not be displayed correctly.
• Client promotion may fail if the client's Synchronization Data Store (SDS) is located on a remote SQL Server database. Remote SDS configuration is common with Duet installation in Citrix environments.
  
  To resolve this issue, refer to the Readme file for additional SQL configuration scripts and for instructions that are needed when remote SDS databases are used.
• During a Duet BoundItem upgrade, an additional sync call to the back-end server may be triggered.
• When you cancel a bound meeting request, this may trigger a DELETE call followed by a CREATE call followed by another DELETE call to the back-end server instead of just a single DELETE call.
• If the Sweeper is temporarily unable to access bound items in Outlook, DELETE requests for those items may be sent incorrectly to the back-end server.
• Clients may be unable to download the Duet Metadata if the Metadata Service is configured for HTTPS.
• More information about how to help secure communication to a remote SDS was added to the Duet Installation Guide under the heading "Metadata Service."
• The ability to use encryption when communicating to an SDS on a remote SQL Server is now available. To do this, enable the new Duet Group Policy setting SdsSqlEncryption.
• The CheckExchangeAccountConfiguration command of the Duet ClientRepair Tool may not correctly report when the OBAControlMessages folder is missing.
• The Duet add-in may unnecessarily load with Microsoft Word or with Microsoft Excel. A new "Duet Addin Load Settings" Group Policy was added to enable control over which Office applications will load Duet. This Group Policy setting is documented in "Appendix A" of the Duet Administration Guide.
• Sensitive information may be written to the log file when you enable verbose logging in Duet. Verbose logging will no longer write the field values to the log file.
• The Duet client installation may fail when you try to install the SQL Express 2005 components on a localized installation of Windows XP SP3. The Installing Duet Client Components (Microsoft) chapter of the Duet Installation Guide was updated with information about how to handle this situation.
• If Duet cannot decrypt the personalization data, Outlook may crash, and you may notice in Task Manager that DW20.EXE is running.
• On Japanese Duet clients, a dialog box that states, "Error occurred in Duet" may appear when you open mail items.
• If the Duet Sweeper encounters an invalid or problematic item, it may fail at that point and not process the rest of the items. The Sweeper then skips the invalid item and continues to process the remaining items.
• Installing Duet 1.5 SP1 on a client may reset the SDS SQL Server name setting to the default value of (Local)\OBASQLExpress.
• If Active Directory was configured to require secure binds, the Duet RequestHandler setup may fail when it validates the Exchange account.
• When you upgrade the Duet client, errors are logged. However, the errors should have been warnings.
• The Sent Items folder for the mailbox that is used by the RequestHandler may grow large and exceed storage limits. To resolve this issue, a new SaveInSent parameter can now be added to the RequestHandler's Web.Config file.

  <add key="SaveInSent" value="true"/>

  When SaveInSent is set to "false" e-mail messages will not be saved in the Sent Items folder. The default setting is "true."

Steps to deploy the client update

Prerequisites

Duet 1.5 RTM should be installed. ARP should show the version of Duet as 1.5.3139.00.

Steps for implementation

1. Install the MSP file that is provided.
2. To verify that the MSP is installed successfully, make sure that the version of the Duet Client is 1.5.4010.00.
3. Apply the new ADM file.

Steps to install Request Handler

Prerequisites

A fresh server computer is required. Any earlier version of Request Handler should be uninstalled by running the Microsoft.OBA.RequestHandler.msi before you continue.

Steps for implementation

1. Install Duet 1.5 Service Pack 1 Request Handler build 1.5.4010.00.
2. To verify that the MSI is installed successfully, make sure that the version of all RH DLLs is 1.8.4010.00.

Steps to install MDS

Prerequisites

A fresh server computer is required. Any earlier version of MDS should be uninstalled before continuing by running the Microsoft.OBA.RequestHandler.msi

Steps for implementation

1. Install Duet 1.5 Service Pack 1 MDS build 1.5.4007.00.
2. To verify that the MSI is installed successfully, make sure version of all MDS DLLs is 1.8.4007.00.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

The hotfix package contains the following files: After you run Duet_1.5_102.msp to upgrade the client, the following files will be updated to build 1.8.4010.0: After Microsoft.OBA.RequestHandler.msi is installed on the server, the Request Handler file informartion will be as follows: After Microsoft.OBA.MetadataService.msi is installed on the server, the Metadata Service file informartion will be as follows:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: