Question

'Error Reading HTTP Response Body' - web client, all browsers

Web Client Laserfiche Version 10

Updated April 30, 2019

asked on January 13, 2019 • Show version history

Hi all,

A client of mine is having an issue where they receive the error 'Error Reading HTTP Response Body' when attempting to Edit/View an electronic document.

I've noticed this tends to happen when the document is checked out, worked on, and then checked back in the first time. After it is checked back in, they can no longer access it due to the error. Looking at the raw document in the desktop client shows there doesn't appear to be anything wrong, so I'm at a bit of a loss as to what's going on.

They're currently running 10.3.1 - I have seen this error in all browsers and the latest versions of them.

I've attached a screenshot of what I see when I try to open a document that has been checked back into the repository. I have all administrative rights.

This occurs when you right click on the document in the web client, select 'Open' and then 'Electronic Document'. It checks the file out, but then cancels the download due to the error.

Any help on this would be greatly appreciated!

response error.png (21.46 KB)

| Download

error log.txt (2.43 KB)

| Download

0 0

Replies

replied on January 14, 2019

This error typically refers to the connection between the web client and the Laserfiche server. Is there some kind of scanning firewall that might be blocking the download?

0 0

replied on January 14, 2019

I suspected this too - however I have since found it may be related to the way the documents are uploaded and/or modified.

Example - I create a word document, drag and drop it into LF Web Access. Then open the document and it works fine. The user who at the other end can also open it. The documents the user has created, cannot be opened and cause the error to pop up either in the browser, or when it attempts to open in Word using the browser extension.

I suspect the fault may be in how the user is adding their documents to LF Web Access.

If I find what the exact cause is, I will update this.

0 0

replied on April 30, 2019

Disabling "BranchCache" service and restarting the server fixed the issue for us.

0 0

replied on January 14, 2019

Ok I think I have discovered the issue.

It appears to occur during the import process relating to the option 'Generate searchable text when importing documents'. With this ticked/enabled, any documents with externally pasted images inside a Word document header causes a corruption during the import process.

The document appears to import fine and check it self in, however you can no longer download/edit the document as per the original error.

Unticking/disabling 'Generate searchable text when importing documents' and importing the same problematic document works fine and users can download without error.

Is this a bug I should be reporting? What is the process to do so? In any case, I now have a customer who has imported a large number of documents that they're not overly interested in importing again.

0 0

replied on January 15, 2019

That's interesting, "Generate searchable text" shouldn't have any effect on the contents of the document. To report a bug, you can go through your reseller, who will be able to provide us with information about your setup as well as some sample documents.

0 0

replied on February 13, 2019

Hi Brian,

Sorry for the late reply to this - but everything had been working following the 'fix' I earlier, but has now returned.

I've had the user list me the steps they've taken that highlights what they do to reproduce the issue:

"I’ve been re-creating directories and saving files to them whilst on site using the laserfiche application (not the web version).

Today is the first time I’ve tried accessing files from the remote client / web version. It seems that once I’ve opened the document once, I cannot re-open it using WebAccess.

However, I’ve just created a new document from an existing one in: \Operations\1 Food Safety & Quality\1 NP 3 Programmes

I could not reopen the original version (Training & competency V3)
I was able to open the new version (Training & competency V4)
I reopened the Document (V4) and made changes and saved it (overwriting)
I reopened the V4 again (successfully) and closed without saving
I was then unable to open V4"

Any more thoughts on what this could be?

0 0

replied on March 6, 2019

That's really strange. And you're still getting the "Error reading HTTP response body" error? I don't know what it could be, I'd suggest opening a support case so we can investigate further.

0 0

replied on March 2, 2019 • Show version history

Dears,

I've the same issue when I use SDK DocumentExporter.

I run my application on LF server itself and same issue occurred.

Document Total size size= 358 MB

Any suggestions ?

0 0

You are not allowed to follow up in this post.

Question

Question

'Error Reading HTTP Response Body' - web client, all browsers

Replies

Sign in to reply to this post.