Hello All,

I am having a strange issue with a handful of our windows 7 clients.

What we have:

Recently I have setup a new 2008 R2 x64 server to hosts the printers in our school district. I have tried to keep things simple by using global print drivers that are available.  I only have the lastest hp global driver, the lastest xerox global driver, a dell printer driver, and a minolta driver. All of out client machines are running windows 7 enterprise and are both x64 and x86.

The Problem:

A handful of windows 7 machines seem to be missing the dependent files that should be listed under the properties of the driver in "print server properties". It has happened on x64 and x86 clients and pretty much prevents the clients from using any functionality of the printer they are connected to. At first I thought it may have been a xerox driver issue, but after seeing the issue on a few hp printers I am thinking its a problem with point and print somewhere? Any information that may help us resolve this problem would be greatly appreciated, thanks for your support! :D

I have recently set up Windows Fax and Scan and have been sending and receiving faxes.

But I was noticing that the From, To, and Subject text boxes are blank for the received faxes.

I have been trying to determine if this is how it always is or if there is more configuraiton that I need to do.

  Thanks,

            Spazfu 

Hello,

I am wondering if anyone has pointers on streamlining the login times after adding a GP printer on the user side of the policy with the shared printer option.

The conditions are as follows:

Machines are freshly imaged WIN 7 SP1 on the domain.

Papercut Agent 15.1 locally installed, agent is started in the same policy that pushes the print drivers.

Deep Freeze is installed and the machines are frozen so every logon is the "first" logon.

Attempting to push 2 papercut virtual print queues pointed to null as the port, one uses the LaserJet 9050 driver the other is a LaserJet M806 driver.

Print Server is 08 R2 VM running the print server role

The issue that came up was we went up to an almost 4 minute logon time. To test "preloading" the drivers we unfroze a machine, logged in to get the drivers to push down then refroze the machine. The brings the logon time to about 2:30 minutes which is a large improvement but still not quite enough.  We have also tested installing the printers with a script at user login and time to desktop is about 1:30 but you see the script run on the desktop for about 20 to 30 more seconds.

Are there any recommendations to debug the extended login times?

I've been working on a new print server that's running Windows Server 2012 R2, and I've found that Windows 7 x64 clients are unable to add any shared printer that is using a Type 4 print driver.  The add printer wizard stops at "Finishing the Installation" and pops up the error "Windows cannot connect to the printer", "Operation failed with error 0x00000002".

Windows 7 x86 clients and Windows 8.1 x64 work fine.  Windows 10 x64 works as well.

I've been looking around online and here for a possible solution, but I've not been able to locate one.  I've seen some mentions of removing and re-installing the enhanced point and print driver, but I can't figure out how to do that.  I've also seen people suggest going into Group Policy and changing the point and print policy setting to Disabled.  I tried that recently on a test machine and it has not worked.

So, I decided to start up Procmon and have it capturing while I tried to add one of the printers and see if anything jumped out at me.  I wasn't sure exactly what to look for, so I didn't set any particular filters.  I just let it run, tried to add a printer, then stopped the capture when it failed and scrolled through to see.  The only thing of interest I saw was a buffer overflow when querying a registry value:

Event Class:Registry
Operation:RegQueryValue
Result:BUFFER OVERFLOW
Path:HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers\ECE-PRINT-02.ece.ncsu.edu\Monitors\Client Side Port\{CDF9D151-00CC-45A7-BD31-64EB193C7450}\PrinterPath

After some more searching around online I found a blog post about an unrelated printer issue that mentioned looking at C:\Windows\inf\setupapi.app.log.  In there I found some entries and errors at the time I had tried adding one of the printers.  

At this point I'm not sure where else to check for more information.  If anyone has any suggestions for other logs or events to check, or filters to set and specific things to look for in Procmon, let me know.

Hi,

Possibly after some updates, we get this error in Print management and find that one of our firewalled internal subnets cannot add or use printers.

Did any recent update change a port that is in use? or is there another known fix for this?

Thanks

I'm having a problem with a document being deleted before it is printed.  Here are two of my events logs that occur back-to-back:

Log Name:      Microsoft-Windows-PrintService/Operational
Source:        Microsoft-Windows-PrintService
Date:          7/23/2015 3:11:40 PM
Event ID:      800
Task Category: Print job diagnostics
Level:         Information
Keywords:      WDI Diag
User:          MyDomain\muser
Computer:      computer.local.com
Description:
Spooling job 203.
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>800</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>43</Task>
    <Opcode>1</Opcode>
    <Keywords>0x4004000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-23T19:11:40.706653200Z" />
    <EventRecordID>413435</EventRecordID>
    <Correlation />
    <Execution ProcessID="2020" ThreadID="712" />
    <Channel>Microsoft-Windows-PrintService/Operational</Channel>
    <Computer>computer.local.com</Computer>
    <Security UserID="S-1-5-21-1118070172-928659315-1173975732-1154" />
  </System>
  <UserData>
    <JobDiag xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
      <JobId>203</JobId>
    </JobDiag>
  </UserData>
