Voltron5
asked on
PrintTicket provider failed to bind
I have 2 servers running Server 2012 Standard. 1 of those servers is used for RDS only. I have workers from multiple locations that run a program on the RDS server thru RdWeb. No issues there. However, when a worker tries to print a report, whether it's from a Windows 8 64 bit PC or a Windows 7 64 bit PC, the following error always comes up:
PrintTicket provider failed to bind to printer. Win32 error. Access is denied.
I have seen the Microsoft KB 2872151 article and ran the Microsoft Fixit 20112, but it still errors out. I've researched it online and saw a workaround using VS2013, but that program is not installed on our Server...only SQL Server Management Studio 2012.
Any suggestions would be greatly appreciated!
Dave
PrintTicket provider failed to bind to printer. Win32 error. Access is denied.
I have seen the Microsoft KB 2872151 article and ran the Microsoft Fixit 20112, but it still errors out. I've researched it online and saw a workaround using VS2013, but that program is not installed on our Server...only SQL Server Management Studio 2012.
Any suggestions would be greatly appreciated!
Dave
ASKER
Yes, it is a third party app that is accessed thru RDWeb. They are trying to print locally. They don't have any 32 bit machines. I've tried running in in IE 11 as well as Google Chrome, but the error message always pops up. They have to save it in Dropbox as a pdf, so that they can then download it and print locally.
Thanks for the update.
Have you ever had printing working with this 3rd party app? In the office does the app print ok?
http://searchvirtualdesktop.techtarget.com/tip/Five-reasons-printer-redirection-causes-Windows-printing-problems-in-RDS highlights the following relevant issues:
Is it running on a domain controller?
Have you given users permissions to print?
Just check that these are covered. Apologies if we're covering ground already travelled.
Have you ever had printing working with this 3rd party app? In the office does the app print ok?
http://searchvirtualdesktop.techtarget.com/tip/Five-reasons-printer-redirection-causes-Windows-printing-problems-in-RDS highlights the following relevant issues:
Is it running on a domain controller?
Have you given users permissions to print?
Just check that these are covered. Apologies if we're covering ground already travelled.
ASKER
It's a hit or miss when printing. Most of the time the error message comes up. There are no issues printing locally, only the remote people. I checked the link that you included and made 1 change to Group Policy. It seems the error message is gone, and it appears to print, but nothing prints. I checked out the local printer just in case, but it didn't print there either. I'm going to check for the 4th time on the drivers stored on the RDS and make sure there are no issues there. I will give an update as soon as I can. I really appreciate the help you have given on this!
Dave
Dave
ASKER
So, here's the latest. I open the application on the RDS-Server. I select the Report Viewer w/in the program. When I hit the Print button, nothing happens. (no printing or error message) If I go into the Select printer option (button next to the Print button), I can see my local printer with the (redirect #). I can select Properties and print a test page successfully. The RDS-Server is not a DC. As for giving Users permission to print, I added "Everyone" with Full access for the Printers folder. (C:\Windows\System32\Spool \Printers. I'm not sure what else I'm missing. I configured the 5 items in the Printer Redirection folder inside Group Policy on the RDS-Server to what I believe to be correct:
1 - Do not set default printer to be default printer in a session: Dissabled
2 - Do not allow client printer redirection: Disabled
3 - Use Remote Desktop Easy Print printer driver first: Enabled
4 - Specify RD Session Host server fallback printer driver behavior: Not Configured
5 - Redirect only the default client printer: Not configured. (i did try it Enabled, but no change)
I'm not sure what else I'm missing... Thoughts??
Dave
1 - Do not set default printer to be default printer in a session: Dissabled
2 - Do not allow client printer redirection: Disabled
3 - Use Remote Desktop Easy Print printer driver first: Enabled
4 - Specify RD Session Host server fallback printer driver behavior: Not Configured
5 - Redirect only the default client printer: Not configured. (i did try it Enabled, but no change)
I'm not sure what else I'm missing... Thoughts??
Dave
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Beyond Frustrated! I took your advice and published Word pad. NO issues printing. Went back into main program, nothing prints. Again, the only positive is that I don't receive an error message. So, it seems to be the Report viewer in the application. And here's another interesting tidbit... Apparently, one of the laptops can print using a USB printer, but won't print using the network printer. The local and remote network printers are Canon, but they are different models. They do however, have the same local static IP address. Now that I'm thinking about it more, the Canon at the remote location is using a UFR II XPS driver, instead of the normal PCL or PS. I'm going to install the Canon with a PCL driver and see what happens. I'll let you know...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm going to find out about the logs in the main program and check the Windows event viewer as well. I'm hoping to be on site tomorrow to install the drivers (locally) and check the logs. I'll let you know what happens.
Ok - I'll be monitoring :)
ASKER
Ok... I have added every PCL driver (x64 and x86) to the RDS Server Printer properties for the remote printer. Still no good. I checked the event viewer on a remote workstation after I received the error. There is no error or warning in this viewer. Checked the event viewer on the RDS server... Event ID 122...Access to Drivers on Windows Update Blocked by Policy. I corrected the policy to Always install from Windows Update. Still no good. There's no other error in any part of the event viewer tied to Remote, printing, or terminal services. I believe this issue is with the company whose program is being run. I am going to contact them again and let them know that I can print from other apps, just not theirs. I'll keep you posted.
That's exactly what we were after, in that it's the 3rd party program with the issue as other programs print fine. Will be waiting to hear :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's great news. :)
ASKER
The last thing I did before reaching the solution was to try an older version of the program and see if I was able to print. And I was. This confirmed that the issue lies within the new version of the program and it is now up to the manufacturer to solve it. However, I wouldn't have reached that conclusion if it weren't for Rob's expert advice in troubleshooting the problem.
I doubt VS 2013 would fix your issue as it sounds like you're using a 3rd party app? When you say "print a report", from the program in the RD session? I gather your users are trying to print to their local printer?
The users browser will be 32-bit so that should rule out any architecture issues, however are you getting the same issues from Windows 7/8 32-bit machines?