Question

web client Office document checkout

Web Client Version 10

Updated January 15, 2019

asked on January 15, 2019

I have a site using Web Client 10.3 extensively, but when they try to edit (check out) MS Office documents, the Office product is opened and then and error window is presented stating that office could not find the file.

The name shown in the error box does not match up to the document opened and looks a bit wonky. Any ideas as to the cause and/or a solution?

0 0

Replies

replied on January 15, 2019

Does it happen to all Office documents? Do the documents have characters in their name or path other than alphanumeric, white space, underscore, and standard punctuation? For example, something like a character with an accent or an emoji-type symbol.

I haven't run into this issue offhand, but we've seen similar problems when Web Client tries to parse a character it doesn't expect.

The best course of action is to open a support case and attach WA event logs (from c:\programData\Laserfiche\WebAccess\EventLogs) with log level set to debug. Also, copy and paste everything under 'Details' in the dialog in your screenshot to the case.

0 0

replied on January 15, 2019 • Show version history

As far as I am aware, it is all office documents. They showed me the issue and every office document they tried to open (random selection) gave the same type error.

The names of the documents are just using standard letters input from a standard keyboard with standard English USA region cultural settings.

0 0

You are not allowed to follow up in this post.

Question

Question

web client Office document checkout

Replies

Sign in to reply to this post.