</Event>

Log Name:      Microsoft-Windows-PrintService/Operational
Source:        Microsoft-Windows-PrintService
Date:          7/23/2015 3:11:41 PM
Event ID:      310
Task Category: Deleting a document
Level:         Information
Keywords:      Classic Spooler Event,Document Print Job
User:          MyDomain\muser
Computer:      computer.local.com
Description:
Document 203, Print Document owned by muser was deleted on CC2-BP-CS3. No user action is required.
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>310</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>27</Task>
    <Opcode>11</Opcode>
    <Keywords>0x4000000000000840</Keywords>
    <TimeCreated SystemTime="2015-07-23T19:11:41.412643100Z" />
    <EventRecordID>413436</EventRecordID>
    <Correlation />
    <Execution ProcessID="2020" ThreadID="712" />
    <Channel>Microsoft-Windows-PrintService/Operational</Channel>
    <Computer>computer.ad.prestigefab.com</Computer>
    <Security UserID="S-1-5-21-1118070172-928659315-1173975732-1154" />
  </System>
  <UserData>
    <DocumentDeleted xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
      <Param1>203</Param1>
      <Param2>Print Document</Param2>
      <Param3>muser</Param3>
      <Param4>CC2-BP-CS3</Param4>
    </DocumentDeleted>
  </UserData>
</Event>

So the job looks like it is spooling but then next action is the document being deleted.  I would normally see the event 307 from the PrintService which says Printing a Document.  Can anybody tell me why the document is being deleted instead of printed?  The client machine is Windows XP SP3 and the print server is Windows Server 2012 R2. Thanks for any help.

I have fax service working on windows server 2012 ,I sharing it to allow all domain users to use. The clients using windows xp.

When user sent a fax I can't monitor it in the main server and the 'store in folder' feature doesn't work.

Formerly, I used fax service on windows server 2003 without above problems.

Please advise.

Thanks in advance for your time and assistance.

I've got Windows Server 2012 R2 Standard (Server Core) running the Print-Server role. I'm connecting via printmanagement.msc from an admin station to the print server and attempting to add a driver (Lexmark MX310dn PCL XL) to the drivers tab of the print management console on the print server. I'm getting the following error message:

"Add Printer Driver Wizard - Unable to install Lexmark MX310 Series XL, Type 3- User Mode, x64 driver. This operation is not supported."

I've tried this with Windows Firewall on and off. The user I'm using is a member of the local administrators group. I've also tried manually adding myself to the print operators group. Same result. I've tried a number of different drivers and received the same results. I've setup a print server in a test environment and got the same error. Is this an issue with adding user mode drivers remotely? I've done this successfully in 2008 R2 and Windows 7.

Is anyone else running a print server on Server Core 2012 R2? If so, are you guys managing it through PowerShell or MMC? I tried using PowerShell to Add-PrinterDriver and pointed -InfPath to the .inf, but it gave an error as well.

I have seen a couple of threads regarding this, but in frustration of being ignored by MS Pro-support i post anyway.

As we have started to upgrade to MS Server 2012 R2 on several of our customers, we are starting to see a pattern regarding the 2012 R2 when Print Management services is installed and network printers are shared from that server.

For all of the customers where we have experienced this problem, the shared printers are deployed automatically to the users through Group Policy, and are processed during user logon on RDS servers.

Symptoms we are experiencing are as follows:

Default printer is not set properly, either by policy during logon or if the user tries manually once logged in. If the users logs off and on again, we find that the default printer setting has either changed to a different printer, or the  icon is missing from the printer that should be default. HOWEVER, if you right-click the printer, it is clearly marked as default in the context menu.

When that happens, third-party applications like Adobe Reader are unable to print PDF's, and we also have another software which is unable to print labels. MS Office programs are unaffected though.

The only solution that might resolve the problem for the user is to manually remove the shared printer and then re-add it again. But the problem will return upon next log off/on again.

This problems as surfaced on all customers we have 2012 R2 as print server so far, regardless of printer brands, models, types, drivers versions, number of shared printers and physical network setup.

When changing print server back to 2012 or 2008 R2, everything is fixed instantly.

##

