@teerapongpa, there are no errors in the logs, which is a good sign.
Can you please check the status of the addin from:
Excel menu File --> Options --> Add-ins -->
Scroll to bottom to Manage drop-list “COM Add-ins” --> Go button
We want to make sure that the BigFix Connector is checked and no errors from Excel.
What I noticed
@teerapongpa, there are no security policy blocks that will impact this.
When you install the addin, it should have by default installed in c:\users[name]\appdata folder.
The fact that your say c:\Tivoli Endpoint Manager Excel Connector 3.3\ means that you changed it correct?
I wonder if because the user does not have permission in this folder structure.
Add-in Express Loader Log File: 01/29/2019 18:28:50:176
18:28:50:176 1356 6204 Starting the add-in registration process.
18:28:50:176 1356 6204 Loading mscoree.dll
18:28:50:176 1356 6204 Getting the latest CLR version.
18:28:50:176 1356 6204 The latest CLR version is ‘v4.0.30319’.
18:28:50:176 1356 6204 Loading CLR: v4.0.30319.
18:28:50:176 1356 6204 Calling CLRCreateInstance method.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Calling GetRuntime method.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Checking if the hosting API of .NET Framework v4.0 beta is installed.
18:28:50:176 1356 6204 The hosting API is up to date.
18:28:50:176 1356 6204 Calling GetInterface method for the CorRuntimeHost interface.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Starting CLR…
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the CLR version.
18:28:50:176 1356 6204 The CLR v4.0.30319 has been initialized successfully.
18:28:50:176 1356 6204 Creating a new domain setup.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the add-in directory.
18:28:50:176 1356 6204 Success. The directory is 'C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8’
18:28:50:176 1356 6204 The ‘shadow copy’ is disabled.
18:28:50:176 1356 6204 Creating a new application domain.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the base directory for the domain.
18:28:50:176 1356 6204 Success. The directory is ‘C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8’.
18:28:50:176 1356 6204 Searching for the Add-in Express core library.
18:28:50:176 1356 6204 Success. The ‘AddinExpress.MSO.2005.dll’ file has been found.
18:28:50:176 1356 6204 Creating an instance of the ‘AddinExpress.MSO.ADXLoaderSupport’ class.
18:28:50:176 1356 6204 Assembly identity is ‘AddinExpress.MSO.2005’.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Unwrapping the instance of the ‘AddinExpress.MSO.ADXLoaderSupport’ class.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Creating an instance of the XML parser class.
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Loading the manifest file (C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8\adxloader.dll.manifest).
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the root element of the manifest (C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8\adxloader.dll.manifest).
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Getting the ‘assemblyIdentity’ element of the manifest (C:\Users\cisdtpan\AppData\Roaming\IBM\IBM BigFix Excel Connector 3.3.8\adxloader.dll.manifest).
18:28:50:176 1356 6204 Success.
18:28:50:176 1356 6204 Searching for the ‘name’ attribute of the ‘assemblyIdentity’ element.
18:28:50:176 1356 6204 Success. The name is ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’.
18:28:50:176 1356 6204 Calling the managed procedure to register the ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’ assembly.
18:28:50 1908 6204 Connecting to the application domain of the Add-in Express loader.
18:28:50 1908 6204 Success.
18:28:50 1908 6204 Loading the ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’ assembly.
18:28:50 1908 6204 Error: Could not load file or assembly ‘IEM Excel Connector, PublicKeyToken=bef2983f1300af93’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
18:28:50 1908 6204 Inner Exception: The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
18:28:50 1908 6204 The managed registration process is complete with HRESULT = 2.
18:28:50:192 1356 6204 The system cannot find the file specified.
I found error on manual loading COM,Do you know what it is ? @leewei
Problem Solved : For every user , each of them have to run following cmd separately. (I install it on terminal server.)
“/adxregistrator.exe /install=“BigFixExcelConnector.dll” /privileges=user”
Then Bigfix Excel Addon Showup , 
Hi Leewei,
Amazing utility you created, it has been very helpful. Is there support for windows 10. The latest version uses .NET framework 2.0, wondering if it will be coded to use a more recent version.
Alex
Latest version uses 4.5.2 NET framework. Info is in the original post.
Change History
Changes in version 3.3.8.0
(2017/05/04) Switched to .NET Framework 4.5.2 from 2.0
(2017/05/04) Supported TLS 1.2
Hi everyone!
I have question about specification of BigFix Excel Connector.
I executed Query Wizard and create report of BES Computers. Then I showed Relevance Code.
I could show the code including bes property "<property name>".
Also I could show the code including bes property whose (name of it = "<property name>" and (item 0 of it = <property id> and item 1 of it = <property sub-id> and item 2 of it = 1) of id of it).
I can’t understand about these difference of relevance code involving bes property.
why it is occur these difference?
Please let me know.
thanks
Nobumitsu
Hi Lee Wei,
I’ve downloaded BigFix Excel Connector version 3.3.8, verified .Net Framework full is installed, when I run it I’m getting a message window “This setup requires the .NET Framework version 2.0. Please install the .Net Framework and run this setup again. The .Net Framework can be obtained from the web. Would you like to do this now?”
However .NET Framework version 2.0 has ended support long ago. As I understand it .Net Framework is the latest version and is compatible with .NET Framework 4.5.2, noted in the installation instructions. Am I missing something. Also, does the Excel Connector require any of the .Net Framework advanced services enabled?
Any help is appreciated. Thanks.
Chi
Did you try turning on the .NET Framework 3.5 feature? It includes the runtimes for .NET 2.0 and 3.0
I’ve tried but I think it’s blocked. Correct me if I’m wrong but I was under the impression that apps written to .Net Framework versions 3.5 and lower will require version 3.5 to be installed, and apps written to .Net Framework version 4 or higher will need version 4 installed. Also, Change History for version 3.3.8.0, “(2017/05/04) Switched to .NET Framework 4.5.2 from 2.0”, so why would it be asking for version 2.0? I’m a bit confused.
It’s that highlighted checkbox at the top of your “Turn Windows Features on and off” screenshot, not the download file referenced in the installer.
This is the correct screenshot referenced in the installer.
This is what I have, so I still can’t understand why I’m still getting the window asking to install .Net Framework version 2.0.
.Net version.pdf (146.3 KB)
I’m facing same issue like Chi
Still asking for .Net 2.0 but even when installed the connector does not install
I am using Excel 2016 and cannot get this add-in to work. I checked my COM add-ins and it shows as loaded, but I cannot figure out to use it. How do I get the bigfix query wizard to come up?
