I have a Fax device set up on my Windows Server 2012 Standard box. I can fax successfully if I do not have a cover page. However, if I specify a cover page I get an error when clicking the Send button: "The message could not be sent. The printer name is invalid."
I've tried different cover pages. I've even created a cover page with no info so it's something beyond an error in the cover page.
Hello
I am having the strangest issue with our print server. We recently took over a location and they had previously installed every single printer to this print server. Everything seemed to be running smooth until the other day when we pushed out Kaspersky to the server. I received a call from them that printers were randomly going offline and they were unable to print. Sometimes the print jobs would go through, but 90% of the time they would not. I disabled kaspersky thinking that was the issue but i still got reports of the problem with printing. I then remoted into the server while they were having the problem and i open printers and devices and the printers were gone... I refreshed a few mins later and they came back, I then refreshed again a few mins later and they were gone again. I am not sure what is going on, it seems like the print spooler keeps crashing. Has anyone had an issue like this before?
Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Date: 8/28/2013 12:30:09 PM
Event ID: 329
Task Category: Publishing a printer in the Active Directory
Level: Error
Keywords: Active Directory,Classic Spooler Event
User: SYSTEM
Computer: CSA-DC02
Description:
While attempting to publish the printer to the Active Directory directory service, the print spooler could
not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: 6d3. This can occur if DNS cannot resolve the domain controller IP address, or if the domain controller or directory service is not
functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.
Event Xml:
<Event xmlns="">
<System>
<Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}"
/>
<EventID>329</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>33</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000001800</Keywords>
<TimeCreated SystemTime="2013-08-28T16:30:09.154610000Z" />
<EventRecordID>23936</EventRecordID>
<Correlation />
<Execution ProcessID="6484" ThreadID="2116" />
<Channel>Microsoft-Windows-PrintService/Admin</Channel>
<Computer>csa-dc02</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<CantGetDnsDomainName xmlns:auto-ns3="
xmlns="">
<Param1>6d3</Param1>
</CantGetDnsDomainName>
</UserData>
</Event>
I am trying to find a script for this:
If number of printed pages > 10 then print separator page with owner name, date, time
The purpose of this is that often times, clients print 10+ pages and never claim it.
Less than 10 pages, it will print without separator page.
Thanks in advance!
Hi
I've been racking my brains over this for a while... we have the following setup:
Windows Server 2008 - sharing multiple printers out to a variety of clients.
Clients - xp, windows 7.
Problem: The XP clients are fine, all of the time. SOME of the windows 7 clients, have an issue: their printers (all mapped to this server, local printers are ok) are occasionally (once a day or so) showing as offline.
In this state it is not possible to remove and re-add the printers; the only way we have been able to temporarily solve it for each user, is to restart the (client side) print spooler service. Note that the service does not stop, all appears normal but the printers show as offline until the spooler service is restarted. there are no errors in the event logs.
any clues as to how one might nail down the source of this problem?
thanks
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 created a new Windows Server 2008 R2 SP1 print cluster over the summer and migrated all of our printers there - approx. 180. We are a school district and once staff started to come in the server sits at 100% utilization (caused by the spooler service) and I can see that network utilization sits at an average of 250Mbps (max around 400Mbps) on this server, which seems very excessive for a print server that is sitting mostly idle. There is not that much printing going on to match that amount of network usage. I checked with procmon and all I see is the spoolsv.exe responding to, what appears to be, client requests for printer statuses, etc. Wireshark shows 100,000 packets in 0.7 seconds. Also, when I failover the cluster to the other node, the CPU spikes almost immediately on that node (as expected). When staff start leaving at the end of the work day the CPU and network utilization drops.
Id appreciate any help anybody could provide. This is causing a huge issue right now - slow printing, etc.
-Rob
Client:
Windows 7 SP1 x64
Server:
Windows 2008 R2 SP1
Latest UPD drivers from HP, Xerox, Ricoh, etc.
Problem:
In the Microsoft-Windows-PrintService/Operational log, the printer's GUID instead of name is getting logged for events during GPP actions. By actions, I mean when the printer is recreated (since the GPP setting is REPLACE). Happens for all vendors.
Sample event (there are plenty more for other EventIDs too with ID 300, 304, 306, 302, 301)
Log Name: Microsoft-Windows-PrintService/Operational
Source: Microsoft-Windows-PrintService
Date: 5/28/2013 4:45:23 PM
Event ID: 300
Task Category: Adding a printer
Level: Information
Keywords: Classic Spooler Event,Printer
User: SYSTEM
Computer: MYPC.MYDOMAIN
Description:
Printer {01930C4C-5D21-4D1B-BC75-EC927AA8E293} was created. 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>300</EventID><Version>0</Version><Level>4</Level><Task>4</Task><Opcode>11</Opcode><Keywords>0x4000000000000820</Keywords><TimeCreated SystemTime="2013-05-28T23:45:23.032258100Z" /><EventRecordID>34675</EventRecordID><Correlation /><Execution ProcessID="1536" ThreadID="4372" /><Channel>Microsoft-Windows-PrintService/Operational</Channel><Computer>MYPC.MYDOMAIN</Computer><Security UserID="S-1-5-18" /></System><UserData><PrinterCreated xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events"><Param1>{01930C4C-5D21-4D1B-BC75-EC927AA8E293}</Param1></PrinterCreated></UserData></Event>Why isn't windows logging the real printer name? The GUID isn't useful at all.
I have 2 Windows 2003 x86 Standard servers (ServerA and ServerB)
I have installed some printers on both of them with x86 drivers.
Now I need to install x64 printer drivers as well.
I open Printers and Faxes - Server Properties - Drivers - Add
On ServerA I can choose the x64 option, but the option is not there on ServerB
On ServerB I have tried:
- Installing via the share, from a x64 client, but not possible
- Additional drivers on the share tab of the printer - same problem, no x64 option
- Exported a x64 driver using printmig.exe from ServerA. Imported it to ServerB. Error in event log: "Printer TESTx64 failed to initialize because a suitable KONICA MINOLTA C554SeriesPS SP driver could not be found."
When i search for others with the same problem I get flooded by the normal x86/x64 printer driver problems of having the same version, using the additional driver button and trying to install via the share from a x64 system
How can I get the x64 option back on serverB?
Thanks
I have a very annoying issue. When I attempt to add a Printer from PrintServer1 (2008 server) to a MemberServer01 (2008 server) via the following command:
rundll32 printui.dll,PrintUIEntry /in /n \\PrintServer1\Printer
I receive this error: "Windows cannot connect to the printer. Operation could not be completed (error 0x0000007e)" However, when I run this same command from a Windows 7 or Windows XP client, it works like a charm. Now,
I've googled, and read plenty, but can't seem to find any solutions that really apply to this particular situation. Any help that can be provided would be GREATLY appreciated!
Using a Office Jet 6500 on a local workstation in a terminal server environment. When printing from a remote session, the printer works, but we cannot print landscape. The Excel spreadsheet shows and previews as landscape, but when it is printed, it is not rotated on the page properly.
If we print to a different printer, the document prints properly, so it is just an issue with the OfficeJet's
All RDP clients are updated to the latest versions, and all updates on the server are current...
Any suggestions?
Brian
So Windows 7 can easlity find the printers and install them but xp cant even find the printers on the network
I presume if it was a driver issue with xp I couldnt install the printers but I would still beable to see the printers on the directory but nothing shows up
Im a bit stumped
Hello all
Windows 2008 R2
We recently decided to switch from printing directly to a printer by IP address from Windows 7 computers instead using Windows 2008 R2 Print Management feature.
We're using HP printers 500 MFP 525 with HP's print drivers. We setup a print queue to the IP printer then on each workstation we added the printer by searching for it for example:\\printserver\hrprinter. We have about 20 identical printers in each departments.
Our users reported an increase in wait time for these printers to print out from 10-30 minutes. On many occasion the print queue would report errors on many documents. We applied a hot fix: KB2276594 that helped a lot to reduce the amount of errors however we're still experiencing long wait times.
As a test we decided to map a few computers to print directly to the printer by IP address bypassing the print server. That was an incredible difference. Print out were immediate without any errors and we had multiple computers printing simultaneously.
As an FYI-We're using HP LATEST PRINT DRIVERS.
We're not using GPO to map these printers. The helpdesk are setting them up on each computer/profile.
I've searched a bit and didn't really find anything that completely addressed what I am experiencing.
We have an HP 8000n, 5200N, 1050c plotter, Canon iPF825 plotter and Konica Minolta C552 MFP. All are set on a Server 2003 R2 print server and a Server 2008 R2 print server. All drivers and firmware are up-to-date.
Issue 1) when printing PDF files to with the KM C552, it take forever for the job to finish spooling through either of the print server. However, if I have the printer installed on a Windows 7 64bit or XP Pro 32bit client as direct IP printing it spits right out lickity split.
Issue 2) if anybody on a Windows 7 client tries to print something like directions from Google map, or print an airline boarding pass from a website for example, through the Server 2008 R2 print server to any printer the job starts to spool, then errors and nothing else will print until that job is manually deleted. This does not seem to happen with direct IP printing or when printing through the Server 2003 R2 print server.
Here is the rub - I need to have at least the Konica Minolta C552 print through a print server because we require a few standard settings for printing. If I have the printers installed as direct IP printing it is much more time consuming to enforce our printing standards, even in a small 40 person office.
I also don't want to fall back to printing everything though the Server 2003 print server because a) that doesn't solve the slow PDF printing issue and b) we intend to phase out of Server 2003 servers.
Manning
Anyone know what tool I can use to migrate pritners from a 2003 server to another 2003 server. I keep seing PRINTMIG being referenced but cant find this anywhere!!
Help!
Thanks
Joe.
We have a unique situation where our organization's main office, running on Windows Server 2003 needs to be able to print to a printer at a remote satellite location. I setup a Windows XP Pro desktop at the remote location and connected to the server via VPN. I have direct access to all server services from the remote desktop, no problem. I directly connected the printer via USB to the remote desktop and shared it. I can print to the printer from the remote desktop no problem. From the main office server, I can find the shared printer in the directory, but cannot connect to it -- when I try, I get a 'Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost it's connection to the server' error. I get the same error if I tried to directly specify the name of the printer as \\desktopname\printershare. Any ideas?
How to Share a Client Shared Printer?
Purpose: I want users in main office to be able to print to VPN Users Printer on my print Server while she is offline and then jobs go to the Printer when the user is connected VPN. Since only the PC connects VPN not her entire home subnet IP Printing is not an option... Surely there is a way to get a Print Server to Serve a Shared printer? I even tried right from my PC with same results as below but problem is for VPN User even though i have same issue on LAN with print Server...
We have a WinXP Client PC with Shared printer \\CAPA5421\WVMCzPrint1
They VPN in and I can even use \\CAPA5421\ to see the printer listed shared but if I run START \\CAPA5421\WVMCzPrint1 I get error message "The request is not Supported" nothing else... Does not seem to be rights issue since I am Admin credentialed and able to see Shares and C$ of PC.
However I can right click the Printer in my Explorer Window \\CAPA5421\ and connect it... Even lets me Print Test page to user that comes out of her Printer at her home office but it will not show up in Print Management if connected this way... Another words its not on my print server as anything more than a Printer on my logon...
Trying to Add Printers thru wizard it only looks at local Subnet and will not let me type in the share name \\CAPA5421\WVMCzPrint1
Any Ideas would be greatly appreciated! Thanks!!