Reader wont use print driver on print server

I recently posted this question on the user forum, my mistake, I know all the really smart people are over here!
I have developed a print-driver with a very special purpose - it launches an application on the machine on which it is installed - and which also has an electronic signature pad connected to it - and captures a handwritten signature and embeds that into the pdf file just printed, keeping the document in electronic form.
This means that if someone using computer A wants the person using computer B to sign a document, they just print that document to computer B's shared instance of this print driver. For this to happen, the print driver on the server computer must be used.
There is an issue of "client-side" rendering implemented by MS since sometime after windows 2000. This can be disabled (at least turned off) and I have done everything I can do to force "server-side" rendering for this print driver.
However, Reader and Acrobat simply won't honor these settings - in all cases these 2 insist on using the local copy of the driver (which must exist on the local computer too - windows now copies that driver from the server each time the server driver is updated).
ALL other applications that I've tested faithfully send the document to the server's driver (though they also "exercise" the local driver for some reason, I can see this through logging when it is activated - but I cannot see where/why the printing subsystem is making the decision to forward it on).
To recap - other applications faithfully "render" using the server's driver on the server machine, Acrobat and Reader render using the client driver on the client machine.
I am more than willing to develop a print provider, print processor, or port monitor for my print driver - if I knew enough about which one of these is best targeted for this particular problem. It was hair pulling enough to figure out how to do the driver to begin with, this time I'd really appreciate any advice about which one of these I need to tackle rather than spend days developing one realizing I should have developed the other.
Or ... if there is something I need to set in Reader/Acrobat properties OR something in the print driver itself (which is, BTW, based on MS pscript5, i.e., not monolithic) that I might need to do ?
Thanks very much for the help
Nate Clark

Hi,
Have you tried the following steps:
1. Delete the printer from control panel -> printers
2. Open Services.msc and stop and start the Print Spooler service
3. Open Print Management(Open command prompt, type in printmanagement.msc or type print management in to the start menu search box)
4. In Custom Filters -> All Drivers right click the printer driver you want to remove and select Remove Driver Package
Thanks.

Similar Messages

Wireless network printer using print server

I have a USB HP LaserJet 3015 printer connected to a print server, Level One FPS-3003 and then connected using RJ-45 LAN cable to my wired/wireless LAN switch router. It works correctly with all my Windows XP and Vista pcs on the LAN wirely or wirelessly.
I recently bought MBA and configured it to connect the printer wirelessly. Before that, I connected the printer directly onto the MBA and it works like a charm. Once I complete the setup and I tried to print a page from Word Mac 2008. It failed. The print job showed that the Printer Paused and job status was stopped. I tried to click the button of Resume Printer and the printer became Printer Ready but the print job status remained Stopped. I clicked Resume button (Resume printing of selected jobs) and the printer changed to Printer Paused.
It appears to me that the print server does not like Leopard. I look at the print server menu and the OS requirements are stated Windows 98 SE/ME/2000/XP/2003 and HP-UX, Unix, Linux and RFC-1179 LPD System. Is there any workaround to make it work with Leopard. Thanks!!

Usually you'll find all the info you need listed under unix or linux (print server manual). Oh, but I see the manual is for Windows only.
The easiest printer setup will be to plug the printer into USB port 1 and use IP Printing > HP Jetdirect protocol. No Queue name. Refer to manual page 50 - TCP/IP port 9100 equals HP Jetdirect protocol.
For scanning, you can try the TWAIN-SANE drivers:
http://www.ellert.se/twain-sane/

Using printer server

i have a laserjet brother printer using usb port.in order to make this printer a network printer i bought a linksys printer server which is my printer connected and the printer server is connected to the wireless router.how i can connect to that printer?

Hrmm, not sure if I quite understand your question, but here is a go.
Most "Wierless Print Server/Router" combos have 4 sets of RJ-45(ethernet) connections and one USB port to plug in a printer. So you can just plug the printer directly into the Router itself.
Now if you bought a "wierless router" and a seperate "wierless print server": Your computers connect to the router RJ-45(Ethernet), and the printer to the "Print server" USB. You need to turn on wierless on your router, and give the "print server" and IP address on your network. That will be the tricky part if your unfimiliar of how to set up the "print server". Once you give your "print server" and IP address it connects to your network and you can use this IP address to poit to the printer on the network. Think of it as plugging a network card into a computer, your just connecting a network card to a printer. Though the way to configure the "print server" will be different, and probably should contact the manifacture to help you on that.
Now, if you accidentaly bought just a "Wierless Router", you can only share the printer while connected to your computer by USB. This means that this computer has to be on when someone wants to print to the printer.. still works wierles, but the mechanics and pro's and cons are different of this setup.

