Hi!

I am having trouble adding network printers on my 2008 x64 terminal server:s (9 servers) i get 0x00000002 error.

I have tried the following, Logged on as domain admin adding a network printer i get error 0x00000002, tried to install a local printer on the server gives me error 0x00000002.

Adding local printer with Microsoft shipped drivers i get error 0x00000002

Have tried above as local admin on server, same problem.

Print server: w2k8 x64 Datacenter (all printers have 64/32 bit drivers)

Terminal Servers: w2k8 x64 Standard

Regards

Roger

We have deployed a new print server using Server 2012, to replace our old one running 2008 "R1."

This server hosts approximately 15 printers. All but a few printers are running the Type 4 drivers supplied with Windows, to ensure RT compatibility. These printers include HP 4350s, 4700, and CP5525s. Additionally, there are several older HP 3380s and 4015s running with the HP UPD, which we do not use with RT.

Almost immediately upon moving a few test users to the new server, we noticed that several of our documents were printing with the right hand margin cut off.

I obtained a copy of one of the Word documents that was having the issue and sent the file to various printers, across the building from my Windows 7 client machine. Every printer reproduced the problem.  I had another user running Windows 8 send the file to the same printer, and the document printed normally.  I then copied the file to the print server, logged into it from the console, opened the file, and printed it directly to the printer.  The document printed normally.

When I held the incorrectly and correctly printed documents together in front of a light, I found that everything is just a bit bigger when it is printed from a Win7 client machine. I'd say that the entire layout of the page is scaled (read: enlarged) to about 105%, so when documents that have tight left/right margins, like some of our form templates, are printed, it runs off the edge of the printable area. The scaling happens on top, bottom, right, and left of the page, meaning that my top line is above the top line of the "correct" printout, etc, but in my case, the right side is the one that gets cut off. Apparently the printer still has sufficient wiggle-room on the top, bottom, and left.

I have tried turning off client side rendering in the print properties on the server, which then trickled down to the connected clients, but that seems to have made no difference, nor did tinkering with different print processors.

Has anyone seen this and/or know what can be done about it, short of upgrading all of my clients to Windows 8?  We'll get to 8 eventually, but we're not there yet. 

Thanks in advance!

Hi all

I hope someone is able to help me out on this question.

In a larger environment you might now always control servers or clients throughout the organization. So youmight end up in a situation where a client has driver version 1.1 downloaded from server1. The client then connects to server2 which has driver version 1.2 - and the new version is pushed to the client.

Then what happens when the client connects to server1 again (where driver version 1.1 is still installed)? Will the client be "upgraded" to the old version or will the client keep version 1.2 and we just have to cross our fingers that it all goes well?

I always thought that was the scenario but several colleagues of mine keeps telling me that the driver will always be downloaded from the server if the version is not an exact match. But that does not correspond well with e.g.http://support.microsoft.com/kb/244284/en-us that states"If the client and server have the same driver but with a different version, the server's drivers are downloaded and the client uses the driver with the latest version." even though it is not 100% clear - unless they mean that the driver is always downloaded if there is a version missmatch, but then discarded by the client if older than its own version?

I hope someone can help me out - preferable by pointing me to some documentation :)

Your help is much appreciated!

Thanks, David.

i just want to inquire on how to add a network printer in windows 2012 server?

many thanks

I have searched the forums and it would appear that Server 2008 R2 does not support this, however, I would like to ask his question again for server 2012 R2.

Just like you would assign disk quotas is there an option to set a print quota to a specific user so they are only able to print X amount of pages a day/week/month?

We are experiencing a problem on Server 2008 R2 Enterprise with print jobs staying in the queue with a "Sent to Printer" status after they have been printed.

I have found two threads that describe a similar problem here and here but neither offers a solution applicable to this case.

I have also noticed that if the spooler is restarted with jobs in the "Sent To Printer" state they print a second time and clear from the queue. However, future jobs submitted still experience the same problem of not clearing.

I have tested this and it occurs on a HP 4050N (using MS provided drivers), a Samsung CLP-550 and a Fuji-Xerox AP-II 4000, printing from both Windows XP and Windows 7.

I have tracked the issue to occurring when the user printing does not have the "Manage Documents" rights to their print jobs. By default users get this right through the Creator Owner security settings for their own jobs, however print monitoring software such as Papercut requires you to remove this so users can not un-pause their own jobs. In previous versions of windows even with this right removed the jobs would still delete when printed. It appears in Server 2008 R2 the print server will not delete the job when printed if the user does not have "Manage Documents" right.

Can anyone suggest a solution to correctly delete jobs when printed, but not give users the Creator Owner so they can not bypass the print auditing software?

Hi

I am trying to set up a fall back printing solution as a just in case solution for if another project fail to complete on time.

I have the Print management role set up on a 2008 R2 server connecting to a AD DC on a separate 2008 R2 server inside a test lab. I have printing working and I am able to install the printer via the print server on to an Win XP VM and a Win 7 VM and print while the server is up but I want them to still be able to print when the server is down say for maintenance or other issues.

I seem to be going around in circles on trying to find this solution and it cant be that hard surely. Printing is not really my thing but been asked to try and just stuck on this. I know it should be simple to have the users pc's talk to the printer directly and just use the server for management of the printers and rivers etc.  

Also is there a script anyone knows of to import on mass printer drivers to the print server so I don't have to do by hand. I can't connect the print server to my outside network to import the printers and there drivers directly but I do have a driver store I have created on my own machine to collect the drivers for the 12,000+ different printers we supposedly have. I need this as we are changing from a x86 environment to an x64 environment so require both drivers.

As I have said this not my normal day too day so any advice is really appreciated.

If I can get this to work the only other change will be swapping the print server to a 2012 server and seeing what needs to change for the same result.

When adding any one of the many printers on one of the Terminal Servers i recieve this message.

I do not have this issue on the other three Servers, just wondering if anyone else has had this issue and can share advise

Luckily it's near christmas so the school is pretty much empty

Thanks

Johno

Dear Sir/Madam,

Server - Microsoft Windows Server R2 2008 Enterprise (Clustered)

Networked Printers - HP LaserJet Printer, Ricoh Multifunction machine

Clients' PC - Windows 7 desktop

I have installed print queues on the above Server.  However, users encountered problem when printing MS Office documents - Printing notification bubble showed "This document was sent to the printer" is showing wrong number of total printed pages.  But there is no problem on the printout.

I found that there is no pages number error when printing PDF files.

Would you please help to check the above issue and how to solve it?  Thanks for your help

Ray

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

Hi!

I'm in charge of our printing system and I’m migrating our cups print server to a Microsoft print server. We are using many (about 45 Windows and 15 Ubuntu) shared printers from workstations, which are causing problems due to missing authentification data while using local ports.

When I send a print job to the server, I can clearly see the print job owner. When the requested printer is a shared one of a windows workstation, the print job signals “error” and stays in the queue (without error messages in the logfiles). But when the requested printer is shared by one of our Ubuntu machines, the print job will be forwarded to the Ubuntu causing an error there, since no authentification data is provided anymore:

I [14/Nov/2013:12:49:41 +0100] Denying user "" access to printer "testprint"...

Printing port of the clients is (local port) “\\testprintserver\testprint”

Printing port of the shared printer on our server 2012 (local port) “\\workstation1\testprint”

And at last, our workstation1 is sharing a local USB Printer as “testprint”.

I’ll use the configuration written above for an example:

Printing directly from our print server to testprint on workstation1 works, but not from the clients (using our print server, directly works). When I use LPD/LPR services between print server and workstation1, the clients can print on the workstation’s shared printer using our print server.

I read that the LPD/LPR Services are deprecated and will eventually be removed in future versions. Is there any other possibility of getting our workstation’s shared printer to work?

Best regards

Alexander Preuß

Hi Everyone,

Great day!!

i would like set the E-Mail notification on print spooler services on windows server 2008. can some one help me with steps..

Regards, Praveen Kumar Reddy

I have some Windows 2008 R2 terminal servers in my environment that I have manually added local printers to for the users. However when I boot up the servers they are also adding some or all of the shared network printers in our domain. This is duplicating the printers and since I don't have the drivers installed the users can't print to the network printers anyway. (I am using a universal print driver for them)

I want to disable this; I do not want any network printers automatically added. I do not want the users to see them. I do not want the users to have duplicate printers. I only want the users to see the local printers that I added. 

I've spent many hours searching and researching but have yet to find a solution. Can anyone please point me in the right direction?

Thanks,

Curtis

I have come across a user having a problem with a faint white screen coming over their whole screen with the "Not Responding" error on top of the current open window above the address bar.  This error freezes the user's PC from 30 seconds to 1 minute.  This error seems to happen while the user is only working within Microsoft Office applications, mostly within Microsoft Project (That is the main application that this user works with everyday). I have looked into the user's PC and they are not running extra programs in the background or services that would bog down the PC overall.  The even viewer log error details are as follows:

Faulting application name: WINPROJ.EXE, version 11.3.2007.1529, time stamp 0x465bf9b1

Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec49caf

Exception code: 0xc0000374

Fault Offset: 0x000c33bb

Faulting process id: 0xaf4

Faulting application start time: 0x01cdb9007f27256f

Faulting application path: C:\Program Files\Microsoft Office\OFFICE11\WINPROJ.EXE

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: e4b8f6b6-24f3-11e2-a1e6-b499bae70793

Log Name: Application - Source: Application Error - Event ID: 1000 - Level: Error - User: N/A - Logged: (Today) - Task Category - (100) - Keywords: Classic - Computer: (Computer name.network. . .)

The user goes into his Microsoft Project open project and makes some changes, highlights some cells and goes to make some changes and then the faint white screen comes up with the "Not Responding" screen appears.  Some background information.  This problem happens both on wireless and docked plugged into the LAN.  Our user's have a network drive (home drive) located about two blocks away at my location.  This problem is not specific to accessing information only on the network drive though, already tried that scenario.  This user does not have administrative rights.  I took my laptop over to their location/building and tried to replicate the issue myself and I was not able to do so.  I did not stay more than a hour and a half (may need to stay there all day to replicate).  Multiple user's in that building report having this specific issue that the one user I am working with now is reporting the faint white screen "not responding" error.  All operating machines are using Windows 7.  This happens on both laptops and desktops.  There is not a ton of software or processes running in the background to bog down the user's computer.

Does anyone have any ideas??

Forgive me for any faux pas as I am a newbie to posting here for the first time.

I have a Windows 2008 set up with only the Print Services Role.

Initially, I had set up about 150 Kyocera printers using standard TCP/IP ports, users were mapping to the printers and everything was working great.  Test pages from either the user's WIN7 boxes or from the print server were draining from the queue immediately, sometimes so fast your eyes could miss the document being posted to the queue window.  User's print jobs from all applications were printing at all of the printers almost immediately.

Recently, a user had a need to print to one of the color printers that used to work, but then the print request would kill the local process.  I did some research and determined that it is likely that the WIN7 machines were patched(by IT HQ) and I needed an updated driver from Kyocera for this particular color printer.  I downloaded and installed the drivers from Kyocera on the 2008 box, deleted the color printer(queue) and recreated it with the new drivers and all was good with color printing again(printing no longer killed the local application-including explorer.exe just doing a test page).

Next, is where the strangeness comes.

A few users were complaining that printers they were originally mapped to and using with NO problems were asking for new drivers to be installed, and they weren't able to do so due to permissions errors.  As a local admin I could install the drivers, and after the new drivers were installed printing at the user's workstation was restored, BUT with this huge printing delay of several minutes.  AFAIK, this new drivers request is not the case for ALL users, including my own workstation, but the queue delays now seem to be universal.  So far, there isn't enough time to determine if all user's printer mapping were affected but it seems not at this time.

What seems to be happening now is that for EVERY test page or print document, the job now sits in the queue for at least a minute, sometimes two or three, before the printer "wakes up" and begins printing, whereas before print jobs would drain almost instantaneously for all printers.

Here is something else; when creating new print queues the driver choices for each printer type now have two selections, the old version and the newest driver version (delineated by the version #).  Perhaps these newer drivers are causing this issue? But why? and how do I fix it.

While it is possible that other SysAdmins(IT HQ) have applied patches to the 2008 server that have caused this behavior, I think it might be related to these new drivers being installed.

Is it possible that I installed the new printer drivers incorrectly, misconfigured the server somehow, or could this have been caused by a new server GPO or AV or IDS that has been recently applied by IT HQ?  This is driving me to insanity.

Any advice to get the queue drain time back down to zero would be appreciated. 

Hi.

Our users are getting all of a sudden the follwing error when they try to print on our Xerox printers:

splwow64.exe - System Error

The program can't start because x2utili6.dll is missing from your computer. Try reinstalling the program to fix this problem.

The users are local admins on their workstation, the printers are mounted automatically by GPO, these are Windows 7 x64 machines, it is affecting not all users (i can print myself without any issue).

I have tried restarting the spooler service and delete the C:\WINDOWS\SPOOLER\PRINTERS files without any luck.

The dll file is located in two places:

C:\Windows\System32\DriverStore\FileRepository\x2univx.inf_amd64_neutral_0d51743efa7abccc

C:\Windows\System32\spool\drivers\x64\3

Recently built a new print server on a Windows 2012 server (vmware virtual machine). No problems with the server but I cannot seem to print to any printers configured with host name rather than IP. The server can resolve hostname so it is not a DNS issue, but I can successfully print when printer port configured with IP. I can add this printer on my Win7 workstation by hostname or IP and print with no problems, which tells me there are no problems with the printer. I also think I can rule out any network issues as I can print via IP. The problem exists with 2 different printers (I currently only have 2 installed). 

Thanks for any help you may be able to provide