GlennLawr

Hello

I have two forest, one for resources (server, printer.....) and the other with user accounts and windows 7 clients. There is an unidirectional trust between the two forest and both are based on Windows 2008 DC but with a windows 2003 functional level.

When users want to add a printer by using the search in active directory functionality they can't see the ones that are in the resources forest. From what I learned this search can't work for object that aren't in the forest to which the computer belongs. I am looking for a solution to make the printers from ressources forest available in the user forest. From now I found that FIM may do what I need but there isn't a lot of informations about this usage of FIM. Do you have information about that or another solution?

Thanks

I am trying to migrate about 500 printers from the old print server to a new print server running Windows 2008 R2.  The old server is Windows 2003.  I have went through several iterations trying to get it to work.  I had two different errors at first but was able to correct the "print processor" error using this forum.  But I am unable to figure out how to fix the "printer driver unknown" error.

The Event ID is usually 92 and the error description is as follows:

"Prntbrm.exe (the Printer Migration Wizard or the command-line tool) failed to restore print queue "QueueName".  The restore process will continue, skipping this queue.  Error: 0x80070705.  The printer driver is unknown.

I get this error for multiple models of printers, but most of them are HP branded printers.  I have downloaded the 64 bit printer driver from the HP web site and installed them onto the Windows 2003 print server and saved that out to a file, then import that file into the Windows 2008 print server using Print Management.

The issue appears to be related to any driver using the HP Universal printer driver.  It is used for multiple printer models and each model that uses that driver did not get migrated.

Information    16.07.2012 12:05:43    Microsoft-Windows-PrintService    307    Printing a document    Document 84, file.xlsx owned by pak_el on UH15-RR01 was printed on Kyocera
 FS-1370DN KX [BC1-407] through port px01-kyo1370-3.  Size in bytes: 165298. Pages printed: 2. No user action is required.
Information    16.07.2012 12:05:43    Microsoft-Windows-PrintService    805    Print job diagnostics    Rendering job 84.
Information    16.07.2012 12:05:43    Microsoft-Windows-PrintService    842    Isolating printer drivers and other plug-ins    The print job 84 was sent through the print processor winprint
 on printer Kyocera FS-1370DN KX [BC1-407], driver Kyocera FS-1370DN KX, in the isolation mode 1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0.
Information    16.07.2012 12:04:10    Microsoft-Windows-PrintService    801    Print job diagnostics    Printing job 84.
Information    16.07.2012 12:04:10    Microsoft-Windows-PrintService    800    Print job diagnostics    Spooling job 84.

OS Name    Microsoft Windows Server 2008 R2 Standard
Version    6.1.7601 Service Pack 1 Build 7601
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    UH15-BC1-PS01
System Manufacturer    VMware, Inc.
System Model    VMware Virtual Platform
System Type    x64-based PC
Processor    Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz, 2666 Mhz, 1 Core(s), 1 Logical Processor(s)
BIOS Version/Date    Phoenix Technologies LTD 6.00, 13.10.2009
SMBIOS Version    2.4
Windows Directory    C:\Windows
System Directory    C:\Windows\system32
Boot Device    \Device\HarddiskVolume1
Locale    ¿¿¿¿¿¿
Hardware Abstraction Layer    Version = "6.1.7601.17514"
User Name    Not Available
Time Zone    Russian Standard Time
Installed Physical Memory (RAM)    4,00 GB
Total Physical Memory    4,00 GB
Available Physical Memory    3,16 GB
Total Virtual Memory    8,00 GB
Available Virtual Memory    7,15 GB
Page File Space    4,00 GB
Page File    C:\pagefile.sys

