Problems observed in QZ-Tray 2.0.0 release

[dave.r...@gmail.com]

I am attempting to run tests using the QZ-Tray v2.0.0-alpha1-1 version.

Things connect correctly, but when I perform the following steps:

1. Click on the "Find Default Printer" button
Current printer is correctly reported as "HP Officejet Pro 8600 (Network)"

2. Click on the "Pixel Printing" tab

3. Click on the "Print PDF button"
The following error is reported:

Error: Invalid name of PrintService.
at WebSocket._qz.websocket.connection.onmessage (http://persistentendeavors.com/brickwire/BrowserPrinting/tests/qz-print_2.0.0-alpha1/js/qz-tray.js:240:44)

On another test sequence:

1. Click on the "Pixel Printing" tab

2. Click on the "Microsoft XPS" link
The following response appears on the screen:
Found: Microsoft XPS Document Writer
The current printer is reported as "Microsoft XPS Document Writer"

3. Click on the "Print PDF" button
The XPS viewer appears on the screen.
However, the output PDF result appears in the upper left corner of
the page, compressed into an area about 1.0 x 1.5 inches.

So, there are two different problems observed:

1. The default printer is not recognized as a valid PrintService.
2. The PDF output is dramatically compressed.

Do you have any insights as to what might be going wrong here?

Dave Eland

[Tres Finocchiaro]

However, the output PDF result appears in the upper left corner of
   the page, compressed into an area about 1.0 x 1.5 inches.

This is a known issue with alpha-1.  For now, please set the page resolution to something that matches your PDF printer (i.e. Density of 600).  We're working on making this a default for alpha-2 for all Pixel printing jobs.

HP Officejet Pro 8600 (Network)  Invalid name of PrintService.

This may be fixed with alpha-2 as well.  There's a bug with printer searching for Windows printers that are on a hostname starting with "\\E.... ".  Does yours fall into this category?

If not, do you mind if we track this on our GitHub tracker?

- Tres.Fin...@gmail.com

Dave Eland

--
You received this message because you are subscribed to the Google Groups "qz-print" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qz-print+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dave.r...@gmail.com]

Thanks for your timely reply.

Setting the printer resolution to 600 fixed the "shrinkage" problem.

It would be fine if you wish to track the PrintService issue on your GitHub tracker. Please note that this same problem showed up when I was using the 1.9.5 version yesterday (before downloading the 2.0.0 version). Prior to that everything was working fine. After the problem showed up yesterday, and again today the PrintService error is reported whenever I try to print using QZ (printing to that printer works fine using other approaches -- e.g. print option in Chrome).

[dave.r...@gmail.com]

Forgot to mention that my host name does NOT start with \\E...

[Tres Finocchiaro]

Dave, thanks for the response.  In regards to your bug, I'd like to know how to reproduce it before proceeding with a bug report as we're having a hard time reproducing on our end.

- Tres.Fin...@gmail.com

On Thu, Jan 7, 2016 at 6:46 PM, <dave.r...@gmail.com> wrote:

Forgot to mention that my host name does NOT start with \\E...

[dave.r...@gmail.com]

Tres:

Here is some additional information about my experience with the following error message:

"Invalid name of PrintService"

1. My environment is Windows 7 (running in a Bootcamp partition on a MacBook Pro laptop).

2. Only my "HP OfficejetPro 8600 (Network)" printer experiences this error. Things work correctly for the following printers in my system:

Microsoft XPS Document Writer
ZDesigner GK420d (label printer -- USB connection)
POS-X Thermal Printer (receipt printer -- USB connection)

3. The problem only happens when attempting to print in the QZ context. All other use of the printer works just fine (e.g. printing from Chrome, Microsoft Word, etc.).

4. This problem happens in the 2.0.0, 1.9.5, and 1.8.7 version of the QZ-Print environment (presumably it would happen in all QZ Print versions).

5. This is only a recent phenomenon (the last week or so). Prior to that everything was working fine. Something has happened on my system that makes my HP printer not work correctly in the QZ environment.

6. The error occurs upon invoking the qz.printPS function.

7. Google searches have hinted that one possible source of this problem is Java permission issues (using the Java configuration tool to set permissions to the lowest level did not resolve my problem).

It has been my hope that your extensive experience with printers would lead us to a solution for the problem we are having.

I suspect that the problem can only be easily replicated on my computer system. If you would want to utilize some tool (e.g. join.me) to do remote debugging on my system I would be happy to work with you on doing that.

Dave

[dave.r...@gmail.com]

P.S. Here is a link to the discussion about Java permissions:

https://community.spiceworks.com/topic/799983-java-permission-issue

[Tres Finocchiaro]

Dave,

Thanks for the spiceworks link as well as the very detailed information.

Since this problem only occurs with a single printer, my best guess is that it is a problem specific to the HP printer or driver configuration.

In my experience, HP drivers can be quite complex and when problems arise they can be more difficult to troubleshoot.

In a few rare occurrences, I've run a special HP driver removal tool (a very long multi-reboot process) to fix printer anomalies, but at a very minimum, I would recommend uninstalling the HP driver and reinstalling it to see if that helps.

The article you've linked doesn't reveal too many specifics, but if it is the same cause, it may be a corrupt registry entry that Java can't traverse to.  Since Java is a mulit-platform framework, it's not uncommon for something to work OS-level, but break in Java and the causes are often deep inside the Java C++ source code, which we're not qualified to debug.

That said, I'll contact you directly about a remote session.  Thanks agian.

- Tres.Fin...@gmail.com

On Fri, Jan 8, 2016 at 1:12 PM, <dave.r...@gmail.com> wrote:

P.S. Here is a link to the discussion about Java permissions:

https://community.spiceworks.com/topic/799983-java-permission-issue

[dave.r...@gmail.com]

One big mystery is what happened on my system to cause this issue. I am not consciously aware of any updates of any kind (much less something that would be related to this issue).

[Tres Finocchiaro]

One big mystery is what happened on my system to cause this issue.  I am not consciously aware of any updates of any kind (much less something that would be related to this issue).

If your HP driver is a consumer-driver, they do (from time to time) ask to self-update... although most people turn that off and that would likely be something you'd remember.

The idea of a registry entry getting corrupt happens from time to time and often involves the permissions.  Registry items have permissions very similar to NTFS permissions, so if a group has lost ownership of a key or value in the registry, Java might bark.

Another things that I'm seeing more and more is solid state drives acting up and requiring a forced chkdsk.  I'm not sure if this is due to the read/write accuracy or just my own bad luck.

I know where the registry settings are stored, so I can at least check that portion out remotely.  Let me know if you require remote assistance for this particular problem.  As a premium user, you have full support.:)

  

- Tres.Fin...@gmail.com

On Fri, Jan 8, 2016 at 1:44 PM, <dave.r...@gmail.com> wrote:

One big mystery is what happened on my system to cause this issue.  I am not consciously aware of any updates of any kind (much less something that would be related to this issue).

[dave.r...@gmail.com]

Tres:

As you suggested, I uninstalled the HP device software on my system and then reinstalled the printer.

This has fixed the problem!

Much thanks for your assistance!

Dave

[Tres Finocchiaro]

Thanks for the status update, much appreciated. :)

- Tres.Fin...@gmail.com