Programming, Tips

TRIM Outlook Add-In Module Not Found

Another HP TRIM Outlook issue; this time when trying to check-in a mail item from Outlook, when the TRIM record type has an External Link associated with it – in this case a Generic AddIn (.NET). When the Outlook Add-In gets to the point that it is checking the file in to TRIM the error The specified module could not be found. (Exception from HRESULT: 0x8007007E) is thrown, but only if there is an AddIn associated with the record type of the record being created, otherwise it works fine.

As with most error messages this one is not very helpful, simply indicating that a module count not be found. Fortunately this was working on my local workstation, however the issue was present for test users on their thin client environment, so it was just a matter of finding out what was different between the two environments. After some investigating I remembered that I had manually added the TRIM client installation directory to the PATH system variable to enable running a web site which uses the HP TRIM SDK. Removing the installation dir from the PATH variable did indeed result in the same error message, and funny enough adding the dir back resolved the issue, on both my local instance and on the thin client instance. I don’t know why the TRIM client install doesn’t just add the TRIM directory to the PATH variable by default. Oversight by HP? I’m sure it used to be… there are also plenty of SDK related forum posts suggesting to add it when starting your application (that doesn’t really help in this instance).

To add the TRIM installation directory to your PATH system variable go to your system settings; (start » type “Edit the system environment variables”) or (start » right-click Computer » Properties » Advanced system settings) » Environment Variables » under System variables locate and select Path » click Edit » append your TRIM install folder (default TRIM installation directory should be either ;C:\Program Files\Hewlett Packard\HP TRIM or ;C:\Program Files (x86)\Hewlett Packard\HP TRIM depending on your installation preference.

Standard
Programming, Tips

TRIM Microsoft Word Add-In HP TRIM SDK Not Found

If you’re using the Microsoft Word integration feature with HP TRIM and receive the error message “Could not load file or assembly ‘HP.HPTRIM.SDK’ or one of its dependencies. The system cannot find the file specified.” chances are you probably have a generic .NET Add-In registered in your TRIM dataset for the record type you’re trying to save your word document as.

To solve the issue you can copy the HP.HPTRIM.SDK.dll from your Trim installation folder into your Microsoft Office executable folder (e.g. C:\Program Files (x86)\Microsoft Office\Office14 or C:\Program Files (x86)\Microsoft Office\Office14 *note your office version may vary e.g. Office11, Office15, etc).

There may be another way to resolve this issue, but so far it’s the easiest and only fix I have worked out.

Standard
Programming, Tips

TRIM Outlook Add-In COM Exception

Recently I was getting the error 0×80030002 STG_E_FILENOTFOUND while trying to run any TRIM 7.3 Outlook Add-In function. The Outlook Add-In had loaded fine and was bringing up all the available TRIM options, it was just when I tried to execute one of the options that it would throw the, oh so very “helpful”, error message as with most COM operations. It wasn’t until I found this thread over in the HP forums that I discovered that Cisco Unified Personal Communicator can interfere with the TRIM Add-In. According to another post any ODMA integration can cause issues with HP TRIM’s Outlook Add-In, in their case it was Novell GroupWise causing the issue.

Trim Outlook Com Exception

Unable to cast COM object of type ‘System._ComObject’ to interface type ‘Redemption.SafeMail’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{0A95BE2D-1543-46BE-AD6D-18653034BF87}’ failed due to the following error: could not be found. (Exception from HRESULT: 0×80030002 (STG_E_FILENOTFOUND)).

Fortunately for me, Cisco Unified Personal Communicator was no longer required to be installed (and has been replaced by Jabbr – although I did not test if Jabbr causes issues with TRIM’s Add-In), so to resolve the issue I just had to uninstall Cisco Unified Personal Communicator; for good measure I also did a repair of HP TRIM Microsoft runtimes for VS 2008 and a repair of HP TRIM.

Standard
Technology, Tips

Oracle 06413: Connection Not Open (x64)

Having changed to a 64-bit development machine at work recently I ran into an Oracle error while trying to generate files using CodeSmith. This error was ORA-06413: Connection Not Open. Assuming it was a connection string error, as I had not ran this particular generation in some time and it was likely that the server or username/password had changed, I proceeded to test the connection from SQL Developer. Success!

After ruling out that the connection was indeed valid I did a quick Google search for the error message. After a few clicks I discovered a very well known (has been around for a few years) Oracle issue; When executing an Oracle command from an application with parentheses or equals — ‘(‘ or ’)’ or ‘=’ — in the path then the specified error message is thrown.

In this particular case CodeSmith had been installed under C:\Program Files (x86)\CodeSmith\ which was causing Oracle to fail. The quickest workaround was to simply move CodeSmith from the Program Files (x86) path e.g. into C:\CodeSmith\. However; there is a patch (5383042) for Oracle 10g, which I believe is also applied to Oracle 11G.

Standard
News, Technology

Australian Internet Filter: What Can I Do?

What is it?

The Australian Federal Government is introducing a mandatory ISP-level filtering of all Refused Classification (RC) rated content. This means all websites (or part-thereof) which have been refused classification under Australia’s classification laws will be blacklisted.

See the Electronic Frontiers Open Internet website for more information.

What can I do?

The simplest thing you can do is sign the EFA’s online petition.

Additionally you can contact your local member of parliament or contact Senator Conroy, the Minister for Broadband, Communications and the Digital Economy.

Take Action!

Standard
News, Technology

iiNet Vs AFACT: The Verdict

As a lot of people are probably already aware iiNet was taken to court by the Australian Federation Against Copyright Theft (AFACT) for allegedly allowing its customers to illegally download copyrighted material (e.g. movies, music, etc).

This morning Justice Cowdroy has ruled in favour of iiNet stating that “I find that iiNet simply can’t be seen as approving infringement”. His verdict was that the “copyright (infringement) occured as result of use of BitTorrent, not the Internet” and that “iiNet has no control over (the) Bittorrent system and (is) not responsible for (the) Bittorrent system.”

Common sense and Australia’s Internet Freedom prevails, for now (see mandatory Australia Internet Censoring).

Standard
Technology, Tips

Win 7 Live Messenger Task Bar Fix

For those of you ‘lucky’ enough to have already updated to the new Windows 7 then you have probably already noticed the major changes to the task bar. Good or bad, you decide. Personally, I like some of the new functionality that it provides but I also enjoy a slim taskbar — similar to that of Vista. Fortunately Microsoft provided a “Use small icons” option in the taskbar properties (right-click the taskbar and select properties) which makes the task bar a similar size to that of Vista.

Changing the taskbar to use small icons, however, does not fix the fact that Windows Live Messenger likes to constantly take up a space in the taskbar even when the window is not open. Since there does not currently appear to be an option in Windows Live Messenger to display the program in the system tray, instead of on the taskbar, we need to use a simple work around.

First, close any current Windows Live Messenger instances. Then open your start menu and locate the Windows Live Messenger shortcut. Right-click the shortcut and select properties. Switch to the Compatibility tab and check “Run this program in compatibility mode for:” and select Window Vista (Service Pack 2)”. Now start Windows Live Messenger and problem solved. You should now see the Windows Live Messenger icon in the system tray. As you would on Vista, XP, etc.

Standard