Conectați-vă cu Microsoft
Conectați-vă sau creați un cont
Salut,
Selectați un alt cont.
Aveți mai multe conturi
Alegeți contul cu care doriți să vă conectați.
Engleză
Ne pare rău. Acest articol nu este disponibil în limba dvs.

Symptoms

Consider the following scenario:

  • You create a failover cluster on some computers that are running Windows Server 2008 R2.

  • The names of these computers contain 15 characters or more.

  • You create a clustered print spooler and some print queues.

  • You use the Printer Migration Wizard or the Printbrm.exe command-line tool to back up a clustered print server on a cluster node.

In this scenario, the backup process fails. Additionally, you receive the following error message:

The following error occurred: 0x800700ea.
More data is available.

Cause

This issue occurs because a buffer that is used by the Printbrm.exe command-line tool is too small to handle a computer name that contains 15 characters or more.

Resolution

To resolve this issue, install the following hotfix on all affected cluster nodes.

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=supportNote 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, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    0.16xxx

    Windows Server 2008 R2

    RTM

    GDR

    6.1.760
    0.21xxx

    Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.17xxx

    Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.21xxx

    Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 name

File version

File size

Date

Time

Platform

Printbrm.exe

6.1.7600.16385

21,504

14-Jul-2009

01:39

x64

Printbrmengine.exe

6.1.7600.21040

267,264

31-Aug-2011

07:12

x64

Printbrmps.dll

6.1.7600.16385

19,456

14-Jul-2009

01:41

x64

Printbrmui.exe

1.0.0.0

71,680

14-Jul-2009

01:39

x64

Printbrm.exe

6.1.7600.16385

21,504

14-Jul-2009

01:39

x64

Printbrmengine.exe

6.1.7601.21805

267,264

31-Aug-2011

08:23

x64

Printbrmps.dll

6.1.7600.16385

19,456

14-Jul-2009

01:41

x64

Printbrmui.exe

1.0.0.0

71,680

14-Jul-2009

01:39

x64

Status

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

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 name

Amd64_0be5da13aed7498011fc492917ed4b26_31bf3856ad364e35_6.1.7601.21805_none_05291095e027b199.manifest

File version

Not applicable

File size

715

Date (UTC)

31-Aug-2011

Time (UTC)

22:25

Platform

Not applicable

File name

Amd64_624efaaddc4615c24b1316b10dfb87b1_31bf3856ad364e35_6.1.7600.21040_none_431ddb29caaa9dc7.manifest

File version

Not applicable

File size

715

Date (UTC)

31-Aug-2011

Time (UTC)

22:25

Platform

Not applicable

File name

Amd64_microsoft-windows-p..ting-tools-printbrm_31bf3856ad364e35_6.1.7600.21040_none_de5ed6c4780770c9.manifest

File version

Not applicable

File size

76,924

Date (UTC)

31-Aug-2011

Time (UTC)

22:25

Platform

Not applicable

File name

Amd64_microsoft-windows-p..ting-tools-printbrm_31bf3856ad364e35_6.1.7601.21805_none_e0759eb07508b589.manifest

File version

Not applicable

File size

76,924

Date (UTC)

31-Aug-2011

Time (UTC)

22:25

Platform

Not applicable

File name

PUpdate.mum

File version

Not applicable

File size

2,924

Date (UTC)

31-Aug-2011

Time (UTC)

22:25

Platform

Not applicable

Aveți nevoie de ajutor suplimentar?

Doriți mai multe opțiuni?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Au fost utile aceste informații?

Ce v-a afectat experiența?
Apăsând pe Trimitere, feedbackul dvs. va fi utilizat pentru a îmbunătăți produsele și serviciile Microsoft. Administratorul dvs. IT va avea posibilitatea să colecteze aceste date. Angajamentul de respectare a confidențialității.

Vă mulțumim pentru feedback!

×