Description of the Duet for Microsoft Office and SAP hotfix package: February 22, 2007

List of issues fixed

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

• An InvalidComObjectException error may occur when you use a Duet for Microsoft Office and SAP client computer. This error may occur because of a known "reference counting" issue in which the boundItem object is released prematurely when Marshal.ReleaseCOMObject is called. Additionally, you may receive the following error message:
  COM object that has been separated from its underlying RCW cannot be used.
  The hotfix fixes this "reference counting" issue.
• When you run Microsoft Office Outlook on a Duet for Microsoft Office and SAP client computer and you create new items or you open existing items, performance may be slower than usual. The hotfix fixes this performance issue.
• The default cache size on a Duet for Microsoft Office and SAP client computer is 10 megabytes (MB).
  
  This hotfix increases the default maximum cache size to 100 MB for the client computer after the new Microsoft.Duet.Framework.GroupPolicies.adm file is deployed. The new Microsoft.Duet.Framework.GroupPolicies.adm file is included in this hotfix.
  
  For more information about how to deploy the new Microsoft.Duet.Framework.GroupPolicies.adm file, see the "Post-installation information" section.
• When a Duet for Microsoft Office and SAP client computer initiates a Web service call, an icon that represents a spinning globe is displayed to indicate that the system is processing the call. After this hotfix is installed, no error icon or error message is displayed if a back-end error occurs and the user should not be concerned about it. However, the error message is automatically logged in the Application event log.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. 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

You must have the Duet for Microsoft Office and SAP hotfix package that is dated December 3, 2006 to apply this hotfix package.

For more information about the Duet for Microsoft Office and SAP hotfix package that is dated December 3, 2006, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart your computer after you apply this hotfix. However, you must log off the client computer and then log on as the Duet user.

Registry information

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

Post-installation information

To use the new default maximum cache size of 100 MB, do one of the following actions:

• If you are a domain administrator, run the Group Policy Management Console tool (Gpmc.msc) to deploy the policy file to the whole domain.
• If you are a local administrator, run the Group Policy Object Editor tool (Gpedit.msc) to update the policy file on the local client computer. To do this, follow these steps:
  1. Click Start, click Run, type gpedit.msc, and then click OK.
  2. Expand one of the following:
     • Computer Configuration
     • User Configuration
  3. Right-click Administrative Templates, and then click Add/Remove Templates.
  4. In the Add/Remove Templates dialog box, click the existing Microsoft.Duet.Framework.GroupPolicies.adm file, and then click Remove.
  5. Click Add.
  6. Locate and then select the new Microsoft.Duet.Framework.GroupPolicies.adm file that is included in this hotfix package. Then, click Open.
  7. Click Close to close the Add/Remove Templates dialog box.

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.

Download informationMicrosoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:Additional notes

• For more information about how to install this hotfix, see the Duet Value Pack Hotfix Readme (KB 932876).htm file that is included in the hotfix package.
• For more information about the terminology that Microsoft uses to correct software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
  824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates