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

Question

Question

Errors opening Office 2013 files in Laserfiche 9.2.1 on Windows 10 OS

asked on September 30, 2015

Hello,

We have recently started testing Laserfiche Rio 9.2.1.562 on some machines with the Windows 10 operating system, and we are getting several errors when attempting to open Office 2013 files.

For example:

filename.xlsx appears in LF with an Excel icon next to it, and the properties indicate it does have the ".xlsx" exentsion. However, when we attempt to open it, we get the following error:

The file format and extension of 'Filename.htm" don't match. the file could be corrupted or unsafe. Unless you trust its source, don't open it. Do you want to open it anyway?

 

Another example:

When attempting to open a Word 2013 file, we get the following error:

This document could not be registered. It will not be possible to create links from other documents to this document.

 

A final example:

When attempting to open an Outlook 2013 .msg file, we get the following error:

The specified electronic file could not be opened using WebDAV. The document name must include the appropriate extension. Would you like to get a local copy and open it instead?

 

We have checked the default programs to ensure those file types are set to open using Office 2013 products.

Has anyone had this issue? If so, how did you resolve it?

Thank you.

 

0 0

Answer

SELECTED ANSWER
replied on September 30, 2015

Hi Jeanette,

In the Laserfiche Client, go to Tools > Options > View > Open With and under the section "Open electronic documents by default using:" try setting it to use "The associated application" and with "Open files directly (using WebDAV)" unchecked. See if that makes a difference.

Regards

3 0

Replies

replied on September 30, 2015

Hi Alexander,

Thanks for the suggestion... it worked! We unchecked "Open files directly (using WebDAV)" and the files opened properly. 

Thanks again,

Jeanette 

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

Sign in to reply to this post.