VersioningError when Using JDBC driver for SQL Server with RMI

Hi,
I wrote a simple class for inserting rows into a database. The database is SQL Server 2000, and I am using weblogic's mssqlserver4 driver. The class works fine, but when I try to export the class as a remote object (using Sun's RMI implementation, not Weblogic RMI), I get the following error:
Exception in thread "main" weblogic.common.internal.VersioningError: No WebLogic packages defined in CLASSPATH at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:35) at weblogic.version.<clinit>(version.java:18)
at weblogic.jdbc.common.internal.FileProxy.initFileHandles(FileProxy.java:30) at weblogic.jdbc.mssqlserver4.BaseConnection.prepareConnection(BaseConnection.java:215)
at weblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:34) at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:151) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171)
Can anyone tell me why this happens? What is difference between using the driver standalone and using it with RMI? Does it have anything to do with the fact that I'm using Javasoft RMI and not Weblogic RMI? I'm pretty sure I have the classpaths set up correctly.
Thanks,
Bo

Bo Min Jiang wrote:
Hi,
I wrote a simple class for inserting rows into a database. The database is SQL Server 2000, and I am using weblogic's mssqlserver4 driver. The class works fine, but when I try to export the class as a remote object (using Sun's RMI implementation, not Weblogic RMI), I get the following error:
Exception in thread "main" weblogic.common.internal.VersioningError: No WebLogic packages defined in CLASSPATH at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:35) at weblogic.version.<clinit>(version.java:18)
at weblogic.jdbc.common.internal.FileProxy.initFileHandles(FileProxy.java:30) at weblogic.jdbc.mssqlserver4.BaseConnection.prepareConnection(BaseConnection.java:215)
at weblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:34) at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:151) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171)
Can anyone tell me why this happens? What is difference between using the driver standalone and using it with RMI? Does it have anything to do with the fact that I'm using Javasoft RMI and not Weblogic RMI? I'm pretty sure I have the classpaths set up correctly.
Thanks,
BoHi. Show me the whole stacktrace of the exception. The issue seems to be the driver licensing
code, which is looking for the bea.license file, and not finding it. Have your code run a System command
to find and print out the classpath it thinks is in effect. You will then see if the license file is there.
Joe

Read File using File adapter from remote server

I need put poll on remote directory for files. Can some one tell where to put the remote connection details?
Thanks
KK

Sorry dumb question!!!! We can use GetFile operation in FTP adapter.....
Thanks
KK

CP1217 vs. Network Print Server

