Microsoft KB Archive Search

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.

  1. Home
  2. Stability update for Windows Server 2008 R2 Failover Print Clusters

Stability update for Windows Server 2008 R2 Failover Print Clusters

View products that this article applies to.

Symptoms

This update fixes the following issues for print server failover clusters that are running Windows Server 2008 R2. We recommend that you install this update on all the print server failover cluster nodes that are running Windows Server 2008 R2 to make sure that basic functionality and that basic manageability is maintained.


Issue 1

Consider the following scenario:
  • A shared printer is installed on a print server failover cluster that is running Windows Server 2008 R2.
  • The print processor of the related driver has multiple dependent files.
  • The print server fails over to another node.
In this scenario, the shared printer may be missing on the new node after the failover operation.


Issue 2

Consider the following scenario:
  • A shared printer is installed on a print server failover cluster that is running Windows Server 2008 R2.
  • Some clients open connections to this shared printer.
  • The print server fails over to another node.
In this scenario, the spooler service may stop responding after this printer server resource fails over to another node. Therefore, all print jobs fail.


Issue 3

When you use the Print Back-up Restore Migrate utility (Printbrm.exe) to restore printers on a print server failover cluster that is running Windows Server 2008 R2, some printers cannot be restored, and you receive the following error message:
1081 invalid printer name

↑ Back to the top

Cause

Cause of issue 1

Only one dependent file is copied to the destination node in every failover operation. The printer is missing after the failover operation because some dependent files are not available.



Cause of issue 2

The print server failover cluster enters an infinite loop.



Cause of issue 3

In order to add the print processors to the print server failover cluster, the print spooler resource must first go offline and then come online. This issue occurs because the printer is restored before the print spooler resource comes back online.

↑ Back to the top

Resolution

Hotfix information

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

If the hotfix 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 the hotfix.

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, visit the following Microsoft Web site:
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 a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running Windows Server 2008 R2. Additionally, the Failover Clustering feature must be installed.

Restart requirement

You do not have to restart the computer if the Print Spooler service is stopped before you apply this update.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Win32spl.dll6.1.7600.20794751,10404-Sep-201006:11x64
Win32spl.dll6.1.7600.20794492,03204-Sep-201005:44x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Win32spl.dll6.1.7600.207941,512,96004-Sep-201005:24IA-64
Win32spl.dll6.1.7600.20794492,03204-Sep-201005:44x86

↑ 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

More Information

For more information about software update terminology, 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 file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_174b1605f26232c12d55b6efee689ba5_31bf3856ad364e35_6.1.7600.20794_none_897015457b71f83c.manifest
File versionNot Applicable
File size722
Date (UTC)07-Sep-2010
Time (UTC)15:04
PlatformNot Applicable
File nameAmd64_2f769c89a9ea81f837ecd10959347095_31bf3856ad364e35_6.1.7600.20794_none_cd7e7c35fb374cbe.manifest
File versionNot Applicable
File size722
Date (UTC)07-Sep-2010
Time (UTC)15:04
PlatformNot Applicable
File nameAmd64_a9079f83de747ac09dbec37ac9890918_31bf3856ad364e35_7.1.7600.20794_none_2944246b401ee3f1.manifest
File versionNot Applicable
File size1,086
Date (UTC)07-Sep-2010
Time (UTC)15:04
PlatformNot Applicable
File nameAmd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7600.20794_none_95e5fea7a3c1a472.manifest
File versionNot Applicable
File size10,428
Date (UTC)04-Sep-2010
Time (UTC)07:05
PlatformNot Applicable
File nameAmd64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_7.1.7600.20794_none_87567aed2ea84d41.manifest
File versionNot Applicable
File size6,373
Date (UTC)04-Sep-2010
Time (UTC)07:14
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,093
Date (UTC)07-Sep-2010
Time (UTC)15:04
PlatformNot Applicable
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7600.20794_none_a03aa8f9d822666d.manifest
File versionNot Applicable
File size10,426
Date (UTC)04-Sep-2010
Time (UTC)06:07
PlatformNot Applicable
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_7.1.7600.20794_none_91ab253f63090f3c.manifest
File versionNot Applicable
File size6,371
Date (UTC)04-Sep-2010
Time (UTC)06:08
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_ece035f2349b433511cfc3026749b535_31bf3856ad364e35_6.1.7600.20794_none_57346c3db1fee85b.manifest
File versionNot Applicable
File size1,084
Date (UTC)07-Sep-2010
Time (UTC)15:04
PlatformNot Applicable
File nameIa64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7600.20794_none_39c90719eb623c38.manifest
File versionNot Applicable
File size10,426
Date (UTC)04-Sep-2010
Time (UTC)06:53
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,463
Date (UTC)07-Sep-2010
Time (UTC)15:04
PlatformNot Applicable
File nameWow64_microsoft-windows-p..ooler-networkclient_31bf3856ad364e35_6.1.7600.20794_none_a03aa8f9d822666d.manifest
File versionNot Applicable
File size10,426
Date (UTC)04-Sep-2010
Time (UTC)06:07
PlatformNot Applicable

↑ Back to the top

Keywords: kbexpertiseadvanced, kbfix, kbbug, kbautohotfix, kbclustering, kbhotfixserver, kbqfe, kb, kbsurveynew

↑ Back to the top

Article Info
Article ID : 976571
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 288