Highlighted
Established Member.. TRIMCat
Established Member..
5080 views

ERROR: Outlook 2010: "Unable to cast COM object of type System.__ComObject"

Jump to solution

Unable to cast COM object of type 'System.__ComObject' to interface type 'AddInExpress.MSO.IRibbonUI'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{000C03A7-0000-0000-C000-000000000046}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

 

Has anyone seen this issue before please?

 

I think it's likely that this is a dependency pre-requisite that wasn't installed properly?

 

Version Specifics:

  • TRIM 7.34 (Build 5739) (32 bit client)
  • Windows 8 Pro (32 bit)
  • Office 2010 SP1

 

 

- Posted by another member of the team, not Mick Regan.

0 Likes
1 Solution

Accepted Solutions
Established Member.. TRIMCat
Established Member..

Resolution: Installation of .Net Framework Manually

Jump to solution

 

NB: 11/6/2014: This fix has been updated. Refer to the bottom for the update.

 

Thanks for the responses. That pointed me in the right direction.

 

Version information added to the initial post.

 

It seems to have been a missing .Net 4.5 Framework** installation. It looked like it had been installed as part of Windows 8 features, however it either wasn't properly installed or had somehow been corrupted.

 

An install of the redistributable package such that it appeared in the Add/Remove Programs listing resolved the issue.

 

* Installation Notes:

 

  • Installed: NDP451-KB2858728-x86-x64-AllOS-ENU.exe

  • This is not the .Net Framework recommended in the Specifications and Limitations document for TRIM 7.3.4, however appeared to work in this case, which may have non-standard components. The re-installation of .Net Framework 3.5 (Service Pack 1) was not tested due to time limitations and may also resolve this.

 

- Posted by another member of the team, not Mick Regan.

 

Update:

 

Due to a limited testing environment, there was a similtaneous download (Office) occuring at the same time as attempting to troubleshoot this issue. Net was being updated. For this reason, it appeared that .Net was the fix (and indeed .Net is a pre-requisite for the fix), however the fix appears to be dependent on the correct installation of Office Primary Interop Assemblies (http://msdn.microsoft.com/en-us/library/kh3965hw.aspx) which appeared not to have been installed.

0 Likes
6 Replies
Micro Focus Expert
Micro Focus Expert

Re: ERROR: Occurring via Outlook 2010: "Unable to cast COM object of type System.__ComObject&qu

Jump to solution

Need a fair bit more to understand the issue.

 

When does the issue occur?

 

What version of TRIM does this happen in?

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Micro Focus**
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: ERROR: Occurring via Outlook 2010: "Unable to cast COM object of type System.__ComObject&am

Jump to solution

Yeah, in lieu of any other information my guess would be the Office 2010 Primary Interop Assemblies (PIA). Install them if you haven't. Repair them if you have. With any luck this may fix it.


Neil

Note: Any posts I make on this forum are my own personal opinion, and unless stated otherwise do not constitute a formal commitment on behalf of Micro Focus.

(Please state the version of CM you're using in all posts.)

MySupport: https://softwaresupport.softwaregrp.com/
Established Member.. TRIMCat
Established Member..

Resolution: Installation of .Net Framework Manually

Jump to solution

 

NB: 11/6/2014: This fix has been updated. Refer to the bottom for the update.

 

Thanks for the responses. That pointed me in the right direction.

 

Version information added to the initial post.

 

It seems to have been a missing .Net 4.5 Framework** installation. It looked like it had been installed as part of Windows 8 features, however it either wasn't properly installed or had somehow been corrupted.

 

An install of the redistributable package such that it appeared in the Add/Remove Programs listing resolved the issue.

 

* Installation Notes:

 

  • Installed: NDP451-KB2858728-x86-x64-AllOS-ENU.exe

  • This is not the .Net Framework recommended in the Specifications and Limitations document for TRIM 7.3.4, however appeared to work in this case, which may have non-standard components. The re-installation of .Net Framework 3.5 (Service Pack 1) was not tested due to time limitations and may also resolve this.

 

- Posted by another member of the team, not Mick Regan.

 

Update:

 

Due to a limited testing environment, there was a similtaneous download (Office) occuring at the same time as attempting to troubleshoot this issue. Net was being updated. For this reason, it appeared that .Net was the fix (and indeed .Net is a pre-requisite for the fix), however the fix appears to be dependent on the correct installation of Office Primary Interop Assemblies (http://msdn.microsoft.com/en-us/library/kh3965hw.aspx) which appeared not to have been installed.

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Resolution: Installation of .Net Framework Manually

Jump to solution

Nice one, glad to hear you got it sorted.

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Micro Focus**
Established Member.. TRIMCat
Established Member..

Re: Resolution: Installation of .Net Framework Manually

Jump to solution
0 Likes
TheRealTRIMCat Absent Member.
Absent Member.

Re: Resolution: Installation of .Net Framework Manually

Jump to solution

Users are still getting this error intermittently on tablets when cataloguing emails in TRIM.

 

Running on Windows 8 Enterprise (32 bit) with TRIM 7.34

Here is what users tried: 

 

  • Turning Outlook and TRIM off and relaunching it again
  • Ensuring that only one Network connection exists (e.g. possibility to connect via 3G connections that do not allow TRIM access).
  • Making sure the TRIM dataset is connected in the Outlook ribbon Add-Ins section.

 

Notably the error did not occur, in this example, when the user opened the email and catalogued in TRIM from there; only when the email was being catalogued directly from the email inbox listing. 

 

This may be a workaround,  however would this would only serve when not using the function that allows cataloging in TRIM through linked Outlook folders.

Needed to create a new account due to changed departmental login rights. Was formally known as TRIMCat
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.