Article ID: 2407374 - Last Review: November 3, 2010 - Revision: 2.0

Certain Office Communications Server 2007 R2 services do not start on a computer that has more than 16 CPU cores

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

When you install Microsoft Office Communications Server 2007 R2 front-end server on a computer that has more than 16 CPU cores, you find that the following services do not start:
  • A/V Conferencing service
  • Application Sharing service
  • Conferencing Announcement service
  • Conferencing Attendant service
  • Monitoring Agent service
  • Outside Voice Control service
  • Response Group service
Additionally, you may find an event log that resembles the following on the front-end server:

Log Name: Office Communications Server
Source: OCS ApplicationSharing Conferencing Server
Date: <Date & Time>
Event ID: 32010
Task Category: (1304)
Level: Error
Keywords: Classic
User: N/A
Computer: <Server Name>
Description:
The description for Event ID 32010 from source OCS ApplicationSharing Conferencing Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

 

RESOLUTION

To fix this problem, install the following cumulative update:
2400399  (http://support.microsoft.com/kb/2400399/ ) Description of the cumulative update for Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core Redist 64-bit: September 2010

STATUS

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

APPLIES TO
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
  • Microsoft Office Communications Server 2007 R2 Standard Edition
Keywords: 
kbfix kbsurveynew kbexpertiseinter KB2407374