We have an application which will not print more than one page via Citrix Universal Printer if the printer is not set to "Print directly to the printer".

This setting goes back to "Spool print documents..." automatically some times.
Not 100% sure, but it seems that this happen when the spooler service is restarted.

Does anyone know how to prevent this from happening? We need to have this setting configured for direct printing always for some printers.

The print server is Windows Server 2008 R2 Standard on VMware vSphere 5.0

Hi All,

Recently one of our windows client in the domain network cannot access the print preferences.

It was previously fine and other computers within the domain could access the print preferences.

All the users are authorized to go to the print preferences settings as the users i am referencing to are managers of the company.

I have tried to uninstall the print drivers and un-deploy the printer and gpupdate the PC. however it is still unable to access the printing preferences.

Andre

When trying to install a network printer (working on all workstations) error comes up "Unable to install printer. Either printer name was typed incorrectly or printer has lost its connection to the server..." Printer still works on all workstations (4 XP, Windows 7 and Vista Pro). Printer does show up in the Printers and Faxes folder but as "HP LaserJet 3050 Series PCL 6,0" When clicked warning message comes "Operation could not be completed either printer name was typed incorrectly or printer has lost its connection to the server..."

Attempts for fix:

1) remove all printers and drivers, reboot and re-install

2) remove all ports used (except XPS Document), remove all drivers, reboot and re-install

3) remove all registry keys of printers (and all printers), reboot, re-install

4) ensure all updates are completed

5) tried direct usb connect, after removal of all printers/drivers and rebooting

Printer HP laster jet 3055. Print Spooler is confirmed Running and all dependent Services are running.

Issue started when trying to add a printer connected to a computer (shared) Brother MF7340 for remote desktop use through Windows 7 Pro. Printers in "Local Resource" when using Remote Desktop for anyone do not work and show up as "Printer Name 0,4" or anther number instead of the 4. Once the Print Spooler is restarted "HP LaserJet 3050 Series PCL 6,0" dissapears.

• Clients = WinXP SP3 with GPP KB974266 installed. 
• Print Server = Windows 2008 R2 x64
• GPO - point and print restrictions enabled so clients can install drivers automatically.
• GPP - Shared Printers are being deployed per-user.

• HP = 5.1.1.8232
• Ricoh = 3.30
• Xerox = 5.185.15

1. When opening Printers and Faxes, it takes ~30 seconds for the status to change fromOpening to Ready . There are ~35 printers in this test case.
2. I notice in the System Event Logs that printer drivers are constantly getting reinstalled, even though they're not getting changed on the print server.  This is happening for all of the vendor's drivers, but with no pattern.  Some times it'll be the Xerox and Ricoh... other times it's HP and Xerox, etc.  I suspect this is the cause for the large delay when opening printers and faxes.

Hi!

Should all the printers that need to be published under win 2008 R2 must support win 2008 and should have driver for the server software first? What about the printers that do not have windows 2008 Drivers?

Thanks.

I have a few old HP printers and none have NICs.  I will use one as an example.  HP LaserJet 4050 Series printer is directly connected via LPT1 port/Parrallel cable to the XP x86 client.  The HP LJ 4050 is shared.   I have to add the 64 bit drivers for the 4050 on a Server 2008 R2.  The part that I'm getting stuck at is the drivers.  I've spent a good deal of time researching this today and in the past. 

I tried to follow numerous technet threads, but came to dead ends.

http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/7e347b87-a0a0-4096-afbc-10603e4e2754

I was able to add the 64 bit driver using the link above's suggestions, but then I couldn't use the driver even when I tried to add a new printer and pointed to the System32\DriverStore\FileRepository\xxx\x.inf for the driver. I tried using the HP Universal PCL6 & PCL5 drivers before I tried adding the HP LJ 4050 PCL6 driver from Windows Updates, via the Print Management console.

I also tried changing the driver on the XP client.  I tired adding Universal Printing PCL6 driver from HP's website but got PCL errors when I printed from the XP client.  I tried both the Universal PCL6 and the PCL6 version 5.6 unsuccessfully.  I had to put the old HP LJ 4050 PCL6 driver back in place.

Brand new Server 2008 R2 x64 on VM.

