Update package for Office Communications Server 2007 R2 Group Chat Server SDK: April 2010

This article describes the Microsoft Office Communications Server 2007 R2 Group Chat Server SDK issues that are fixed in the update package for Office Communications Server 2007 R2 Group Chat Server SDK that is dated April 2010.

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

Issues that this hotfix package fixes

This update package fixes the following issues:

• 981450  (http://support.microsoft.com/kb/981450/ ) The Group Chat API throws an unhandled exception when you develop a service by using a specific Group Chat API in Office Communication Server 2007 R2, Group Chat SDK
• 981451  (http://support.microsoft.com/kb/981451/ ) "An item with the same key has already been added" error message in an Office Communications Server 2007 R2 Group Chat Server SDK-based application
• 981455  (http://support.microsoft.com/kb/981455/ ) The IsManager property of a participant displays an incorrect status in an Office Communications Server 2007 R2 Group Chat Server SDK-based application
• 981456  (http://support.microsoft.com/kb/981456/ ) The "ParticipantAttendanceChanged" event callback function is not invoked in a Group Chat Server SDK-based application when a user signs out of an Office Communications Server 2007 R2 Group Chat client
• 981457  (http://support.microsoft.com/kb/981457/ ) An Office Communications Server 2007 R2 Group Chat Server SDK-based application crashes and throws an exception when an Add-in is set in a chat room
• 981458  (http://support.microsoft.com/kb/981458/ ) The ParticipantAttendanceChanged event callback function is not invoked in an Office Communications Server 2007 R2 Group Chat Server SDK-based application
• 981459  (http://support.microsoft.com/kb/981459/ ) An Invalid Chat Room URI exception is generated in an Office Communications Server 2007 R2 Group Chat Server SDK-based application

Update package information

The following file is available for download from the Microsoft Download Center:

Download the UCGCSDK.msi package now. (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c3dc291c-db47-47e8-9964-0c077776ddb0)

Release Date: April 2010

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

Please make sure that the following services are running before you install the update:

• Office Communications Server 2007 R2 Group Chat Server - Lookup service / Channel service
• Office Communications Server 2007 R2 Group Chat Compliance Server - Compliance Service

Restart requirement

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

Replacement information

This update does not replace any previously released update.

Registry information

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

Update package installation information

Install this update for Office Communications Server R2 Group Chat Server

1. Make sure Office Communications Server (OCS) 2007 R2 Group Chat servers are installed, configured and functioning correctly. OCS 2007 R2 Group Chat servers include Channel Server, Lookup Server and Compliance Server.
2. Stop the Channel service and stop the Lookup service that are currently running
3. To apply this update, install this update by running UCGCSDK.msi on all of the computers that are in any of the Group Chat Server roles.
4. On the Chat server, start the Server Config Tool as follows:
   • Start menu: All Programs, Administrative Tools, Server Config Tool
   • File location: <driver letter>:\Program Files\Microsoft Office Communications Server 2007 R2\Group Chat Server\ServerConfigTool.exe.
5. Click Yes when you receive the following message, and the Server Config Tool upgrades the existing Group Chat database schema. Additionally, the Server Config Tool changesthe server's configuration files to reflect these changes.
   The Group Chat servers installed on this computer require an upgrade to QFE1. You must have read/write permission to the server's configuration files to complete this task.
   
   Note You must shut down all group chat servers before you perform this upgrade.
6. Restart the Channel service and restart the Lookup service and then restart the Compliance Server service.

Workaround on how to add a new server into an existing pool after you install this update

Only the MSI update files (.msp files) without a complete installer are released in the update package. After youupgraded all OCS 2007 R2 Group Chat servers to this update, follow these steps to add another Group Chat server into the existing pool:

1. Set up OCS 2007 R2 Group Chat Server (Channel Server and Lookup Server) on a new database by using the same service accounts as the existing pool. Refer to OCS 2007 R2 deployment documentation for more information about how to set up OCS 2007 R2 Group Chat server.
2. Upgrade to the new OCS R2 Group Chat installation.
3. Stop both the Channel service and the Lookup service.
4. Run the following command to reconfigure the new servers to point to the Group Chat database pool.

   <driver letter>:\Program Files\Microsoft Office Communications Server 2007 R2\Group Chat Server\ServerConfigTool.exe /i

Note All services start automatically after the servers are reconfigured.

Removal information

After you apply this update, it cannot be uninstalled. If you uninstall this update, the Channel service and the Lookup service does not start. You may receive the following error message in the event log.

Event ID 6407
Description : The Server is not compatible with the database at server=<yoursqlservername>;Database=<databasename>;Integrated Security=SSPI

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

File information

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

The global version of this update package uses a Microsoft Windows Installer package to install the update 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.

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