HP Designjet T610 44in [BC1-323]    HP Designjet T610 44in HPGL2    px01-hp610-1    Local Server
HP Designjet T610 44in [BC1-415]    HP Designjet T610 44in HPGL2    px01-hp610-2.is.local    Local Server
HP LaserJet 3055 PCL5 [BC1-311]    HP Universal Printing PCL 6    px01-hp3055-1.is.local    Local Server
HP LaserJet P2015 [BC1-406]    HP Universal Printing PCL 6    px01-hp2015-2.is.local    Local Server
HP LaserJet P2015 Series PCL6 [BC1-313]    HP Universal Printing PCL 6    px01-hp2015-1.is.local    Local Server
HP LaserJet P2015 Series PCL6 [BC1-317]    HP Universal Printing PCL 6    px01-hp2015-3.is.local    Local Server
HP LaserJet P2015 Series PCL6 [BC1-516]    HP Universal Printing PCL 6    px01-hp2015-4.is.local    Local Server
HP LaserJet P2055dn [BC1-401]    HP Universal Printing PCL 6    px01-hp2055-2.is.local    Local Server
HP LaserJet P2055dn [BC1-410]    HP Universal Printing PCL 6    px01-hp2055-6    Local Server
HP LaserJet P2055dn [BC1-503]    HP Universal Printing PCL 6    px01-hp2055-8    Local Server
HP Officejet Pro K8600 Series [104]    HP Officejet Pro K8600 Series    px01-hp8600.is.local    Local Server
Kyocera FS-1028MFP [BC1-510]    Kyocera FS-1028MFP KX    px01-kyo1028-1.is.local    Local Server
Kyocera FS-1028MFP KX [BC1-3 floor]    Kyocera FS-1028MFP KX    px01-kyo1028-6    Local Server
Kyocera FS-1028MFP KX [BC1-310]    Kyocera FS-1028MFP KX    px01-kyo1028-10.is.local    Local Server
Kyocera FS-1028MFP KX [BC1-4 floor]    Kyocera FS-1028MFP KX    px01-kyo1028-3    Local Server
Kyocera FS-1028MFP KX [BC1-506]    Kyocera FS-1028MFP KX    px01-kyo1028-11    Local Server
Kyocera FS-1028MFP KX [BC1-507]    Kyocera FS-1028MFP KX    px01-kyo1028-12    Local Server
Kyocera FS-1118MFP KX [BC1-405]    Kyocera FS-1118MFP KX    px01-kyo1118-4.is.local    Local Server
Kyocera FS-1118MFP KX [BC1-509]    Kyocera FS-1118MFP KX    px01-kyo1118-2.is.local    Local Server
Kyocera FS-1118MFP KX [BC1-UR]    Kyocera FS-1118MFP KX    px01-kyo1118-5.is.local    Local Server
Kyocera FS-1128MFP KX [BC1-501]    Kyocera FS-1128MFP KX    px01-kyo1128-1.is.local    Local Server
Kyocera FS-1135MFP KX [BC1-316]    Kyocera FS-1135MFP KX    px01-kyo1135-4.is.local    Local Server
Kyocera FS-1135MFP KX [BC1-502]    Kyocera FS-1135MFP KX    px01-kyo1135-2.is.local    Local Server
Kyocera FS-1135MFP KX [BC1-515]    Kyocera FS-1135MFP KX    px01-kyo1135-1.is.local    Local Server
Kyocera FS-1370DN KX [BC1-306]    Kyocera FS-1370DN KX    px01-kyo1370-2    Local Server
Kyocera FS-1370DN KX [BC1-310]    Kyocera FS-1370DN KX    px01-kyo1370-10_1    Local Server
Kyocera FS-1370DN KX [BC1-312]    Kyocera FS-1370DN KX    px01-kyo1370-4    Local Server
Kyocera FS-1370DN KX [BC1-316]    Kyocera FS-1370DN KX    px01-kyo1370-5    Local Server
Kyocera FS-1370DN KX [BC1-402]    Kyocera FS-1370DN KX    px01-kyo1370-7    Local Server
Kyocera FS-1370DN KX [BC1-405]    Kyocera FS-1370DN KX    px01-kyo1370-14.is.local    Local Server
Kyocera FS-1370DN KX [BC1-407]    Kyocera FS-1370DN KX    px01-kyo1370-3    Local Server
Kyocera FS-1370DN KX [BC1-502]    Kyocera FS-1370DN KX    px01-kyo1370-6    Local Server
Kyocera FS-1370DN KX [BC1-505]    Kyocera FS-1370DN KX    px01-kyo1370-9    Local Server
Kyocera FS-1370DN KX [BC1-512]    Kyocera FS-1370DN KX    px01-kyo1370-8    Local Server
Kyocera FS-1370DN KX [BC1-513]    Kyocera FS-1370DN KX    px01-kyo1370-1    Local Server
Kyocera FS-1370DN KX [BC1-RITRES]    Kyocera FS-1370DN KX    px01-kyo1370-13.is.local    Local Server
Kyocera TASKAlfa 181 [BC1-323]    Kyocera TASKalfa 181 KX    px01-kyo181-1.is.local    Local Server
Kyocera TASKalfa 300i KX [BC1-416]    Kyocera TASKalfa 300i KX    px01-kyo300-1    Local Server
Microsoft XPS Document Writer    Microsoft XPS Document Writer    XPSPort:    Local Server
OKI C9650dn    OKI C9650(PCL)    px01-oki9650-1.is.local    Local Server

Multiple printers just setup having this issue. Out of 6 printers configured to install via GPO 4 fail with the exact same error below.

2012-10-09 17:23:34.774 [pid=0x428,tid=0xdf4c] EVENT : The user 'STBPR06' preference item in the 'PRI_STB {FC84E1E0-9732-485C-BC59-751BB6B7A30A}' Group Policy object did not apply because it failed with error code '0x8000ffff Catastrophic failure'%100790273