Install multiple network printers HP and Ricoh with universal driver PLC6 ( different for each brand) no problem or errors ect....

Will not print any of printers.

In Events on all show :

Have several printers of various types and brands that are shared on a 08R2 Print Server
All users have same permission sets.
All computers built the same, running Windows XP, fully patched
Print drivers are latest universal drivers for whichever model of printer using, most of which are HP's, Dell's, and Xerox.

User A on Computer A can connect to Printer A with no problems
User A on Computer B gets you do not have sufficient permission to connect to this printer when connecting to Printer A
User B on Computer A gets you do not have sufficient permission to connect to this printer when connecting to Printer A
User B on Computer B can connect to Printer A with no problems.
User C can connect to Printer A from any computer with no problems.
User D can't connec to Printer A from any computer.

Again, all users have been confirmed 4 times to have the Exact same permissions. All user accounts have been recreated at least twice at this stage. All systems that have been tested have been rebuilt at least twice, the print server started out as an 03R2 with this same problem, and has since been switched to different hardware, and is now running 08R2 and still getting the same problem.

I know this is going to sound strange, however can someone tell me why when the fax server answers a fax and then goes through the process of emailing the fax, I then get a copy in my email, however when I or anyone on the network open the program FAX and SCAN to see the faxes they are not there to view. The program is connected across the network users have the same rights as before and the program worked just fine. If I want to view the inbox and bypass the program I go to the Progam Data Windows NT inbox and files are there to view. If someone could email me a link or a solution I would greatly appreciate it.

dennis.johnson@asilservices.com

MSB

OS: Windows 7 Enterprise SP1 x64 + hotfixes.

