A colleague attempts to edit an Excel spreadsheet hosted in SharePoint and gets the following error message. Why? and how to solve it?
Sorry, but to open this workbook, your computer must be running a
supported version of Microsoft Excel and a browser that supports
opening files directly from Office Web Apps.
My colleagues has the same version of Office and IE as me (Office 2010 and IE9), but when I attempt to open the same document, it works without with error message. So what is the real cause of this error message, and how to resolve it? The version of SharePoint is SharePoint 2013.
Related
I'm having some trouble. I cannot embed the ActiveX Microsoft Web Browser control in an Excel sheet as desired. Tried a few others controllers and works flawless but Web Browser isn't. Only getting the Cannot Insert Object error.
Version: Microsoft® Excel® for Microsoft 365 MSO (16.0.14026.20326) 64 bits
Does anyone know what might be going on here and/or what a solve the problem?
The web store 'Open In Excel' button does not work for Mac users. Excel indicates that it is downloading some file but then nothing happens. I'm sure expected behavior is that the workbook should open and install the add-in to Excel. Here is a video showing this, on Excel v16.40 (latest version as of this writing):
https://drive.google.com/file/d/1MqlZyqhYe9MfOzJN_sjpFwyPHOn4LuPD/view?usp=sharing
I became aware of this issue because some of our customers have contacted us, asking why the add-in wasn't working. Who knows how many potential customers we have lost because they simply thought the add-in wasn't supported on their system and moved on.
Is this a problem with our add-in code? Is anyone at Microsoft aware of this issue?
I have written an add-in for Microsoft Excel. The add-in works great on the web-based Excel, but I get the error below when I try to run it in the desktop version
This happens when the plugin tries to authenticate the user using a popup window. Anyone encountered this issue ?
Thanks
Matteo
Excel addin which uses Excel API 1.2. Add-in loads fine in Excel 2016 for Windows and Excel online. Save the file from Excel online and open in Excel 2013, addin fails to load in Excel 2013 with following errors:
When loading the Addin published in Store:
APP ERROR We can't load this app because we could not connect to catalog
When sideloading the addin from trusted catalog:
This app could not be started. Close this dialog to ignore the problem or click restart to try again
I know that Excel 2013 does not support Excel API 1.2. Could you please confirm the recommended way to make sure the add-in loads in Excel 2013?
• Should we use runtime checks using isSetSupported method?
• In such cases, how to debug which line of code is failing in Excel 2013 client?
• Is there any logging that can be enabled to troubleshoot such issues in Excel client?
I tried debugging a default add-in created by VS 2015 which uses Excel 1.2 API in Excel 2013. I added the following requirements set to the Manifest:
<Requirements>
<Sets DefaultMinVersion="1.2">
<Set Name="ExcelApi" />
</Sets>
</Requirements>
The addin also fails to load in Excel (15.0.4849.1003) when debugging using VS 2015. It works fine in Excel 2016 client.
I think there are two separate issues here (though there's a good chance that they're related, and the platform is simply giving the wrong error string. If so, let's confirm, and then I can file a bug to have us fix this).
Excel 2013 does not support the "ExcelApi" requirement set, which is a 2016 addition of the host-specific APIs (same goes for "WordApi"). If you specify ExcelApi in the requirements section of the manifest, as you have above, this will always fail to load in Excel 2013 -- by design. Essentially, you're requesting an API set and marking it as "required" for something that Excel 2013 does not support -- so it has no choice but to refuse to run it.
This is where the runtime check (isSetSupported) comes in. Please see my answer at Neat ways to get environment (i.e. Office version) for more details.
I am not sure what you mean by "how to debug which line of code is failing" or troubleshooting techinques. Essentially, any call to an Office 2016 API (anything in the ExcelApi set) from 2013 will result in a runtime failure...
Hope this helps!
I am supporting a legacy application that was written in Access 2003 using VBA. We are updating our systems to Office 2010, with the exception of Access, which will remain the 2003 version. (This is due to several factors pertaining to other groups in my organization.)
We use Access as a front end for running reports out of MS SQL and Sybase databases. Some of these reports open in Excel. During testing, running reports that write to an Excel workbook causes the Access application to crash and exit without a warning message - the application simply disappears from the screen.
I'm not sure what the cause of this is or where I should start looking for answers. Has anybody dealt with a similar situation?
I saved and recompiled the application on the development machine that had Office 2010 installed, and thereafter the application worked correctly with Office 2010 (of course, it no longer works on machines only having Office 2003.) This was, of course, after checking the references were correct. Without any intervention, the reference to Office was for 2010.
After testing with early versus late binding, it would appear the best answer to this issue is to use late binding.
Make sure you are writing to Excel in Excel compatibility mode (.xls).