Forum Discussion

CyrilBuchs's avatar
CyrilBuchs
Copper Contributor
Jun 26, 2024

Imported DOTX template creates error when opening document in app

Hi all,

Just created a new library for testing a few things with documents. I imported a fully working sample template (it works on a local disk and network share) to my SharePoint library:

 

When clicking it, it successfully creates a Word document that opens in the Word desktop app, but it's then showing this:

Translation: "Word was unable to read this document. It may be corrupted. Try one the following operations:

- Open and repair the file

- Open the file with the Text Recovery Converter"

 

If I then close it and right click -> Open in browser, it get this popup (first time opening the DOCX):

 

I can then edit my template. Furthermore, if I click on "Edit" ("Modification" here) -> Open in app, it get the same error message as above.

 

This problem is occuring with every template I upload (they are all created with Word M365 version if you're wondering). I want my users to be able to edit a template-generated document from the app, like any other doc.

 

What is going on here?

 

Thanks in advance for your help!

  • Jan_Sharepoint's avatar
    Jan_Sharepoint
    Copper Contributor

    In a way I'm glad I'm not the only one. I cannot imagine that there aren't any other organisations using this option, because it's a real time-saver!
    I've encountered this issue since (since at least 27 June 2024) and haven't found a solution. I opened a ticket with my Microsoft license provider but they claim they don't support Sharepoint. (It's frustrating, really, because I don't understand how a license retailer can sell Sharepoint licenses without having the knowledge to support the platform).

    I tested the templates by saving them to my local drive and run them from File Explorer. I had no problems opening them. It only occurs when I try to open them from the Sharepoint environment 🙁

    • CyrilBuchs's avatar
      CyrilBuchs
      Copper Contributor

      I opened a ticket to MS directly, but they were really evasive. I recently followed them up, but since then, no answer was provided...

  • MVNITI's avatar
    MVNITI
    Copper Contributor
    Did you figure out what was causing this? I'm facing the same issue.
    • CyrilBuchs's avatar
      CyrilBuchs
      Copper Contributor

      MVNITI sadly no, I opened a case to MS. They will come back to me mid-November, I'll update the thread with their response at that time.

      • Jan_Sharepoint's avatar
        Jan_Sharepoint
        Copper Contributor

        Hello, CyrilBuchs Dit Microsoft finally come back to you about this? I have no direct access to them, hence my question.

Resources