It appears the printer subsystem is broken as Windows is unable to install any driver from any vendor.  All attempts result in HRESULT 0x8000ffff.  For example:

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          1/8/2013 8:19:49 AM
Event ID:      215
Task Category: Installing a printer driver
Level:         Error
Keywords:      Printer Setup,Printer
User:          SYSTEM
Computer:      WORKSTATION.MYDOMAIN
Description:
Installing printer driver Remote Desktop Easy Print failed, error code 0x0, HRESULT 0x8000ffff. See the event user data for context information.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" /><EventID>215</EventID><Version>0</Version><Level>2</Level><Task>19</Task><Opcode>12</Opcode><Keywords>0x8000000000000220</Keywords><TimeCreated SystemTime="2013-01-08T16:19:49.334750400Z" /><EventRecordID>777</EventRecordID><Correlation /><Execution ProcessID="1448" ThreadID="2300" /><Channel>Microsoft-Windows-PrintService/Admin</Channel><Computer>WORKSTATION.amc.MYDOMAIN</Computer><Security UserID="S-1-5-18" /></System><UserData><SetupInstallPrinterDriver xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events"><Label>InternalInstallPrinterDriverFromPackage</Label><Message>GetCorePrinterDriversKey failed</Message><AdditionalInfo>-</AdditionalInfo><InfPath>C:\Windows\System32\DriverStore\FileRepository\tsprint.inf_amd64_neutral_c48d421ad2c1e3e3\tsprint.inf</InfPath><DriverName>Remote Desktop Easy Print</DriverName><InstallSection>TSPRINT_FILES</InstallSection><ProcessorArchitecture>Windows x64</ProcessorArchitecture><PackageAware>Package aware</PackageAware><CoreDriverDependencies>{D20EA372-DD35-4950-9ED8-A6335AFE79F5}</CoreDriverDependencies><LastError>0x0</LastError><HResult>0x8000ffff</HResult></SetupInstallPrinterDriver></UserData></Event>
=================================================
Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          1/8/2013 8:19:49 AM
Event ID:      215
Task Category: Installing a printer driver
Level:         Error
Keywords:      Printer Setup,Printer
User:          SYSTEM
Computer:      WORKSTATION.MYDOMAIN
Description:
Installing printer driver Remote Desktop Easy Print failed, error code 0x0, HRESULT 0x8000ffff. See the event user data for context information.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" /><EventID>215</EventID><Version>0</Version><Level>2</Level><Task>19</Task><Opcode>12</Opcode><Keywords>0x8000000000000220</Keywords><TimeCreated SystemTime="2013-01-08T16:19:49.339750900Z" /><EventRecordID>778</EventRecordID><Correlation /><Execution ProcessID="484" ThreadID="544" /><Channel>Microsoft-Windows-PrintService/Admin</Channel><Computer>WORKSTATION.MYDOMAIN</Computer><Security UserID="S-1-5-18" /></System><UserData><SetupInstallPrinterDriver xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events"><Label>InstallPrinterDriverFromInfPackage</Label><Message>InstallPrinterDriverFromPackage failed</Message><AdditionalInfo>-</AdditionalInfo><InfPath>C:\Windows\System32\DriverStore\FileRepository\tsprint.inf_amd64_neutral_c48d421ad2c1e3e3\tsprint.inf</InfPath><DriverName>Remote Desktop Easy Print</DriverName><InstallSection>-</InstallSection><ProcessorArchitecture>Windows x64</ProcessorArchitecture><PackageAware>Not package aware</PackageAware><CoreDriverDependencies>-</CoreDriverDependencies><LastError>0x0</LastError><HResult>0x8000ffff</HResult></SetupInstallPrinterDriver></UserData></Event>
=================================================
Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          1/8/2013 8:19:49 AM
Event ID:      215
Task Category: Installing a printer driver
Level:         Error
Keywords:      Printer Setup,Printer
User:          SYSTEM
Computer:      WORKSTATION.MYDOMAIN
Description:
Installing printer driver - failed, error code 0x8000ffff, HRESULT 0x8000ffff. See the event user data for context information.
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" /><EventID>215</EventID><Version>0</Version><Level>2</Level><Task>19</Task><Opcode>12</Opcode><Keywords>0x8000000000000220</Keywords><TimeCreated SystemTime="2013-01-08T16:19:49.339750900Z" /><EventRecordID>779</EventRecordID><Correlation /><Execution ProcessID="484" ThreadID="544" /><Channel>Microsoft-Windows-PrintService/Admin</Channel><Computer>WORKSTATION.MYDOMAIN</Computer><Security UserID="S-1-5-18" /></System><UserData><SetupInstallPrinterDriver xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events"><Label>PSetupInstallPrinterDriver</Label><Message>InstallDriverFromCurrentInf failed</Message><AdditionalInfo>-</AdditionalInfo><InfPath>C:\Windows\System32\DriverStore\FileRepository\tsprint.inf_amd64_neutral_c48d421ad2c1e3e3\tsprint.inf</InfPath><DriverName>-</DriverName><InstallSection>-</InstallSection><ProcessorArchitecture>Windows x64</ProcessorArchitecture><PackageAware>Not package aware</PackageAware><CoreDriverDependencies>-</CoreDriverDependencies><LastError>0x8000ffff</LastError><HResult>0x8000ffff</HResult></SetupInstallPrinterDriver></UserData></Event>

If I attempt to install a driver through Printer Management, the following errors are always thrown.  Yes, I've tried both HP and Xerox so it's not a vendor specific issue:

I've attempted to purge all vendor files from C:\Windows\System32\spool\.  Remove all vendor entries from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print.  Currently there doesn't appear to be any left over vendor files/entries laying around.

Shame the Microsoft Fixit for Printing tool doesn't work on Windows 7.

I've also tried the Microsoft FixIt Pro - printing troubleshooter, but it was unable to find any real problems.

Thoughts on why everything is failing?

Reddy

Printers disconnects randomly on remote desktop connections that's running windows server 2008.  The typical fix is to delete the printer and re-install the network printer.  Any suggestions as to why or a link to a hotfix would be appreciated.

Rick G.

We migrated our print server from Windows Server 2008 R2 SP1 to Windows Server 2012 just before the start of 2013 and since then we are seeing a number of problems occur on our Windows 7 SP1 x64 clients.

