07-29-2008 11:38 AM
07-31-2008 02:01 AM
Solved it !!!!!
Apparently a trial version of ACT for Web 2008 had previously been installed on the machine and whilst uninstalled successfully, it had left various registry settings referring to ACT dlls with wrong paths and / or version numbers (we now have ACT! Premium 2008). These did not cause any problems anywhere in the program except in the ACT! Outlook Add-in. A very manual registry clean solved it - not recommended.
I got there by running Microsoft's Fusion Logging and comparing the Outlook.exe logs to those on a successful machine.
Sage's UK ACT Technical Support had disowned the problem and told me to talk to Microsoft - very helpful!
07-30-2008 04:22 AM
Another UK user, (another Andy!) running 10.0.1 with Outlook 2003 (SP3) and XP (SP2). We've had similar problems with a number of our users - and have played with the loadbehavior registry setting with mixed results. We've reinstalled .Net 2.0, again with mixed results. I've done one full deep-de-install and re-install with zero success. Yet others don't seem to have the problem. Is it something new coming down the line from Microsoft that is messing up ACT??
Also (I use Word as my Outlook email editor) I've been tearing my hair out over the fact that every time I now open a new email message (including replies) I get two consecutive error messages before the new email appears, minimised in the Taskbar.
The first message is from Outlook, warning that a program is trying to access email addresses stored in Outlook.
The second is an ACT error message - Exception from HRESULT: 0x94904005.
I can't pin this down at all as it seems to sit midway between our IT support guys and our ACT support...
07-30-2008 08:40 AM
07-30-2008 08:46 AM
I thought v10 solved that issue? I used to use the Outlook editor until v10 came along but then switched 'because I could' and because of the additional benefits. I had been using Word as my email editor for several months without problems, until very recently.
07-30-2008 08:54 AM
07-30-2008 08:59 AM
Hmm, I appreciate your responses on this but, what's bugging me is that it USED to work. So what's changed in my setup? (Sorry, I don't necessarily expect you to know what's changed in my system, since we are subject to random Office updates through our IT support!) I just wondered if there was something I could tie it down to
07-30-2008 09:26 AM