What does this mean?

The only suggestion after an hour of researching I can find is permissions on the printer. But all 6 are exactly the same - default as everyone having read (print) access.

Users are logging onto a 2008 Terminal Server. Every user at the site is having the same issue when logging in to just one of the servers, not the other matching server, they work fine here.

What does the error mean? That's the log entry from the user.log - is there something further I can check? There's no more info in the Application log entry which basically matches above?

Environment and requirement:
On the print server 10.158.100.34 there are 8 shared printers, two of which are using the $ suffix as the share name. I hope these two shared printers are not able to be "seen" by users.

There were not any problems while a Windows 7 client trying to access the print server by \\10.158.100.34.

However, while a Windows XP client tried to access the print server by \\10.158.100.34, although those two shared printers with $ suffix as share name were not able to be seen, there was a "Printers and Faxes" icon. After opening this "Printers and Faxes", all the 8 printers installed on the print server were able to be seen, including those two $ printers.

Is there a way to prevent Windows XP clients from "seeing" the shared printers with $ suffix as share name? Thanks very much!

Windows Server 2008 64bit. 2 Network printers installed - Dell 1320c and Dell 1130n. All clients are Windows 7.

At varying times I get error in the System event log relating to the print spooler service.

ID:7031 Print Spooler Service Terminated Unexpectedly

ID:7034 Printer Spooler Service Terminated Unexpectedly

Some days this error doesn't appear at all, on other days it can appear a dozen times. Occasionally, (maybe once a month) the Print spooler service stops and no one is able to print. I manually start the service and everything starts working again.

As it isn't a huge headache I've always ignored these errors but now I'd finally like to get this sorted for good.

In another thread with a similar issue http://social.technet.microsoft.com/Forums/en-AU/winserverprint/thread/8c71eec3-3da0-4dbd-a897-76147e477410 Alan Morris suggests:

"Look in C:\ProgramData\Microsoft\Windows\WER\ReportQueue for any directory with spoolsv in the name.  There is a text based report.wer file that you can open with notepad.  Check the faulting module name"

I can see various report files, the faulting module name is StackHash_a190 - is that of any help to anyone?

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

Hi,

I need some urgent help on the below issue as i have been struggling since last 1 week for this issue. Let me describe it from the start

Here we go :- We have a Wincor 4915xe cheque book printer which is connected to a client machine (windows Xp) and we are using windows server 2008 R2- 64 bit terminal server . while logging to the terminal server we are able to see the redirected printer while giving any print job to the redirected printer it is giving us a bull shit error as " Needs troubleshooting" and in the event viewer we can see an event as " control point not found" whereas in the print server properties we can see the driver is available for both X86 and X64.

we have tried different solution to make it work while everytime we are getting the same event on all the windows server 2008 R2. could any body help me from this !!!

I am getting the below event and i have installed the printer driver manually in the windows server 2008 which shown me X64 drivers and to make it work from the client machine i have pushed the drivers of Windows\Xp X86 from the client machine.

Please let me know how to make it work and how to get rid of this event !

Your help is appreciated on this.

Event Details:-

Log Name:      Application
Source:        wnhprlm
Date:          10/9/2012 6:32:18 PM
Event ID:      1
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MUNMVS0104.ratnakarbank.in
Description:
StartJob(1240):control point not found.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="wnhprlm" />
    <EventID Qualifiers="16384">1</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-09T13:02:18.000000000Z" />
    <EventRecordID>2024</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MUNMVS0104.ratnakarbank.in</Computer>
    <Security />
  </System>
  <EventData>
    <Data>StartJob(1240):control point not found.
</Data>
  </EventData>
</Event>

We had Windows 2003 Terminal Servers and installed "fax printers" which all terminal server users could access. We use a VoIP fax product that has a plugin to the windows fax architecture, which worked fine. When we upgraded to Windows 2008 x64 Terminal Servers, we installed the VoIP plugin for fax and scan and it creates a Fax device in the printers.

When the user selects the fax device they get a screen asking if they want to connect to a fax modem or fax server. I've tried it both ways and it really doesn't matter because the result is the same. The next screen they get a message box saying to use the printer selected you must first create a fax account. Continuing gets the new fax dialog where you enter the fax number, subject, message, etc. When you click send, a "Print to File" window opens trying to save the fax in a folder as a .prn file - but there isn't any file name listed. Adding a filename and clicking save results in a message "the message could not be sent. the system cannont find the file specified."

What is going on here? Is there any way to have just a simple fax printer that everyone can share? Please help.

Hi,

We have several printers where jobs are randomly paused.  In the event logs event id 308 is logged that says: 

