Forum Discussion

Abhimanyu Singh's avatar
Abhimanyu Singh
Steel Contributor
Oct 11, 2017

Open in Excel - Error: Cannot open Excel workbook

We are facing a typical problem with one of the forms since last one week. We have opened a ticket as well, but no resolution even after 1 week. The only response I am getting from support is, "we ar...
Microsoft Forms
  • Qingwen Zeng's avatar
    Qingwen Zeng
    Oct 12, 2017

    Hi Abhimanyu,

    From our service logs, I found that your form was truly created from Excel. I can see the excel file info
    {
     WorkbookId: "drives/b!QB_j3D3OCkaltV6FsXy_73P0zVPS60tCkV9ozfDI4M-PV311TEftQJ78NF5wGyIo/items/01N6DO3N...",
     Origin: "Excel",
     Title: "Book1"
    }
    So I guess you might forget the creation entry of the form. And then the excel file "Book1" might be considered as a useless file and be deleted.
    You can reexport your data to a new excel file by the steps:
    1. click the button "Open in Excel", it will open a page tab.
    2. copy the url of the new page, it looks like:  https://forms.office.com/Pages/RedirectToExcelPage.aspx?id=v4j5cvGGr0GRqy180ZNV4u&forceReExport=false
    3. change the "false" to "true" in the end of the url, like:
    https://forms.office.com/Pages/RedirectToExcelPage.aspx?id=v4j5cvGGr0GRqy180ZN4u&forceReExport=true
    4. open the new url in browser then you will see all the data in a new excel file.

    Hope it will help.

     

    Thanks,

    Qingwen

DavidEaston's avatar
DavidEaston
Copper Contributor

Abhimanyu Singh 

I had the same problem. I tried Chrome and Edge and had the same results.

After downloading and (re)installing Internet Explorer and opening it there, the file actually opened in SharePoint.

sadhya111's avatar
sadhya111
Copper Contributor
Aug 10, 2022
I had a similar issue, and entered a test entry into my form, and found that even though when I clicked Open in Excel and got the "Excel workbook is missing" fail, that a new workbook (numbered 1) stored same place in my OneDrive with all of the responses thus far (including my test one) was there. It looks like Microsoft fixed the issue as long as you can get to the owner's file storage.

Resources