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

Question

Question

Web Client - How to install Excel Previewer server side

Web Client
Updated April 30, 2021
asked on April 26, 2021

We have a client were we can preview Excel files, and one where we can not. With the preview configured it pops this loading box in the bottom left of the document viewer and then displays the spreadsheet in read-only right inside of the web browser.

Using the same browser and trying with another client's server on the same build or higher, I don't get this option, instead it just says Not Found.

How do we configure this for other clients?

0 0

Replies

replied on April 26, 2021

This should work out of the box. The first thing I would check is that you are using https with proper certificates. Misconfigured https is the root cause of many of these problems recently. Failing that, there may be something in the event viewer that will point you in the right direction.

1 0
replied on April 26, 2021

Just as I open an excel document in the web client and get the Not Found screen instead of the preview, I see an error posted in the event log each time.

Since it is over convoluted I will short the request:

404.0 - Not Found

The directory or file specified does not exist on the Web server.</

Physical Path</th><td>&nbsp;&nbsp;&nbsp;C:\Program Files\Laserfiche\Web Access\Web Files\document\token

Create the file or directory and try the request again.

I created the directory, now when I open the Excel document it says Forbidden to the user and I get this error.

403.14 - Forbidden

The Web server is configured to not list the contents of this directory.

A default document is not configured for the requested URL, and directory browsing is not enabled on the server

I don't think I want to enable directory browsing, so I am lost now.

 

 

0 0
replied on April 26, 2021

Laserfiche Document Preview Service exposes an endpoint like "/ldps/api/v1/document/token" which sounds like what isn't being handled correctly. This is supposed to be mapped to an application created in IIS, and for some reason IIS is trying to map it to a location under the web client folder?

I'd start by making sure there is an application called "ldps" created under IIS. Even if there is, I'm not sure how that accounts for the url getting mapped under web client. You could check IIS logs to make sure that the incoming request matches what I pasted. Do you have some kind of global rewrite rule?

1 0
replied on April 30, 2021

Given this info I am going to try a fresh installation over the weekend, and will verify the LDPS app is there, I always wondered where that was appearing from.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...