Highlighted
Established Member.. TRIMCat
Established Member..
2380 views

TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed"

 

Clicking on the "Manage" function on the Outlook-TRIM Add-in causes an error: "The operation failed". (Dialog box header: HP TRIM in Outlook)

 

Environment Details:

 

TRIM 7.34

Windows 7 Enterprise, Service Pack 1

Outlook 2010, SP1

 

Has anyone else have this happen or know what the cause is?

 

Thanks.

 

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

0 Likes
6 Replies
Micro Focus Expert
Micro Focus Expert

Re: TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed&

Is it only manage causing the issue?

 

Do the other integration features work?

**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
Established Member.. TRIMCat
Established Member..

Re: TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed&

It does appear to be basically working, only the manage that is the issue in this case (in this circumstance)

 

That said, the Outlook add-in is shaky at best.

 

It sometimes crashes, hangs, disconnects the dataset for no obvious reason, and unlinks folders of its own accord. 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed&

So all the pre-requisites are installed? vstor30, PIA2010

 

Is this a problem for all users or do you only really see it with a handful?

 

Is there anything worth mentioning about your environment, for example are all the users running through a Citirix environment? Or do they have their app data stored on a network drive?

 

 

**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
Established Member.. TRIMCat
Established Member..

Re: TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed&

I am not sure how broadly this issue is spread. It is occurring on my laptop (though Outlook-TRIM issues are generally occurring more broadly), which is using these pre-requisites:

 

  • HP TRIM Microsoft  Runtimes for VS2008 x86
  • HP TRIM Microsoft VB Runtime
  • .NET Framework 4.5.1

 

Also:

 

  • Microsoft Visual C++ 2005 Redistributable
  • Microsoft Visual C++ 2008 Redistributable x86

 

The PIA is a bit less clear. We initially had issues with some deployments with the Outlook add-in working at all to some new machines (of a different image & OS). I understand that the fix was likely to involve Office Professional Plus installation (though cannot be certain). I figured PIA was a part of this, however the reasoning or method of deployment was not fully clarified in this regard.

 

Searching for *Microsoft.Office.interop* across my hard drive, I only find:

 

  • Microsoft.Office.Interop.Visio.WorkflowAuthoring

I'm assuming that the Interops maintain their naming conventions as below. If so, it would seem that the relevant PIAs aren't installed. There are other Interops installed, just not under the *Microsoft.Office.interop* naming convention. They appear to be unrelated.

 

Assemblies included in O2010PIA.MSI  read me (also listed on the Microsoft PIA Site) are shown in the readme included to be:

 

1.  ADODB

2.    extensibility

3.    ipdmctrl

4.    Microsoft.mshtml

5.    Microsoft.Office.InfoPath.Permission

6.    Microsoft.Office.Interop.Access

7.    Microsoft.Office.interop.access.dao

8.    Microsoft.Office.Interop.Excel

9.    Microsoft.Office.Interop.Graph

10.  Microsoft.Office.Interop.InfoPath

11.  Microsoft.Office.Interop.InfoPath.SemiTrust

12.  Microsoft.Office.Interop.InfoPath.Xml

13.  Microsoft.Office.Interop.MSProject

14.  Microsoft.Office.Interop.OneNote (Assembly version 12.0.0.0)

15. Microsoft.Office.Interop.OneNote (Assembly version 14.0.0.0)

16. Microsoft.Office.Interop.Outlook

17. Microsoft.Office.Interop.OutlookViewCtl

18. Microsoft.Office.Interop.PowerPoint

19. Microsoft.Office.Interop.Publisher

20. Microsoft.Office.Interop.SharePointDesigner

21. Microsoft.Office.Interop.SharePointDesignerPage

22. Microsoft.Office.Interop.SmartTag

23. Microsoft.Office.Interop.Visio

24. Microsoft.Office.Interop.Visio.SaveAsWeb

25. Microsoft.Office.Interop.VisOcx

26. Microsoft.Office.Interop.Word

27. Microsoft.stdformat

