MGCTech
asked on
Printing problems on Windows Server 2003 SP2 x64 in Terminal Services mode
Windows Server 2003 SP2 x64 in Terminal Services mode can only print plain text documents from Notepad or Wordpad or Windows Printer Test Pages from the console as Administrator, but can print any documents when logged in via Terminal Services / Remote Desktop as any user including Administrator. This started on 2/4/09. That day, .NET Framework 2.0 and 3.0 were installed.
When attempting to print a web page from FireFox while logged into the console as Administrator, an error message comes up stating "You may not be able to print after installing .NET F..." The rest of the message is truncated and the wording may not be exact.
Hotfix 944203 from Microsoft has been applied and re-applied with no change.
When attempting to print a web page from FireFox while logged into the console as Administrator, an error message comes up stating "You may not be able to print after installing .NET F..." The rest of the message is truncated and the wording may not be exact.
Hotfix 944203 from Microsoft has been applied and re-applied with no change.
ASKER
There are no printer-related errors in the event viewer, other than the usual ones when a client connects via RDP with a printer for which the server has no driver.
The print spooler service is running.
Yes, the server has been restarted.
Let me know what other info you need and I'll post it.
Thanks!
The print spooler service is running.
Yes, the server has been restarted.
Let me know what other info you need and I'll post it.
Thanks!
When you applied the hotfix, did you check the file version on unidrv.dll, and unidrvui.dll so that those where the same version as in the hotfix?
have you installed any print drivers just before the .net installation or after that uses the above files? since unidrv.dll is commonly used by many drivers maybe those have been updated by another driver and therefore the hotfix is not applied (no replace when version is newer on existing file)
can you check the file version on those two files above? you will find them in the spool\drivers folder on the server.
/ Mikael
have you installed any print drivers just before the .net installation or after that uses the above files? since unidrv.dll is commonly used by many drivers maybe those have been updated by another driver and therefore the hotfix is not applied (no replace when version is newer on existing file)
can you check the file version on those two files above? you will find them in the spool\drivers folder on the server.
/ Mikael
ASKER
I did check the unidrv.dll and unidrvui.dll versions. The first time, they were later than what was specified in the KB article, so I renamed those ones to *.old and then applied the hotfix again, which did give us the versions we were expecting, but did not resolve the issue.
There's another hotfix (KB961118), which I'll be applying early next week. If that doesn't resolve the issue, I'll try uninstalling .NET Framework 3.5 to see if that solves the problem. If not, then uninstalling .NET Framework 3.0.
Thanks for your suggestions. I'll post the results next week.
There's another hotfix (KB961118), which I'll be applying early next week. If that doesn't resolve the issue, I'll try uninstalling .NET Framework 3.5 to see if that solves the problem. If not, then uninstalling .NET Framework 3.0.
Thanks for your suggestions. I'll post the results next week.
ASKER
Used method 1 and method 2 in KB923100 to remove .NET Framework and then reinstalled just version 1.1.
Unfortunately, that has not changed the status of the issue.
Unfortunately, that has not changed the status of the issue.
ASKER
Reinstalled .NET Framework 2.0, 3.0 and 3.5 and applied hot fix KB961118.
Still no change.
Any thoughts?
Still no change.
Any thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are the print spooler service running on the server?
Do you get any other printer related errors in the eventviewer?
post some more info and we continue from there
/ Mikael