These vary from an 0x0000007a error when trying to print a test page (which we've managed to solve) and now we are having problems when printers are attached to machines from our printer scripts.  The error being generated from the script is: "This operation requires an interactive window station" but the error appearing the events logs is: "Installing printer driver <DRIVERNAME> failed, error code 0x0, HRESULT 0x800705b3.  See the event user data for context information"

Before the migration we had no issues.  The migration completed without errors and the server name is the same as previous so we made no changes to any of our scripts.

Any ideas why we are suddenly seeing errors and any suggestions on how to fix them?

I have a Windows Server 2008 R2 VM with a print server set up. I have a few drivers loaded that I have verified and set to Isolated. My problem exists with the device metadata which I will describe below.

I add printers through server manager,  if you drill down to Drivers / Ports / Forms / Printers... I right click on Printers and select "Add a Printer". The process I follow is:

1. I select "Add a TCP/IP or Web Services Printer by IP address or hostname"
2. I input the Host Name and copy it to the Port Name box. (Auto detect the printer driver to use is unchecked)
3. Here I would normally select "Use an existing printer driver on the computer" and I would select the driver that I have pre-qualified and loaded with the "Add printer driver wizard". I do this to ensure that my techs are using the correct driver when installing printers. However, when I use this option the device metadata will not download for the installed printer. In order to have the metadata automatically downloaded and applied, I have to select "Install a new driver" and then browse to the exact same driver that I had saved in a folder on my hard drive. When I use this option, device metadata including the unique printer icon automatically downloads successfully.

I have tried to debug the process by logging "DeviceMetadata/Debug" under "UserPnp" but I don't received any errors or warnings. Windows makes 10 different DMRC queries but fails to download anything.

My questions is: what is different about browsing to the driver rather than using an existing driver that would cause the query to fail?

Windows 2008 R2 SP1 x64 Terminal Server - Hyper-V with Citrix XenApp6

Unable to install printer.  Event ID 215 - 0x5b3 error code.

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService

Event ID:      215
Task Category: Installing a printer driver
Level:         Error
Keywords:      Printer Setup,Printer

Description:
Installing printer driver - failed, error code 0x5b3, HRESULT 0x800705b3. See the event user data for context information.

Prior to that Event ID 215

Description:
Installing printer driver HP Universal Printing PCL 5 (v5.2) failed, error code 0x0, HRESULT 0x800705b3.

I was able to remove the driver but cannot add it back.

This keeps happening on various servers.  In the past week I have had to rebuild 4 servers out of 11.

The only reference to the error code 0x5b3 I have found is for Vista and I have tried those suggestions.

I have ruled out the problem being a Virus.   I have cleaned out the registry settings as per various posts from Technet.  Which allowed me to remove the driver only. Not add it back.

This is the latest version of the HP UPD PCL5 driver.  It seems to have started after installing SP1 for W2k8 R2 in February.

The problem seems to happening more frequent now.

Are there other suggestions?

Would appreciate any help.

Thanks,

Denise

Hello,

I was working with our printer manufacturer on getting x64 drivers installed as additional drivers (for our Win7 x64 users) on Server 2008 32-bit. The manufacturer informed me that there is an updated (sometime in the last year) that fixes certain issues with the x64 drivers on this version of server.

Anybody know what update he's talking about?

Thanks!

Hi!

In our environment we are working with Windows 2008R2 Terminalserver on Citrix XenApp and therefore with a Windows 2008R2 printserver.

The about 450 printers we are using are various but most likely Kyocera, Konica Minolta, Lexmark and HP.

Again and again we have problems with printjobs that stuck, e.g. because the printer has no paper or no toner or some kind of other problem. As these jobs can not be put out by the printer they stay in the server spool untill the printer works again. So far so good.

But the server trys to send these stuck jobs to the printer again and again. And in a Win 2008R2 environment printjobs can be very huge!As a result printjobs for other printers that would work fine are queued in the spool directory on the server and have to wait till the server recognizes that the offline printer is not available and starts an other job. Then he trys again to print the stuck job, an so on.....

This causes extremly log periods untill printjobs are put out. The only thing we can do then is to put the not working printer on the server on hold and delete the regarding printjob. Then within seconds the queued printjobs for the oter printers are put out.

Would anybody know an option to tell the printserver/spooler to not send printjobs AGAIN to a printer for that he already had recognized staus as "failure"?? Or is it possible that the printers would be automatically set on status "hold" instead of "failure"?

It would be no problem for us to set the printer or printjobs free manually then.

Thanks in advance!!

Nadine