Hi,
I'm trying (and failing) to get my CP1217 (colour lasjet) working with my network print server (Netgear WGPS606).
The CP1217 works fine connected directly (USB) to the computer, and the WGPS606 works fine (otherwise I wouldn't be typing this - and it worked fine with my previous (HP) printer).
When the CP1217 is hooked up to the WGPS606 (and after the printer/software setup is done so that the printer is setup on the IP printer port), the HP print monitor (prnstatusmx.exe) reports that it isn't connected, and nothing prints. The WGPS606 status/diagnostics however report that it is connected (although it is clearly true that the printer is no longer locally connected.)
I have three questions - all help appreciated:
Has anyone got the CP1217 (or a printer from the same series) working with a WGPS606? (If so, how?)
Is the CP1217 compatible with a network print server (apart from the HP wireless kit thing which wouldn't do what I need)?
Does the print monitor (prnstatusmx.exe) only "see" locally connected printers, regardless of what port settings are set for the printer?
Thanks in advance...

I've been using a CP1217 with a Sitecom LN308 print server (which is cabled to my switch) since late March and it's fine, so the answer to your question whether it works with anything other than the HP print server is a resounding 'Yes'. Initially I just installed drivers as I was in the middle of an Open University assignment and wanted to print a.s.a.p (my poor old DJ840C was struggling). Today I decided to install the Toolbox so I can monitor the toner levels etc, as I'm about to start another block in my OU course and have lots of course text to print. That's where the problem started as the Toolbox is seeing the printer via the Sitecom but there's a big cross beside it and I can't access the status monitors etc. I've posted this as I'm hoping someone can tellme if/how this can be made to work.
You don't say if your print server is wired or wireless - if the latter, might this be an issue?
You said you've installed it using IP (I take it you've used a local TCP/IP port with the print server IP no?) - have you tried installing it as a local crown port using \\<print server name>\Printer name? Might be worth a go.
Good luck.
JayJay

Can I use flash drive in Windows that install on Oracle VM Server

Dear everyone,
I install Windows server 2003 on Oracle VM Server x86. I can use .iso file by copy iso file to /OVS/iso_pools and add resource. But I want to use flash drive on Windows server 2003 that installed on Oracle VM. I don't know how to do or it can do. I want to plug flash drive in Oracle VM Server and can use it on Windows server 2003
Thank you so much for advance
Fujimaru

It looks like you will not be able to use it without continually stopping and starting the guest and editing the vm.cfg file to add the physical device once it is mounted on the DOm0

Using JSP & JDBC driver for SQL Server 2000 on Red Hat

I successfully have a .jsp app running on windows server 2000 using JDBC
driver for SQL Server 2000. Which I installed in order to the following
Red Hat:
http://msdn.microsoft.com/MSDN-FILES/027/001/779/install.htm
I moved the .jsp app over to the Red Hat 9 server running Tomcat, while
keeping the MS SQL 2000 on windows. The issue I have is setting up the
JDBC driver for SQL Server 2000 on the Red Hat server.
I created a folder called /usr/java/MSSQLdriver and unzipped the tar file with
the driver for SQL Server 2000. And ran the install.ksh script.
The /usr/java/MSSQLdriver/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
I chmod 0777 each of the *.jar files.
I then went into /etc/profile.d/tomcat.sh and adding the following:
CLASSPATH=.;/opt/msSQLjdbc/lib/msbase.jar;/opt/msSQLjdbc/lib/msutil.jar;/opt/msSQLjdbc/lib/mssqlserver.jar
Each time I login and pull up the termial I get the following error:
bash: /opt/msSQLjdbc/lib/msbase.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/msutil.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/mssqlserver.jar: cannot execute binary file
And can't connnect to the database within the .jsp app.
Is there anyone out there using DBC driver for SQL Server 2000 on the Red Hat server?
Michael

Sorry, I needed to correct some information of where the drivers were installed.
I created a folder called /usr/java/MSSQLdriver/new and untar the Microsoft file with the driver for SQL Server 2000. I ran the install.ksh script "sh install.ksh"
installed the driver into the default directory "/opt/msSQLjdbc".
The /opt/msSQLjdbc/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
Michael

Specifying Partner Failover in odbc.ini for Linux ODBC driver for SQL Server

Hi,
We are trying to specify the partner failover when making connections via Linux ODBC driver for SQL Server. Do you know a way to specify partner failover in the DSN entry in odbc.ini?
We are using Linux ODBC driver for SQL Server and unixODBC DriverManager.
Our DSN is:
[MyDSN]
Driver=ODBC Driver 11 for SQL Server
Description=MyDSN
Server=MySERVER,<port>
I also tried to use the following connection string in Python (via pyodbc) bypassing the DSN and connecting using the server name.
cnxn = pyodbc.connect("Server=server1,<port>;UID=sa;PWD=<pwd>;Driver=ODBC Driver 11 for SQL Server;Failover_Partner=Server2,<port2>;Database=MyDB")
If the standby DB is on server1 connection fails. It doesn't try server2. If the DB is principal on server1 connection succeeds.
Thank you,
Liviu
LLL

Hello,
Did you use ODBC Driver for SQL Server to connect to database that uses database mirroring?
According to
the BOL,it does not list "Failover_Partner" as ODBC Driver for Linux connection string keywords.
But ODBC driver for Linux supports
AlwaysOn Availability Groups or Failover Cluster Instance by specify MultiSubnetFailover=True when connecting to a SQL Server 2012 availability group listener or SQL Server 2012 Failover Cluster Instance.
The following case is about similar issue and it seems that ODBC Driver on Linux does not recognize Failover_Partner in connection string. (Not test myself).You can refer to:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6a8b5223-066d-4493-84a3-b5374a32e433/native-client-on-linux-does-not-recognize-failoverpartner-in-connection-string?forum=sqldataaccess
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

A number of vendor drivers written for OS X cannot be used when connecting via SMB to a printer that is shared by Windows. This is due to limitations of the driver.
In some cases, if you were to enable the LPD Print Service in Windows, you can connect to the share using the same syntax as SMB but on the Mac you would use the LPD as the protocol.
If you can reply with the brand and model of printer you have then we may be able to provide more information.

Printer server always uses Generic Postscript Driver so cannot print!

I have setup print server in Leopard Server with my 2 x HP 2600n Lasers, I have installed the HP drivers but when I try to add the printer to the pool it always uses the generic postscript driver which the printer will not work with, any suggestions?
Thanks

The 2600n series uses host-based printing and will not print over LPR or IPP. The host computer will only communicate with the printer over BonJour which won't work across subnets unless you have Wide-Area DNS-SD setup on your network. Leopard's print server only prints to printers over LPR or IPP but can advertise LPR and IPP queues via BonJour.

Auto Installation of a Print Driver from the Server?

Hi all,
I hope this is the correct forum for this question. I am fairly new at setting up Mac Servers and was looking for some advice. I am trying to set up a Mac 10.6 Server as a print server. I am familiar with setting up printing services on W2k3 servers, but have some questions about this on a Mac server. On a Windows server, once I have installed the printer with the correct driver and shared it out, users just need to connect to the server's print queue and the correct driver is automatically downloaded from the server and installed on the workstation. On the Mac server, it seems that even after I have set up the print queue and installed the needed driver, when I connect a Mac workstation to the queue, it automatically tries to use the Generic Postscript Driver. I then have to manually download and install the needed driver for the printer. Is there any way to get the Mac workstations to automatically download and install the driver from the server, or do I have to pre-load the needed driver on each Mac that will be using the shared printer?

tmcbride wrote:
Hi all,
I hope this is the correct forum for this question. I am fairly new at setting up Mac Servers and was looking for some advice. I am trying to set up a Mac 10.6 Server as a print server. I am familiar with setting up printing services on W2k3 servers, but have some questions about this on a Mac server. On a Windows server, once I have installed the printer with the correct driver and shared it out, users just need to connect to the server's print queue and the correct driver is automatically downloaded from the server and installed on the workstation. On the Mac server, it seems that even after I have set up the print queue and installed the needed driver, when I connect a Mac workstation to the queue, it automatically tries to use the Generic Postscript Driver. I then have to manually download and install the needed driver for the printer. Is there any way to get the Mac workstations to automatically download and install the driver from the server, or do I have to pre-load the needed driver on each Mac that will be using the shared printer?
A Mac Server can distribute Windows print drivers (along with settings) to Windows clients. It does it exactly the same way as Linux Samba servers and (older) Windows servers. This is done by creating a special hidden share point (using SMB), it is special in that it uses the name print$ the drivers and settings are then loaded (from a Windows PC) in to this share, and subsequent PCs can then automatically download them.
See http://www.techrepublic.com/article/techrepublic-tutorial-automate-desktop-print er-setup-with-samba/1053286 for some more information on how to do this.
Note: My past experience has seen the associated .tdb databases for this function stored on this share often get corrupted meaning one had to re-upload (from a Windows PC) the drivers again. Also despite the automatic distribution of drivers and settings being something Windows has done for decades, Apple are still very poor at this in terms of the equivalent Mac (server) to Mac (client). Finally, I have not seen (yet) whether this approach is possible with Windows 7 clients.

Printing problems using a print server

I am having trouble printing across my local network to some printers. This is a mixed wired and wireless LAN.Lan works fine as the windows machines print with no problems.
Printing takes place using a Trendnet TE 100-P21 Print Server. This box is connected to my network with a CAT6 cable. It has 2 USB and one Parallel port.
The Mac can print to the parallel printer with no problem. Installation was easy and painless. It found the other two printers (the USB ones) just as easily, installed drivers, etc. It even knows when they are idle or not.
_It can print to the HP 6L, which is the only one that has a parallel connection._ (I think that must be important)
_But it can’t print to the other two, both of which have USB connections._
Here are the Queue Names that the Mac reported. (In the below notations, P3 denotes the parallel printer port, U1 the first USB port, and U2 the second USB port on the print server.)
HP6L (parallel)
URL: dnssd://PS-700AED-P3._printer.tcp.local.
*Cannon i9900* (USB)
URL: dnssd://PS-700AED-U1._printer.tcp.local.
*HP ColorLaserJet 3500* (USB)
URL: dnssd://PS-700AED-U2._printer.tcp.local.
Windows machines on the network can print to all three printer with no problem, so we know printers, print server, network and cables work. When hooked up directly to the printer (at least the HP 3500) the Mac can print as well. But not when connected via the print server.
Eventually the job times out and the HP 3500 spits out a page that reads
PCL XL error
System: KERNEL
Error: IllegalTag
Operator: Vendor Unique
Position 8
Any thoughts?

I assure you that changing print server will not fix this issue. You MUST have a CUPS driver to print to a non-postscript, not-intended-for-network printer via the standard comm protocols available in OS X and on nearly all print servers. The Gutenprint drivers included by Apple are CUPS drivers, as opposed to the old Mac-style "monolithic" drivers.
* It is true that using a postscript driver to print to a postscript printer would work for the TrendNet as well as nearly All other print servers. Postscript is the native output (well, along with "packaged postscript" = PDF) of OS X, so a postscript driver IS A CUPS driver by default.
I hope this helps you avoid the hassle of buying another brand of print server, only to find out out it is the same.

Problem Installing a LaserJet P1606dn on a printer server using the HP UPD

I'm trying to setup a LaserJet P1606dn printer as a local printer on a 64bit Server 2003 print server. I'd like to use the HP Universal Print Driver as the printer driver for Citrix compatibility (per the HP whitepaper entitled "HP printers supported in Citrix XenApp server environments"). I successfully downloaded, extracted and installed the latest HP UPD PCL5 driver on the print server without issue. I then successfully added the P1606dn as a new local printer (using a new Standard TCP/IP port directed to the IP address of the printer) and configured it to use the UPD PCL5 driver. Everything appears ok with the setup, but when I try to print a test page, nothing prints out.
I've confirmed that I've configured the TCP/IP port with the correct address and that the printer is connected to the network and pingable from the print server. I also tried using the HP UPD PCL6 driver with the same result.
Thanks.

Hi @yamIT ,
I read your post and see that you need a driver for 64 bit Server 2003. I would be happy to help you.
There is a 64 bit listed under the Basic Drivers.
Here is a link to the drivers web page for the Server 2003 drivers. HP LaserJet Pro P1606dn Printer.
Feel free to click the Thumbs up button below if this helps.
Have a nice day!
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

HP DeskJet 712c Driver and Wireless Print Server Setup

I have recently purchased a MacBook Pro and am unable to setup my printer to print. Previous to using the MacBook Pro I was using a windows machine without any trouble printing to this printer, however now I can't locate the printer on a list of pre-installed drivers for Mac. I've already checked HP's website and was unable to find any drivers that were for Mac OS. What is a good alternative driver source? Once I do get the driver what would my next steps need to be to set up the wireless print server to work with my mac?
Printer: HP DeskJet 712c
Wireless Print Server: D-Link DP-311P
I would be grateful for guidance to go about this process so that I can use my printer again.
MacBook Pro 2.16GHz Mac OS X (10.4.6)

HP-provided drivers don't support network printing. You'll need to install Foomatic (a PPD interpreter), ESP ghostscript (postscript translator) and the 712c PPD from:
http://www.linuxprinting.org/macosx/foomatic/
http://www.linuxprinting.org/showprinter.cgi?recnum=HP-DeskJet712C
Then, since we don't have the auto-setup software for OS X, you need to review the print server manual and find out which IP printing protocol to use. The easiest is HP Jetdirect (called TCP/IP raw port printing in many manuals) if it's available, because it doesn't require the device queue name.
Good luck.

Reader wont use print driver on print server

Similar Messages

Maybe you are looking for