28. Microsoft.Vbe.Interop

29. Microsoft.Vbe.Interop.Forms

30. MSCOMCTL

31. msdatasrc

32. OFFICE

33. stdole

34. Policy.11.0.Microsoft.Office.Interop.Access

35. Policy.11.0.Microsoft.Office.Interop.Excel

36. Policy.11.0.Microsoft.Office.Interop.Graph

37. Policy.11.0.Microsoft.Office.Interop.InfoPath

38. Policy.11.0.Microsoft.Office.Interop.InfoPath.Xml

39. Policy.11.0.Microsoft.Office.Interop.MSProject

40. Policy.11.0.Microsoft.Office.Interop.Outlook

41. Policy.11.0.Microsoft.Office.Interop.OutlookViewCtl

42. Policy.11.0.Microsoft.Office.Interop.PowerPoint

43. Policy.11.0.Microsoft.Office.Interop.Publisher

44. Policy.11.0.Microsoft.Office.Interop.SmartTag

45. Policy.11.0.Microsoft.Office.Interop.Visio

46. Policy.11.0.Microsoft.Office.Interop.Visio.SaveAsWeb

47. Policy.11.0.Microsoft.Office.Interop.VisOcx

48. Policy.11.0.Microsoft.Office.Interop.Word

49. Policy.11.0.Microsoft.Vbe.Interop

50. Policy.11.0.Office

51.  Policy.12.0.Microsoft.Office.Infopath

52.  Policy.12.0.Microsoft.Office.Infopath.FormControl

53.  Policy.12.0.Microsoft.Office.Infopath.Permission

54.  Policy.12.0.Microsoft.Office.Interop.Access

55.  Policy.12.0.Microsoft.Office.Interop.Access.Dao

56.  Policy.12.0.Microsoft.Office.Interop.Excel

57.  Policy.12.0.Microsoft.Office.Interop.Graph

58.  Policy.12.0.Microsoft.Office.Interop.InfoPath

59.  Policy.12.0.Microsoft.Office.Interop.InfoPath.Xml

60.  Policy.12.0.Microsoft.Office.Interop.MSProject

61.  Policy.12.0.Microsoft.Office.Interop.Outlook

62.  Policy.12.0.Microsoft.Office.Interop.OutlookViewCtl

63.  Policy.12.0.Microsoft.Office.Interop.PowerPoint

64.  Policy.12.0.Microsoft.Office.Interop.Publisher

65.  Policy.12.0.Microsoft.Office.Interop.SmartTag

66.  Policy.12.0.Microsoft.Office.Interop.Visio

67.  Policy.12.0.Microsoft.Office.Interop.Visio.SaveAsWeb

68.  Policy.12.0.Microsoft.Office.Interop.VisOcx

69.  Policy.12.0.Microsoft.Office.Interop.Word

70.  Policy.12.0.Microsoft.Vbe.Interop

71.  Policy.12.0.Office

 

 

TRIM and Outlook are both installed to the hard drive.

 

This would be considered one of the more advanced uses of this add-in. I have seen this work on other machines, and cannot say how widespread this issue is.

0 Likes
toneeh
New Member.

Re: TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed&

I have seen this before a few times, especially people who have many TRIM Outlook linked folders. This can happen if the folder in Outlook is no longer present (i.e. deleted from outlook) or if the folder has been moved to a shared mailbox.

To fix this issue, you may have to go to the users registry and investigate further.

www.kapish.com.au
0 Likes
Honored Contributor.. Tamara Hoagland Honored Contributor..
Honored Contributor..

Re: TRIM 7.34: Outlook 2010 TRIM Add-in "Manage" Causes Error: "The operation failed&

I have also seen the issue with TRIM Outlook linked folders where the folder in Outlook is no longer present (i.e. deleted or renamed in Outlook).

 

You can see the Outlook links from within the Document Queues list in TRIM. Then you can compare and see if any Document Queues should be deleted due to lack of Outlook folder link.

 

Regards,

Tamara

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.