You are viewing limited content. For full access, please sign in.

Question

Question

Documents not printing correctly from Web Client 10.2

asked on April 27 Show version history

Anyone else having issues with printing from Web Client 10.2?

Printing a Tiff only gets partial image when printed from Web Client.  Same Tiff printed from desktop client prints complete document.

Printing a PDF gets either the document text OR it prints a cut off version of the image.

All documents get the URL printed for the Export Streaming Handler which I would like to remove.

Edit - sorry for the redactions but the ticket has feed formulations which are proprietary.

pdf print as text.jpg
0 0

Replies

replied on April 27

Hi Michelle,

Our QA team took a look into this and printing seems to be working fine in the general case. The next step I'd suggest is to talk with your reseller about opening up a support case. Support can look into whether there's something specific to the documents you are trying to print that's causing this behavior. 

0 0
replied on April 28

I will pursue opening of a support case with my reseller.

0 0
replied on May 10

I am having the same issue. Although on some PCs, the image will not download to print at all, causing Chrome to crash or IE to lock up.

0 0
replied on May 10

In Web Client 10.2, we had switched to using pdf.js to handle printing images. However, the version of pdf.js we are using has a bug when printing from Internet Explorer where only the top half of pages get printed. A fix is being looked into and we'll update the thread when more information is available.

Perhaps as a workaround for now, users can use another web browser besides IE or Edge if they need to print images.

If you are having other issues with printing in Web Client 10.2, please contact your Laserfiche reseller to open a support case.

0 0
replied on May 25

We are having the exact same issue since upgrading to 10.2.1 last week.

Did you get any resolution to this issue?

0 0
replied on June 5

Is there a fix for this problem yet?

0 0
replied on June 5

We are currently testing the fix for this and looking into releasing a hotfix for it.

0 0
replied on June 15

Same here, lots of our customers are complaining they cannot print using IE via Web Client.

When will this hotfix be available?

0 0
replied on June 15

KB 1013868

0 0
replied on June 21

Has anyone else tried the hotfix, yet?  And if so, did it work for you?

For us, after installing the hotfix, everything appears to work until the prompt where I select a printer to print to. The prompt doesn't show up and clicking on the printer icon (top left corner) does nothing (meaning, nothing happens).

Chrome continues to work. This experience is with IE, which is our corporate preference.

Appreciate your time and suggestions, thank you!

Side note: the toolbar/menu at the top of the window is skewed in IE.

In Chrome it looks like this: .

In IE it looks like:  ...no matter the size of the window.

0 0
replied on June 21

Hi Sarah, 

 

Please delete your browser cache (Internet Options->Browsing history->Delete, and make sure Temporary Internet files and website files is checked) and try again. Also, make sure you swapped out the entire 'Viewer' folder rather than copying the file contents. Missing a single file can break the PDF viewer and has caused issues similar to what you've described for us internally. 

 

If that doesn't work, please contact your reseller and tell them to open a case with our support team. Please provide full IE 11 version, a video reproducing the issue, and a fiddler trace while the issue is being reproduced (your reseller should know how to take this trace). 

0 0
replied on June 21

Thank you, Ryan - we will double-check and try your suggestions again after hours. We backed off the hotfix this morning because it caused a "Script Error" on many documents (particularly those that appeared to not have "generated pages" done on them.)

0 0
replied on June 21

Yeah, it looks like the Web Client is running into errors loading the JS for the PDF Viewer. One other thing that comes to mind- Are you currently on Web Client 10.2.0 or 10.2.1? The hotfix is specifically for 10.2.1. 

0 0
replied on July 14

Ryan, has there been a fix to the hotfix to correct the script error that Sarah was getting on her documents? 

I would like to put the hotfix in place to stop using the workaround of downloading and printing (lots of local desktop cleanup involved with this) but don't want to introduce the script error to my users.

Please advise, thanks.

0 0
replied on July 14

The hotfix is safe to apply. We can't reproduce Sarah's issue internally with our hotfix. Multiple customers have applied the fix successfully, and this is the only known instance of someone running into trouble with it. To my knowledge, Sarah's organization hasn't reached out to open a support case through her reseller for the hotfix and she hasn't replied to my post earlier, so I can't speak to the issue she was experiencing.

 

Just make sure when you apply the hotfix, you're specifically on 10.2.1 (not 10.2.0) and that you swap out the entire 'Viewer' directory. If you do run into any issues with the hotfix, ask your reseller to open up a support case and we'll fix any problems that occur.  

0 0
replied on July 14

Ryan, thanks for the update.  I have the 10.2.1 update on my calendar and will apply the hotfix at that time. 

When you mention swapping out the entire 'Viewer' directory, will this occur via the application of the hotfix, or do I need to look elsewhere and do something else to make that happen?

0 0
replied on July 14

This is a static file hotfix, not a hotfix deployed by an executable. The hotfix in the KB contains a zipped directory with patched source files. To apply the hotfix, you back up the original directory and replace it with the directory from the KB. See the instructions here.

 

 

0 0
replied on June 22

We were having the same problem and switched everyone to Google Chrome from IE and that corrected the issue on our end.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.