Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Update for HPC Pack 2012 R2: April 2014


View products that this article applies to.

Summary

This update fixes a task dependency issue in the Microsoft HPC Pack 2012 R2 job scheduler that causes tasks to fail. Check out the fixed issue and the update information in this update.

↑ Back to the top


Issue that is fixed in this update

When you add a task that has multiple dependencies to a submitted job in an HPC Pack 2012 R2 cluster, the task fails. Additionally, you receive the following error message:
Invalid task dependency: no basic or parametric task named 'TaskName' could be found in the job. A task may only depend on another basic or parametric task. Please check your spelling and try again.

↑ Back to the top


Resolution

Update information

This update is available for download from the following Microsoft Download Center website:

Installation instructions

This update must be run only on head nodes.
We recommend that you stop all active jobs, and then back up the head node and the HPC database before installing or uninstalling the update.

Note If you have high availability head nodes, run the fix on the active head node, and then move the node to passive. After failover occurs, run the fix on the new active head node. Do this for all head nodes in the cluster.
Prerequisites
To apply this update, you must be running Windows Server 2012 R2 or Windows Server 2012.
Restart requirement
You may have to restart the computer after you apply this update.

Uninstall information

To uninstall the update, in Control Panel, click Programs select View installed updates, and double-click HotFix KB2956330 for Microsoft HPC Pack 2012 R2.

Note If you have high availability head nodes, uninstall the update on a passive head node, and then move the node to active. Then you should repeat the uninstallation on the new passive head node. Do this for all head nodes in the cluster.

↑ Back to the top


Status

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

↑ Back to the top


Keywords: kb, kbqfe, kbfix, kbsurveynew, atdownload

↑ Back to the top

Article Info
Article ID : 2956330
Revision : 1
Created on : 1/7/2017
Published on : 5/7/2014
Exists online : False
Views : 237