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?
Related
I've seen posts from several years ago stating that automation wasn't supported in older click to run installations of Office, eg 2010. Can anyone tell me if this is still the case with Office 365?
For background, the reason I'm asking is I support some .NET desktop applications which use late-binding to automate Excel and Word. They've worked fine for all users until a recent client who has Office 365 Business click to run. On this PC (and this one only, so far) the app fails ("Cannot create ActiveX component") at the line:
Dim oExcel as Object = CreateObject("Excel.Application")
User claims Excel is definitely installed and working (and Registry key at /HKEY_CLASSES_ROOT/Excel.Application/Curver confirms 2016 is present.) Also CreateObject("Scripting.FileSystemObject") executes correctly, so it doesn't seem to be a scripting problem.
Thanks for any assistance!
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.
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 have a couple of Excel Add ins. If I move to Office 365, will these add ins be available ? Is there any development support(VSTO) for Office 365 ?
I to have been curious about the answer to this, so went looking online. From the following site, I'd say the answer is no. It looks like developing for Office 365 is more along the lines of SharePoint development.
http://blogs.msdn.com/b/donovanf/archive/2011/06/29/office-365-developer-guidance-and-resources.aspx
I have seen advertisements online for products such as this... http://www.ocxt.com/products that look like they could provide a possible solution for taking a vsto application to the web.
I think things have moved on substantially since this question was asked. Microsoft seem to be fully committed to the Add-in approach with Office 2013 and the equivalent VSTO tooling available in VS2012.
The Office Dev Center home page has Office 2013 and VSTO Add-ins written all over it.
This MSDN Blog Post also clearly shows Add-ins are still part of the strategy.
Until the full capabilities of Desktop MS Office are available in a browser, I can't see this situation changing.
If you mean Office 365 installed on client PC then there is no issue with VSTO Add-ins. Our Chem4Word Add-in is using Office 2010 VSTO and happily works with 2010, 2013, 2016, 2019, O365.
If you mean Office 365 on-line then you have to redesign them using the Office 365 Javascript API
How to fix this error in SharePoint:
"The list cannot be displayed in
Datasheet view. A datasheet component
compatible with Windows SharePoint
Services is not installed, your
browser does not support ActiveX
controls, or support for ActiveX
controls
It started to days ago, for apparently no reason. ActiveX is enabled on this site and I had everything working fine so far. Not sure what went wrong.
Thanks,
... from IE check out your Internet Options, and look under 'Programs'->'Manage Add-Ons'
When I had this problem it was because an add-on was missing or disabled... * thinks * "Microsoft Office List 12.0" or something.
I was getting the below in SharePoint 2010.
The Standard View of your list is being displayed because your browser
does not support running ActiveX controls.
Turns out the site (master page) was being rendered in IE9 mode and the datasheet supports only up to IE8.
The datasheet mode can be used temporarily by switching the Document mode and the User agent string both to IE 8, or permanently by using the meta tag X-UA-Compatible IE=8.
This is known issue and you have to install the hotfix provided by Microsoft.
The issue is addressed in the below specified link along with the URL for the hotfix.
http://www.himmeltech.com/blog/fix-for-datasheet-view-issue-error-in-sharepoint-2010/
Let me know whether the suggested solution fixes your issue
Please install below data connectivity component to resolve this issue.
http://www.microsoft.com/en-us/download/details.aspx?id=23734
This link helped me and it worked fine. Our environment was Windows 7 64bit and MS office 64bit as well, after installing this connectivity tools, user had a option edit the data sheet view in sharepoint.
I ran into the same issue after updating to Office 365 but remaining with IE 11 and Sharepoint 2010.
Issue:
using a 64-bit version of Office with a 32-bit version of IE
Reference: Technet
Resolution: Installed 2007 Office System Driver: Data
Connectivity Components
Seems like a client/browser problem.. do you have Microsoft Office installed? Did you change security settings in Internet Explorer?
My environment is SP2010 enterprise and after trying several solutions, I realized that the user that could not see the views in Datasheet style was because did not have installed "Microsoft Access" that is required when you are using views in datasheet style. So the solution for me was to upgrade that specific user from Office Standard to Office Professional
For me, I performed the following and it worked for me:
Open Control Panel and open Programs and Features
Find your instance of Microsoft Office and select it
Click change at the top
On the dialog that comes up, click Add or Remove Features and then continue
Make sure Microsoft Access Web Datasheet Component is installed under Office Tools/Microsoft SharePoint Foundation Support
Even if it is showing as installed, click Continue.
Let everything install, close any office programs out, then try again
These steps worked for me.