You receive an error message when you try to print to a shared network printer in a terminal server

Microsoft states in 824684

You receive an error message when you try to print to a shared network printer in a terminal server session
View products that this article applies to.
SYMPTOMS
When you are connected to a terminal server session on a Microsoft Windows 2000-based computer or a Microsoft Windows Server 2003-based computer, and you try to print from any program to a shared network printer, you may receive an error message that is similar to one of the following:

No printers are installed. To install a printer, point to settings on the Windows Start Menu, click Printer, and then double-click Add Printer. Follow the instructions in the wizard.

Current printer is unavailable. Select another printer.

Before you can print, you need to select a printer. If you need to install a printer, either double-click the Add Printer icon or click the Find Printer button located on the general tab of this dialog.
Error messages vary from program to program.

After you receive one of these error messages and then click OK, the Printer dialog box may open. If you select the same printer that caused the error message, the Print and Apply buttons are not available, and you cannot print. If you select a different printer, you may be able to print.
CAUSE
This problem may occur if another user logs on to the terminal server, and the user has a later version of the same printer driver installed on their computer. When the print spooler detects the new driver on the terminal server, the spooler creates a new binary data file for the later version of the printer driver. When you try to print from a program in your terminal server session, you cannot access the new binary data file because the earlier version of the printer driver is installed on your computer.

Binary data files are temporary files that the Universal Printer Driver (Unidrv) creates after it parses information that is contained in minidriver text files. The Universal Printer Driver (Unidrv) is the standard printer driver that Microsoft uses for non-PostScript printers. Unidrv binary data files have a .bud file name extension.
RESOLUTION
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 or Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
No prerequisites are required.
Restart Requirement
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix does not replace any other hotfixes.
File Information
The English version of this hotfix has the file attributes (or later) 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
Date Time Version Size File name
--------------------------------------------------------------
20-Nov-2003 22:59 5.0.2195.6824 42,256 Basesrv.dll
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
20-Nov-2003 22:59 0.2.0.1 138,000 Faxui.dll
20-Nov-2003 22:59 5.0.2195.6824 222,992 Gdi32.dll
20-Nov-2003 22:59 5.0.2195.6867 711,440 Kernel32.dll
20-Nov-2003 22:59 5.0.2195.6876 252,688 Localspl.dll
20-Nov-2003 22:59 5.0.2195.6824 54,032 Mpr.dll
20-Nov-2003 22:59 5.0.2195.6876 334,096 Msgina.dll
20-Nov-2003 22:59 5.0.2195.6824 90,232 Rdpwd.sys
06-Nov-2003 22:29 5.0.2195.6870 5,847,552 Sp3res.dll
20-Nov-2003 22:59 5.0.2195.6876 80,144 Spoolss.dll
20-Nov-2003 22:59 5.0.2195.6869 380,176 User32.dll
20-Nov-2003 22:59 5.0.2195.6871 389,392 Userenv.dll
31-Oct-2003 03:02 5.0.2195.6869 1,628,816 Win32k.sys
20-Nov-2003 22:59 5.0.2195.6824 87,312 Win32spl.dll
11-Nov-2003 00:29 5.0.2195.6873 182,032 Winlogon.exe
20-Nov-2003 22:59 5.0.2195.6873 243,984 Winsrv.dll
20-Nov-2003 22:59 5.0.2195.6867 711,440 Kernel32.dll
31-Oct-2003 03:02 5.0.2195.6869 1,628,816 Win32k.sys
20-Nov-2003 22:59 5.0.2195.6873 243,984 Winsrv.dll
20-Nov-2003 23:08 12,866 Kb831754.cat

Windows Server 2003
Date Time Version Size File name Platform
------------------------------------------------------------------
08-Dec-2003 22:14 5.2.3790.110 859,136 Localspl.dll IA-64
08-Dec-2003 22:14 5.2.3790.110 233,472 Spoolss.dll IA-64
06-Dec-2003 01:17 271 Branches.inf
08-Dec-2003 22:26 10,165 Kb831754.cat
08-Dec-2003 22:20 354 Updatebr.inf
08-Dec-2003 22:20 5,971 Update_rtmqfe.inf
Date Time Version Size File name
--------------------------------------------------------------
08-Dec-2003 22:12 5.2.3790.110 311,296 Localspl.dll
08-Dec-2003 22:12 5.2.3790.110 80,896 Spoolss.dll
06-Dec-2003 01:30 271 Branches.inf
08-Dec-2003 22:26 10,165 Kb831754.cat
08-Dec-2003 22:16 354 Updatebr.inf
08-Dec-2003 22:16 5,951 Update_rtmqfe.inf
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for
Microsoft Windows software update packages

For additional information, 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

The information in this article applies to:
Microsoft Windows Server 2003, Enterprise Edition
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Advanced Server



Primary links

Custom Search

Who's new

  • maczugaher
  • locksgydff
  • isotheces
  • ahundredyears7
  • Jacomijntjefu

Who's online

There are currently 0 users and 5 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.