Document 344, <2> (Job 3725019543) Microsoft Word - PROGRESS REPORT owned by UserName was paused on libraryblack. This document will not print until the document owner resumes the print job. No user action is required.

Other jobs continue to print and if the user re-submits the job it will print OK.  The user is not pausing the jobs and the printer is in the ready state.  Is there any way to find why these jobs get paused?

We are running a 2008 R2 print server with AD with windows 7 clients. I have been having an issue with one building where some of our students don't get all the printers that are assigned via GPO. I would say that about 90% of the students do get all the printers but 10% don't. Of the printers that don't show up 2 of them were printers that were added to the GPO recently. Normally I would say to run a gpudate /force but that sometimes has no effect on the problem. The only thing that seems to work consistently is to delete the local user profile and have them log in again.

Does anyone have any ideas?

Thanks

We have a couple HP printers that are doing this.

The user will go to print something in the morning, and it will show the printer they use as "Offline", but the printer itself shows "Ready" on the front panel. She turns it off and back on, and now it will show "Online" under her printers and she can print.

We are using Print Servers, not USB. This only happens on a few of the printers.

Hello all, new to forum, hoping to find answers and help someone else out too....

Situation:

I have a 64-bit Win2k8R2 DC with 3 networked printers (2 HP, 1 Cannon). I've installed the drivers for each printer and they all appear "ready" on the server. I have a mix of XP and 7 clients, both 32 and 64-bit. 

Question:

Is it possible to install XP AND Win7 printer drivers (doesn't matter if it's 32 or 64-bit at this point) for the same printer? I don't want the XP clients grabbing the Win7 drivers and vice versa. I don't have a homogenous client environment where I have all XP or all Win7 OS's....yet. I assume (please correct me if I"m wrong), that if this were a Win2k3 server, then the XP clients would install the drivers just fine and the Win7 clients would error out. However, since this is a Win2k8 server, the Win7 clients would install the drivers fine and the XP clients would error out. Since all my printers have support for XP and Win7, I'm hoping to install the drivers for both OS and have the clients pull whichever one they need (not sure if this is even possible but hey, it's worth a shot).

Thank you for your time and help

Respectfully,

Gary

I have a Canon multipurpose printer which also is being used to scan files to a Server 2008 box.  Last week the server was rebooted and now the scanner will no longer save files to the network share.  I get an error from the Cannon scanner that indicates a TCP/IP problem, but I can see nothing that has changed. I can still see the file share from an XP machine and can successfully move files to the share.  I can also edit the file desitation settings on the scanner and save successfully to a share on an XP machine.  I've checked to make sure services are running and verified the Windows firewall is turned off.  I've tried recreating the share on the server and set permissions wide open but still no success.  I'm out of ideas and would be grateful for any assistance. 

Thanks,

Ed

I have this error on the system log of my Server 2008 R2 server

"The line printer daemon (LPD) service received a print job from pr2adm in an usupported print format. This can occur if the printer driver on the client is configured to use a print data type that is unsupported by this printer. The document may not print correctly as a result".

This is a spooler-LPDSVC error number 4006.

There is no other amplifying information, such as user or printer name/ip address, to narrow it down. 

Hi,

I have a Server 2008 R2 print server, serving a mixture of clients 7,XP (32&64).  We have Papercut (print logging) software installed on the server.

We are seeing intermittent jobs on Print Queues logged as workstation name instead of username, it is on random jobs i.e. Word, PDF, Internet Explorer and random clients.  Unable to find a common link as to why it happens

See Papercut kb - www.papercut.com/kb/Main/JobsOwnedByComputer

We have denied computers object as well as individual workstations on the Print Queue but it still allows computers to print.  It seems like a bug in Windows that this is still allowed to occur.

Any ideas?

Cheers

Ross

Have a Server 2008 machine.

Every driver I attempt to install to it gives:

Unable to install *Driver Name*, Type 3 - User Mode, x86 driver. Operation could not be completed (error 0x00000002).

I've restarted the server, restarted the spooler, stopped the spooler and deleted the contents of %WINDIR%\system32\spool\printers and finally stopped spooler and deleted everything under:

HKLM\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86\Drivers
HKLM\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86\Print Processors (except winprint)
HKLM\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86\Printers

All with no change.

This is a x86 Server 2008 and 100% definitely x86 drivers.

Hi

I have a 16-bit DOS application which runs as a Terminal Server APP on a Window 2008 server (32bit). (Machine with QuadCore Proc).

the application and printing worked fine on windows 2003.

Since migration users can use the app and print, but we regulary see that the dosprint.exe and ntvdm.exe freezes.

I allready changed Dosprint.exe to run as a windows 2003 - SP1. but problemes still continue.

Does someone has a clue ?

thanks a lot. Barry