2008 TS Gets "Access Denied" When Printing to Redirected Printer "Howard Sherman" <howard[ at ]royalgeeks.com> 12/21/2008 12:31:49 PM Ok. I tried everything. I give up. I have a Windows Server 2008 TS (for the record -- x64, Enterprise Edition) and multiple users connecting to run a server-based app. The clients can connect to the server and run their app -- they even see their locally-connected printer before. But when they go to print to it -- no output. It even LOOKS like it'll print -- When in an IE7 on the server and go to print a web page -- the browser sends it to the print queue - the queue icons appear for a minute then.... nothing. My biggest clue to this mystery comes from Event Viewer. it's a long messages but the long and short -- is the server is attempting to print to the RDP printer (ANY RDP printer) and can't. The messages goes to say that I should try to reprint the document or restart the spooler. The very last line says: Win32 error code returned by the print processor: 5. Access is denied. I have a screenshot of it if you'd like me to email it. Here's the fast list of everything tried: Enabled .Net on the server All XP machines are running SP3 -- Still went ahead and manually verified tha RDP 6.1 and .Net 3.0 was installed Tried five different machines -- four of various XP vintages each connected with a different type of printer checking for compatibility issues. The Fifth machine is a Windows Visa Ultimate with SP1, etc. No Easy Print. No printing at all. Googling for this problem got me a bizarre but plausible solution -- share \windows\system32\spool -- DONE. No difference. Also made sure the printer was shared. Why not, right? :) The properties screen of any RDP printer reveals the Easy print driver is, indeed, the one Windows will try and use. Reading over every post and article on the topic of Easy Print there is no reason why this shouldn't working right now. But it isn't. There's SOMETHING going on in this brand new server that is preventing Easy Print from getting the print job to the printer on the client end. HELP! Howard Sherman MCSE (Feeling ready for the 70-648 after this experience!)

Re: 2008 TS Gets "Access Denied" When Printing to Redirected Printer "Vera Noest [MVP]" <vera.noest[ at ]remove-this.hem.utfors.se> 12/21/2008 3:43:43 PM The clients need not just .NET Framework 3.0, they need ..NET Framework 3.0 SP1. Do they have that? I've also seen a number of posts about identical problem, with as solution to give users Full Control of the \windows\system32\spool directory. I know you've shared it (i don't think that's necessary), but do they have Full Control? _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "Howard Sherman" <howard[ at ]royalgeeks.com> wrote on 21 dec 2008 in microsoft.public.windows.terminal_services: [Quoted Text] > Ok. I tried everything. I give up. > > I have a Windows Server 2008 TS (for the record -- x64, > Enterprise Edition) and multiple users connecting to run a > server-based app. > > The clients can connect to the server and run their app -- they > even see their locally-connected printer before. But when they > go to print to it -- no output. > It even LOOKS like it'll print -- When in an IE7 on the server > and go to print a web page -- the browser sends it to the print > queue - the queue icons appear for a minute then.... nothing. > > My biggest clue to this mystery comes from Event Viewer. it's a > long messages but the long and short -- is the server is > attempting to print to the RDP printer (ANY RDP printer) and > can't. The messages goes to say that I should try to reprint > the document or restart the spooler. The very last line says: > > Win32 error code returned by the print processor: 5. Access is > denied. > > I have a screenshot of it if you'd like me to email it. > > Here's the fast list of everything tried: > > Enabled .Net on the server > All XP machines are running SP3 -- Still went ahead and manually > verified tha RDP 6.1 and .Net 3.0 was installed > Tried five different machines -- four of various XP vintages > each connected with a different type of printer checking for > compatibility issues. The Fifth machine is a Windows Visa > Ultimate with SP1, etc. No Easy Print. No printing at all. > Googling for this problem got me a bizarre but plausible > solution -- share \windows\system32\spool -- DONE. No > difference. Also made sure the printer was shared. Why not, > right? :) The properties screen of any RDP printer reveals the > Easy print driver is, indeed, the one Windows will try and use. > > Reading over every post and article on the topic of Easy Print > there is no reason why this shouldn't working right now. But it > isn't. There's SOMETHING going on in this brand new server that > is preventing Easy Print from getting the print job to the > printer on the client end. > > HELP! > > Howard Sherman > MCSE > (Feeling ready for the 70-648 after this experience!)

Re: 2008 TS Gets "Access Denied" When Printing to Redirected Printer "Howard Sherman" <howard[ at ]royalgeeks.com> 12/23/2008 12:13:51 AM The permissions on the \windows\system32\spool folder did the trick. "Easy Print" eh? Why isn't something as essential as this setting documented? Thanks and happy holidays! Howard Sherman

Re: 2008 TS Gets "Access Denied" When Printing to Redirected Printer Jeff Pitsch <jeff.pitsch.fake[ at ]jeffpitschconsulting.com> 12/23/2008 1:05:48 AM Mainly because it shouldn't have to be done but there have been a few issues that have cropped with Win2k8 that have come up for a few vs the many. Jeff Pitsch Microsoft MVP - Terminal Services Howard Sherman wrote: [Quoted Text] > The permissions on the \windows\system32\spool folder did the trick. > > "Easy Print" eh? Why isn't something as essential as this setting > documented? > > Thanks and happy holidays! > > Howard Sherman