I have seen a couple of possible fixes on this floating around on the web, but none as worked for us. As for installing the printers locally on the RDS servers, that is not a viable solution. Some of our customers have 70+ network printers and are running RDS farms of 10 servers. Managing 70 printers * 10 manually is not an acceptable solution.

What ANNOYS me the most about this is the ignore i am receiving from MS PRO-support. 

Does anyone know of any official solution from MS on this....or unofficial for that matter?

Hello,

Having a strange issue where my print server has recently stopped showing the printers in the Print Manager.

If I connect print manager to another print server, I don't see any printers on the other server either. Can see all the ports, drivers, forms and from what I have read those three items render back to Print Manager differently than printers themselves.

restarting the spooler has no impact, server reboot doesn't affect it either.

no firewall enabled.

I can access the shared printers on the server, and click view remote printers to get that special printer share path on the server just fine.

I can view and manage the printers from another client using Print Manager and see everything.

have flushed DNS and tried again with no success.

tried adding print server via FQDN, IP and same result.

On the plus side, so far no interruption in print service to users as it appears to just be cosmetic management issue which is super frustrating.

Server is fully patched.

Any ideas?

Hi,

I need to push out some new default printer settings (mono and duplex) for 300 printers across about 12 x 2003/2008 print servers.  All of these devices are already mapped by around 2500 WinXP/7 users, so reconnecting the devices for everybody is not an option, nor is redeploying via GPO.  I've read the following thread, which appears to explain what I need to do:

http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/a0a9bb3f-db24-417d-9905-c310d068d3c6/ 

Firstly, I need the latest version of setprinter.exe, as the one I've got is date stamped April 2003, which I assume is the one that fails to work with devmode 9.  Does anybody know where I can get this from?

Secondly, I think it says that the clients will periodically update themselves with the server's default settings.  This is perfect, if correct.  However, would anybody please be able to explain when these periodic updates take place?

Many thanks in advance !

Andy

Hi, I'm try to remove the printer driver from our server but I keep getting message "Access denied or Driver in use". I have reboot the server but still same problem. no other users are logged in when I'm try to delete the drivers.

How can check which process is using the driver.

we are using

server 2008 r2

Hi.

I'm try to delete print driver which is not being used on server but when I try to delete it I get error message saying Access denied or driver in use. We have rebooted the server and check and make sure they is no other user is logged in.

How can I check who is using the print driver.

We are using

Windows 2008 r2 server.

Please see the images

We have a Windows Server 2008R2 Active Directory domain. Workstations on our network are both domain joined and non domain joined. We have a domain joined print server\\printserver1 (Windows Server 2008 R2) with some shared printers. We are noticing that if a domain user on a non domain joined machine maps/connects (using their domain credentials)  to a shared printer on\\printserver1 they would print fine  but after a while the printer port on the printer changes from standard tcp/ip to remote print port. I cannot edit or configure this port, keep getting a print server error. The workaround is the delete the entire printer from the workstation and reconnect to it. This is not isolated to any specific printer but is isolated to the non domain joined workstations.

Any advice on this problem would be appreciated. thanks.

I'm trying to add x64 under additional drivers for our existing 32bit printer shares on x86 2003 Server sp2...

If i try to add x64 drivers for say, laserjet 2200, I browse out to the x64 2003 CD for the inf file under AMD64.. it then prompts stating:  "the specified location does not contain the driver HP LaserJect 2200 Series PCL 6 for the requested processor architecture".

I tried this same routine for our Phaser 6250DP printer, if I browse to the x64 folder, where we have the specific x64 drivers for it, I get the error  "selected driver must be installed remotely".

Is it not possible to install an x64 version of a printer driver on a x86 server (not itanium)?

Thanks

I have an HP printer installed in windows server 2003

When i try to print it gives me error printing

Ping IP printer ok

SNMP enabled is not cheked

Other printers are working well

Could you please Help

I even changed the printer by another one and it's the same error

Hello All,

I am having a strange issue with a handful of our windows 7 clients.

What we have:

Recently I have setup a new 2008 R2 x64 server to hosts the printers in our school district. I have tried to keep things simple by using global print drivers that are available.  I only have the lastest hp global driver, the lastest xerox global driver, a dell printer driver, and a minolta driver. All of out client machines are running windows 7 enterprise and are both x64 and x86.

The Problem:

A handful of windows 7 machines seem to be missing the dependent files that should be listed under the properties of the driver in "print server properties". It has happened on x64 and x86 clients and pretty much prevents the clients from using any functionality of the printer they are connected to. At first I thought it may have been a xerox driver issue, but after seeing the issue on a few hp printers I am thinking its a problem with point and print somewhere? Any information that may help us resolve this problem would be greatly appreciated, thanks for your support! :D