Article ID: 903932 - Last Review: October 9, 2011 - Revision: 2.0 You may receive an error message when you try to print a document to a network shared printer from a computer that is running Windows 2000
Important This article contains information that shows you how to help
lower security settings or how to turn off security features on a computer. You
can make these changes to work around a specific problem. Before you make these
changes, we recommend that you evaluate the risks that are associated with
implementing this workaround in your particular environment. If you implement
this workaround, take any appropriate additional steps to help protect your
system. On This PageSYMPTOMSWhen you print a document to a network shared printer from a
computer that is running Microsoft Windows 2000, the print job does not produce
output. You may receive an error message that states that you cannot print a
document or that you have an invalid printer. The exact error message varies
depending on the application that you use to submit the print job. This problem
does not occur if you log on to the computer by using an administrative
account. You may receive one of the following symptoms, depending on your application:
CAUSEThis problem typically occurs when the following conditions
are true:
The .bud file is not created or updated when you push the Windows Server 2003 version of the printer driver from the print server to the computer where you are running the application. When you try to use a printer when a .bud file is missing or does not match the .gpd file, the Printer Spooler service will create or re-create the .bud file. However, if you do not have the permissions to create or re-create the .bud file, the problem occurs. Note The .bud file is a binary version of the generic printer description file (.gpd) that is included with many printer drivers. The .bud file is located in the Windows\System32\Spooler\Drivers\W32x86\3 folder. RESOLUTIONHotfix informationA 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 this specific problem.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, submit a request to 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
(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.PrerequisitesNo prerequisites are required.Restart requirementYou must restart the Print Spooler service after you apply the hotfix.Hotfix replacement informationThis hotfix replaces the hotfix that is described in the following Knowledge Base article:873396
(http://support.microsoft.com/kb/873396/
)
You receive an error message if you try to print a document on Windows 2000-based and Windows XP-based computers (873396)
File informationThe 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 tool in Control Panel.Windows 2000 Service Pack 4Collapse this table
WORKAROUNDWarning This workaround may make your computer or your network more
vulnerable to attack by malicious users or by malicious software such as
viruses. We do not recommend this workaround but are providing this information
so that you can implement this workaround at your own discretion. Use this
workaround at your own risk. To work around this problem, grant write permission to the Windows\System32\Spooler\Drivers\W32x86\3 folder and its subfolders. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.The issue is a spooler limitation
that is fixed in Windows Server 2003 Service Pack 1. There
is no hotfix for the original version of Windows Server 2003. MORE INFORMATION For more information, click the
following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
| Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top