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: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.

Back to the top

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.

Back to the top

Hotfix information

Back to the top

Windows Server 2003

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 this specific problem. 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: 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

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 Server 2003, Itanium-based versions

File name	File version	File size	Date	Time	Platform	Service branch
Localspl.dll	5.2.3790.220	860,160	30-Sep-2004	08:32	IA-64	RTMQFE
Spoolss.dll	5.2.3790.212	233,984	30-Sep-2004	08:32	IA-64	RTMQFE

Windows Server 2003, x86-based versions

File name	File version	File size	Date	Time	Platform	Service branch
Localspl.dll	5.2.3790.220	312,320	30-Sep-2004	23:28	x86	RTMQFE
Spoolss.dll	5.2.3790.212	81,408	30-Sep-2004	23:28	x86	RTMQFE

Back to the top

Windows 2000

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 this specific problem. 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: 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, you must have Windows 2000 Service Pack 3 (SP3) installed.

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

File name	File version	File size	Date	Time	Platform	Service branch
Basesrv.dll	5.0.2195.6824	42,256	20-Nov-2003	22:59	x86	Not Applicable
Cmd.exe	5.0.2195.6824	236,304	21-Sep-2003	00:45	x86	Not Applicable
Faxui.dll	0.2.0.1	138,000	20-Nov-2003	22:59	x86	Not Applicable
Gdi32.dll	5.0.2195.6824	222,992	20-Nov-2003	22:59	x86	Not Applicable
Kernel32.dll	5.0.2195.6867	711,440	20-Nov-2003	22:59	x86	Not Applicable
Localspl.dll	5.0.2195.6876	252,688	20-Nov-2003	22:59	x86	Not Applicable
Mpr.dll	5.0.2195.6824	54,032	20-Nov-2003	22:59	x86	Not Applicable
Msgina.dll	5.0.2195.6876	334,096	20-Nov-2003	22:59	x86	Not Applicable
Rdpwd.sys	5.0.2195.6824	90,232	20-Nov-2003	22:59	x86	Not Applicable
Sp3res.dll	5.0.2195.6870	5,847,552	06-Nov-2003	22:29	x86	Not Applicable
Spoolss.dll	5.0.2195.6876	80,144	20-Nov-2003	22:59	x86	Not Applicable
User32.dll	5.0.2195.6869	380,176	20-Nov-2003	22:59	x86	Not Applicable
Userenv.dll	5.0.2195.6871	389,392	20-Nov-2003	22:59	x86	Not Applicable
Win32k.sys	5.0.2195.6869	1,628,816	31-Oct-2003	03:02	x86	Not Applicable
Win32spl.dll	5.0.2195.6824	87,312	20-Nov-2003	22:59	x86	Not Applicable
Winlogon.exe	5.0.2195.6873	182,032	11-Nov-2003	00:29	x86	Not Applicable
Winsrv.dll	5.0.2195.6873	243,984	20-Nov-2003	22:59	x86	Not Applicable
Kernel32.dll	5.0.2195.6867	711,440	20-Nov-2003	22:59	x86	UNIPROC
Win32k.sys	5.0.2195.6869	1,628,816	31-Oct-2003	03:02	x86	UNIPROC
Winsrv.dll	5.0.2195.6873	243,984	20-Nov-2003	22:59	x86	UNIPROC

Back to the top

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

Back to the top

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base: For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top