FIX: An update is available for HPC Pack 2008 R2: July 2013

View products that this article applies to.

Introduction

This article describes an update that fixes some issues in Microsoft HPC Pack 2008 R2. See the "Issues that are fixed in this update" section for more information.

↑ Back to the top

More Information

Update information

A supported update is available from Microsoft. However, this update is intended to correct only the problems that are described in this article. Apply this update only to systems that are experiencing any of these problems described in this article. This update 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 update.

If this update 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 this update.

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, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support

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 an update is not available for that language.

Prerequisites

To install this update, you must have Service Pack 4 for HPC Pack 2008 R2 installed.

Restart information

You must restart the computer after you apply this update.

Replacement information

This update does not replace any previously released update.

↑ Back to the top

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
Clustermanagementinterfaces	3.3.3957.0	11,776	07-Mar-2012	17:43	Not applicable
Clustermodel	3.3.3957.0	643,072	07-Mar-2012	17:43	Not applicable
Configurationservice	3.3.3957.0	233,472	07-Mar-2012	17:43	Not applicable
Hpc.nodemanagement	3.3.3957.0	9,728	07-Mar-2012	18:17	Not applicable
Hpc.scheduler	3.3.3957.0	204,800	07-Mar-2012	18:17	Not applicable
Hpcschedulercore.dll	3.3.3957.0	999,424	07-Mar-2012	17:43	x86
Microsoft.hpc.azuremanagementbroker.dll	3.3.3957.0	126,976	07-Mar-2012	17:42	x86
Microsoft.hpc.scheduler.communicator.azure.dll	3.3.3957.0	114,688	07-Mar-2012	17:43	x86
Microsoft.hpc.scheduler.nodemanagement.sdm.dll	3.3.3957.0	15,360	07-Mar-2012	17:43	x86

↑ Back to the top

Issues that are fixed in this update

This update fixes the following issues that were not previously documented in the Microsoft Knowledge Base:

Issue 1

Regularly scheduled jobs that are burst in Microsoft Azure are marked as failed even when all tasks are finished successfully.

↑ Back to the top

Issue 2

A job is not scheduled to the Microsoft Azure nodes after it is redeployed.

Issue 3

The HPC Management Service leaves a large memory footprint together with multiple availability policies.

Issue 4

A back-end delete may unexpectedly deploy an operation jump-in too frequently or too early to delete correct deployments.

Issue 5

The Scheduler locks a resource in idle mode even when the node is put in offline mode.

Issue 6

The HPC Management Service does not obtain the event to update the Scheduler properties mapping cache. The Scheduler event is not guaranteed in all conditions. The service does not dirty the cache when the Scheduler client is disconnected from the server.

Issue 7

A regularly scheduled job that is burst in Microsoft Azure may fail even when all tasks are finished successfully. Additionally, you receive the following error message:

The job was cancelled by the scheduler.

Issue 8

A deployment may encounter a 409 (conflict) issue with Microsoft Azure when you try to move a deployment to the Run state.

Issue 9

The HPC Management Service sends duplicate InitTakingOffline operations if a previous InitTakingOffline operation does not finish within one minute.

Issue 10

The node cache in the Scheduler is not in sync with the database. Therefore, the Scheduler always assumes that a node has an ID that does not exist any longer.

↑ Back to the top