I work on Mercury Quality Center 8.2 Build 3406 Entreprise Edition.
In order to write tests within Excel for Test Director, I installed the Excel Add-In.
When I try to export the Excel file to Quality Center I get the following message
Quality Center Microsoft Excel Add-in Error
A general error has occured. Restart Microsoft Excel. Class does not support Automation or expected interface'.
I use Excel 2003 (11.5612.5606) part of MS Office Professional Edition 2003.
Could someone tell me how to make work this add-in correctly ?
Thank you.
Try below steps:
Launch MS Excel 2010
Go to Option--> Trus Center -->Trus Center Settings --> Protected View --> Uncheck the Enable Data Execution Prevention Mode
Restart the Excel.
Still facing the problem:
Navigate to Addins page in QC
Click on "HP ALM Client Registration" and run "Register HP ALM Client"
Close and re-start the Excel program.
Related
I'm trying to mess around with some dashboard/BI tools since Power BI is no longer free and stumbled upon Power Query/Power Pivot as a potential solution.
I installed Power Query (x32) and am since unable to load excel 2010 when the add-in is enabled. When I disable the add-in Excel opens with no issues. When I re-enable the add-in Excel hangs for a brief moment and then crashes.
I'm running on a 64-bit Windows 7 machine with a 32 bit Excel 2010 installation.
Any thoughts as to what could be going on here?
Edit: Many of my coworkers are having a similar issue so it may be something corporate-wide.
I previously had that scenario at one client, and it turned out to be a clash with a specific Add-In - ironically Microsoft's Data Mining Add-In (for SQL 2008 R2).
I suggest first turning on the Developer Main Tab in your Excel ribbon (for convenience) and then using it's Excel Add-ins and COM Add-ins buttons to disable all other Add-ins besides Power Query.
BTW performance of Power Query on Excel 2010 is truly woeful compared to Excel 2016 (where PQ is also built in, not an add-in).
BTW2 Power BI Desktop and a personal powerbi.com account are both still free.
I am using the SQL managment studio to run the import wizard to get data from excel file (XlSX). I get the following error:
External table is not in the expected format. (Microsoft Office Access Database Engine)
The excel file is not password protected and it was created in office 2003 (95% sure)
I have read articles suggesting missing drivers. I have installed all the following:
Microsoft Office version Download
2016 Microsoft Access 2016 Runtime
2013 Microsoft Access 2013 Runtime
2010 Microsoft Access 2010 Runtime
2007 2007 Office System Driver: Data Connectivity Components
Nothing of these worked for me. However; if I open the excel file, click save, close it and then import it using the wizard it works.
The problem is that I would like to automate this process. So opening 200 files, save them, and then close them is not an option.
My specs:
windows 10,
Microsoft SQL Server Management Studio 12.0.4459.0
Microsoft Analysis Services Client Tools 12.0.4459.0
Microsoft Data Access Components (MDAC) 10.0.14393.0
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.11.14393.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.14393
The only thing that I found starnge here is the following:
Microsoft MSXML 3.0 4.0 5.0 6.0.
Is this the correct value. If not, how do I update it?
This is my second day looking for a solution to this problem with no luck. If anyone could help.
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 made a excel spreadsheet using office 2013 and it works fine. But when i try to open it in office 2010 it will crash when retrieving data.
My configuration: office 2013 - x64
Client: office 2010 - x32
data source: odbc
I have no clue what is wrong,
what have i tried:
if i do click on edit query and run the query it runs but as soon as i hit the button to take the data back to office it will just crash.
Have you tried installing powerpivot for office 2010?
This may give you a cleaner and more powerful solution, adaptable in both versions of Excel
I created a VSTO Excel 2003 addin and a setup project. It works perfect in Excel 2003 and Excel 2007.
When I install the addin in Office 2000. I getting the following error...
"The Common Language runtime could not
be loaded... contact
your administrator"
No exception Sad
Since for Office 2000 we need to use the PIA of office 2000. I created the Office 2000 PIA manually and included it in the project and build the project.
The same setup file(office 2000 pia) is working fine in office 2003/2007.
I made the copy local property to true...
Could you please help me what I am missing on this... why it is not working in office 2000...
The only suggestion I can make is to go to the msdn forums...
social.msdn.microsoft.com/Forums/