Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/924604

From BetaArchive Wiki

Article ID: 924604

Article Last Modified on 6/27/2007



APPLIES TO

  • Microsoft Office Live Communications Server 2005 Enterprise Edition
  • Microsoft Office Live Communications Server 2005 Standard Edition



SYMPTOMS

Consider the following scenario:

  • You have a Microsoft Office Live Communications Server 2005 front-end environment and a Microsoft SQL Server 2005 back-end environment.
  • You create a federation between your organization and a partner organization.
  • Presence information works as expected within both organizations. Users from your organization can view the presence information of other users in your organization. Users from your partner organization can view the presence information of other users in the partner organization.
  • You enable federation for a user in your organization.

In this scenario, when a user from your partner organization adds a user from your organization to the contact list, the presence information for the new contact appears as "Status Unknown." However, you expect the correct presence information to appear for users who are federation-enabled.

CAUSE

This problem occurs because of a problem in how Live Communications Server 2005 works with SQL Server 2005. In the scenario that is described in the "Symptoms" section, Live Communications Server 2005 does not set the Federation flag correctly when Live Communications Server 2005 uses SQL Server 2005 as the back-end database.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

You must have the following items installed to apply this hotfix:

  • Live Communications Server 2005 Service Pack 1 (SP1). For more information, click the following article number to view the article in the Microsoft Knowledge Base:

    897674 How to obtain Live Communications Server 2005 Service Pack 1

  • The update that is mentioned in the following Microsoft Knowledge Base article:

    911996 Description of the update for Live Communications Server 2005: February 10, 2006, rereleased July 11, 2006

Restart requirement

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

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.

File name File version File size Date Time Platform
Wrtces.dll 2.0.5470.1035 654,600 23-Oct-2006 20:10 x86

Hotfix installation information

You must apply this hotfix to Live Communications Server 2005 Enterprise Edition front-end servers and to Live Communications Server 2005 Standard Edition servers.

WORKAROUND

To work around this problem, enable both Federation and Public Instant Messaging Connectivity (PIC) for users whose presence is displayed as "Status Unknown." Only use this workaround in organizations that do not use PIC. In organizations that do use PIC, only use this workaround for users who you want to have PIC access.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



Additional query words: LCS2005 LCS

Keywords: kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB924604