XP Service Pack 3 and Easy Print
I have successfully installed XP Service Pack 3 AND the dot net framework 3.5 runtime onto an XP machine.
I am pleased to say that for the most part, easy print is working wonderfully - with one caveat.
I have customers with receipt printers and when I print directly to the printer (which I must) - it does not work - and in fact gives me an error. The SAME program when using Vista with SP1 remote desktop to this terminal server - the printer works fine.
The dialog returned says this when using Windows XP:
--------------------------------
Windows Presentation Foundation Terminal Server Print W
Windows Presentation Foundation Terminal Server Print W has encountered a problem and needs to close. We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem.
.....
----------------------------------
We have sent the error reports.
How can I log a bug for this? I have about 200 customers who will need this functionality working. (since they cannot all upgrade their clients to Vista right away)
We even used this sample from MSDN:ms-help://MS.VSCC.v80/MS.MSDN.v80/MS.WIN32COM.v10.en/gdi/prntspol_93g2.htm
It failed under XP using remote desktop (easy print) but ran fine under Vista (using Remote Desktop to the Terminal Server 2008 server) (easy print)
Does anyone have any suggestions?
Thanks!
=-Chris
답변
Hlo Christopher, please follow-up with MS Product Support here :
https://support.microsoft.com/oas/default.aspx?gprid=1173
- Hambone and Matusco, I was running into the very same problem after performing the same troubleshooting steps with the same versions/service packs of XP and .Net.
I could print just fine locally from the client machine, and the Terminal Server was creating all of the appropriate printers in my RDP sessions, but printing to redirected USB printer (HP LaserJet M1522 MFP) was exhibiting the same behavior you were seeing. After installing KB946411, I saw the error message go away as you did, but nothing would be sent to the print spooler on the client machine.
Since I was redirecting all of the client printers, I then attempted to print a test page using the redirected XPS printer instead. This brought up the appropiate dialog box on the client machine, and created the .XPS document as I expected to see it (showing the printer model as Terminal Services Easy Print). At that point, it was clearly a problem with the client's printer driver/config, so I did the following on the client machine:
Close all open RDP sessions
Open the printer properties for the locally attached HP printer
Advanced Tab
New Driver
Selected the *exact* same driver I had already been using, and clicked next/finish/ok or whatever until the wizard was done.
Clicked OK to get out of the printer properties
RDP-ed back in and confirmed that the redirected HP printer was finally working.
Hope that helps!- 답변으로 제안됨Andy Simmons 2009년 6월 12일 금요일 오후 10:56
- 답변으로 표시됨Christa AndersonMSFT, 중재자2009년 6월 12일 금요일 오후 11:52
모든 응답
Hlo Christopher, please follow-up with MS Product Support here :
https://support.microsoft.com/oas/default.aspx?gprid=1173
- I have the same error message when client tries to print to local printer HP Color LaserJet 3600.
- I also have the same error message when printing to a HP Color LaserJet 4600, it works correctly with my Vista SP1 install but not with staff running XP SP3 w/ .NET 3.5
- Hello, I had the same proble. Do you use Nod32? Because switch off Amon/network drives scaning solved me the problem.
- I have the same issue XPP SP3 w/ .NET 3.5 Laserjet 4100 and 4200.
Update: 4-28-08 still have issue. Here is deal:
Win xpp w/SP3 & .Net 3.5 (.net 3.0 sp1) using easy print
and the remote printer is IP based,
but the Server can not ping that IP based printer
- you get the ERROR starting this thread.
No fix yet from MS XPP support.
MS said to install .Net 3.0 SP1 on the Server (says required if using server to RDP to another server) and KB946411 (fixes XPS files printing funny) - had to call MS to get this hotfix. Not yet tested.- 편집됨dave davie 2008년 7월 29일 화요일 오전 12:26Update still outstanding issue
- 편집됨dave davie 2008년 8월 1일 금요일 오후 8:42Updated 8/1/08
- Anyone got a solutions to this yet? I have exactly the same issue, I have upgrade some client workstations to XP SP3 with the .net framework 3.5 SP1 installed. I tried the above hotfix but, it did not fix the problem although the error message no longer pops up. But it still does not print....
- Has anyone got a solution for this yet? I have the same issue on a 2008 server and xp sp3 .net 3.5 machines. funny thing is it's only 4 machines out of 70 that are effected and the same SOE on each machine.
- We have found that MANUALLY installing TS Client 6.1 AND .Net 3.0 SP1 resolved virtually all of our Easy Print problems... You would think that .Net 3.5 would "cover" whatever functionality is in 3.0 SP1, but it doesn't, not in this case...
So try that -- do BOTH those things (both of those are easily downloadable) and then try Easy Print again... It worked for us... - I can get easy print to work without an issue using sp3 and .net 3.5 but i get a presentation printing issue on some machines only but they do still print, same application that all machines use
- I was having this error message appear on some of my machines. After I applied KB946411 the error message went away.
- Just to confirm prior postings, installation of TS Client 6.1 and at least .Net 3.0 SP1 creates a working enviroment for Easy Print with the really annoying error meassage after EVERY print command detailing the presentation printing issue. The application of KB946411 cleared up the problem.
- SORRY, AND XP SP3.
- I had this issue on several XP SP3 machines trying to print from TS2008 and solved it completely by replacing TsWpfWrp.exe with one from a vista SP1 machine....worked for every one.
- We have this issue also on one machine so far. The client machine has XP SP3, .NET 3.5SP1, .NET 3.0 SP2. When they try to print from a Windows 2008 TS (.NET 3.5 SP1 installed on server), they get the error message “Windows Presentation Foundation Terminal Server Print W has encountered a problem and needs to close. We are sorry for the inconvenience”, and nothing prints. We found this blog, so we first applied KB946411 to the client machine. After applying this fix, the user no longer gets the error message, but nothing prints. We put the original TsWpfWrp.exe (version 1109) back in place, then we get the error message and it does not print. Then we copied the TsWpfWrp.exe from a Windows Vista SP1 machine that has .NET 3.5 SP1 installed to the XP client machine. After applying the Vista version of the file, we get no error message, and it does not print.
We know it is not the Terminal Server because others can perform the same exact function from other machines. We have also eliminated the printer by doing the same function to the same printer from another machine, and it printed successfully. So that pretty much narrows it down the the lone client machine. But I don't know what else to try at this point. Any ideas?
Thanks in advance for your help. - Hi I need help with the same problem (same like hambonegt),
client side: Win XP Home Edition SP3, .Net Framework 3.5 SP1 (also 2.0 SP2, 3.0 SP2)
server side : Win 2008 Standard SP1, .Net Framework 3.5 SP1.
using Easy Print Driver first
After printing user gets error: "Windows Presentation Foundation Terminal Server Print W has encountered a problem and needs to close".
I've tried to replace TsWpfWrp.exe from Vista SP1 and also to install KB946411-x86.exe. Nothing works, nothing prints and now we also get no error message (like hambonegt)
I don't know what to do, thanks for your help. - Hambone and Matusco, I was running into the very same problem after performing the same troubleshooting steps with the same versions/service packs of XP and .Net.
I could print just fine locally from the client machine, and the Terminal Server was creating all of the appropriate printers in my RDP sessions, but printing to redirected USB printer (HP LaserJet M1522 MFP) was exhibiting the same behavior you were seeing. After installing KB946411, I saw the error message go away as you did, but nothing would be sent to the print spooler on the client machine.
Since I was redirecting all of the client printers, I then attempted to print a test page using the redirected XPS printer instead. This brought up the appropiate dialog box on the client machine, and created the .XPS document as I expected to see it (showing the printer model as Terminal Services Easy Print). At that point, it was clearly a problem with the client's printer driver/config, so I did the following on the client machine:
Close all open RDP sessions
Open the printer properties for the locally attached HP printer
Advanced Tab
New Driver
Selected the *exact* same driver I had already been using, and clicked next/finish/ok or whatever until the wizard was done.
Clicked OK to get out of the printer properties
RDP-ed back in and confirmed that the redirected HP printer was finally working.
Hope that helps!- 답변으로 제안됨Andy Simmons 2009년 6월 12일 금요일 오후 10:56
- 답변으로 표시됨Christa AndersonMSFT, 중재자2009년 6월 12일 금요일 오후 11:52
Thanks Andy Simmons, work like a charm
- i had update NOD32 on the 2008 server yesterday. if you uncheck the scan network drives. this fix my problem!
