Issues in OCS 2007/ LCS 2005 caused by applying KB974571

  • Article

This is my first OCS related post.

In this first post I would to make available the information regarding KB974571 and the disruption it causes to OCS and LCS systems.

The KB is now on version 4.0 and it was re-writen to face the errors stated from our customers. 

Kb is available at : https://support.microsoft.com/kb/974571/en-us .

This revision, 4.0, has this new content, which is especially usefull for OCS and LCS administrators :

Known issues that affect this security update

Services that are required by Communications Server are not started after you install this update and then restart a computer that is running any of the following versions of Communications Server:

  • Live Communications Server 2005 (LCS)
  • Live Communications Server 2005 SP1
  • Office Communications Server 2007 Enterprise edition (OCS)
  • Office Communications Server 2007 Standard edition
  • Office Communications Server 2007 R2 Enterprise edition
  • Office Communications Server 2007 R2 Standard edition
  • Office Communicator 2007 Evaluation version only*
  • Office Communicator 2007 R2 Evaluation version only*

*The licensed production version of this application is not affected by this known issue. Only Office Communicator clients that are in their 180-day evaluation period are affected by this issue.
When this problem occurs, the following error events are logged in the Application logs in the Event Viewer of the affected servers:

  • Live Communications Server 2005 Event Type: Error
    Event Source: Live Communications Server
    Event Category: (1000)
    Event ID: 12290
    Date: Date
    Time: Time
    User: N/A
    Computer: Computer
    Description:
    The evaluation period for Microsoft Office Live Communication Server 2005 has expired. Obtain the released version of this product and upgrade to the non-evaluation version by running setup.exe.
  • Office Communications Server 2007 Log Name: Office Communications Server
    Source: OCS Server
    Date: Date
    Event ID: 12290
    Task Category: (1000)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Computer
    Description:
    The evaluation period for Microsoft Office Communications Server 2007 R2 has expired. Please upgrade from the evaluation version to the full released version of the product.
    Log Name: Office Communications Server
    Source: OCS Server
    Date: Date
    Event ID: 12299
    Task Category: (1000)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Computer
    Description:
    The service is shutting down due to an internal error.
    Error Code: C3E93C23 (SIPPROXY_E_INVALID_INSTALLATION_DATA)
    Cause: Check the previous entries in the event log for the failure reason.
    Resolution:
    Check the previous event log entries and resolve them. Restart the server. If the problem persists, contact Product Support Services.

When this problem occurs, the required services behave as if an expired trial version of the product is installed. This behavior affects the whole Communications Server enterprise that is hosted by the affected server or servers.
Microsoft is investigating this issue, and will determine the most appropriate way to address it. Customers who are not running OCS or LCS server are not affected by this known issue, and can safely ignore this issue.
Customers who have deployed the OCS or LCS product on a server should assess the risk that is involved to decide whether to install the security update on that server. These customers should revisit this Knowledge Base article often, because this article will be updated as soon as more information and a resolution are available.

========== | ========== | ========== | ========== | ===========

Thus far, the only solution for this is to remove the KB and reboot the server.

- UPDATED - FIX AVAILABLE AT :

UPDATE - Issues in OCS 2007/ LCS 2005 caused by applying KB974571
https://blogs.technet.com/jribeiro/archive/2009/11/05/update-issues-in-ocs-2007-lcs-2005-caused-by-applying-kb974571.aspx

So being, I strongly encourage evryone to check the KB regularly, as new information may become available.