Community | TeamSolutions
TeamSolutions | Enhanced visibility & communication

Outlook cant find com addin

This post has 10 Replies | 0 Followers

Top 50 Contributor
Posts 2
jhoran Posted: Fri, Aug 11 2006 3:42 PM

I have installed the latest release of TeamLook and am running Outlook 2003 sp2.

Teamlook is no where to be found. I have looked in the advanced options to see if the com addin is there (and enabled) but it was not there. Can I search for it and manually add it? If so what is the name of the file.

 

Thanks

Top 10 Contributor
Posts 104
Joe Buys replied on Fri, Aug 11 2006 9:28 PM

Sorry you are having trouble with TeamLook!  It sounds like it is not loading correctly. Does TeamLook appear in add/remove programs?  The addin will not show in the advanced options dialog becase we install it for all users.  You can verify it is installed by checking for the registry key:
        HKLM\Software\Microsoft\Office\Outlook\Addins\Teamlook

If that key is there, we did get installed.  It may be getting disabled for a number of reasons.  If the subkey 'LoadBehavior' is NOT 0x3, then it is failing the load.  Try resetting this to 0x3, then relaunch Outlook.

If you are still having problems, I will need more detailed debugging information from Outlook.  If you start a cmd prompt, and type:
        set VSTO_SUPPRESSDISPLAYALERTS=0
Then start Outlook from that command line, you should get a warning that the addin could not be loaded.  What is the text it gives you?

Thanks, and I hope I can help!

~Joe

Top 50 Contributor
Posts 2
jhoran replied on Fri, Aug 11 2006 10:48 PM

thanks Joe that did give me some ideas to check on. I found a registry setting for TeamLook. I never did find anything for a subkey LoadBehavior. I was able to install and use teamlook when I logged onto machine as Administrator but when logged on to the domain as a Domain Aministrator the install appears to go well but no application (I do get a registry setting for TeamLook). I have also logged on as Domain Aministrator and did a install as run as Administrator and that yielded nothing.

Unfortunately the only install that did take does not appear when I do my network log on.

Top 10 Contributor
Posts 104
Joe Buys replied on Sat, Aug 12 2006 12:13 AM

The other place the installer may be getting hung up is when configuring the .NET Security.  Open the '.NET Framework 2.0 Configuration' utility from the Administrative tools. 

Expand the Node: 'My Computer'->'Runtime Security Policy'->'Machine'->'All_Code'

There should be a node here called PersonifyDesign.Solutions with some sub-nodes under it.  Verify this is there.  It sounds like there is a problem with the security settings.

~Joe

Top 100 Contributor
Posts 1
nick replied on Fri, Jul 27 2007 11:59 AM

Hallo everyone!

I've faced with the same problem.

After installing the lates version of TeamLook for Microsoft Office Outlook 2003 i cannot see niether TeamLook menu nor TeamLook toolbox.

I've rechecked all things described here but everything is OK.

What is wrong? Can you help me, please?

 

Top 10 Contributor
Posts 104
Joe Buys replied on Mon, Jul 30 2007 5:03 PM

Hello Nick,

Have you tried all the different checks above to verify that the addin is 'installed' but just not loading?

Thanks,
~Joe

Top 50 Contributor
Posts 2
IceTFS replied on Tue, Mar 11 2008 12:26 AM
I am having a similar issue after installing using TeamLook_v1.6.xx.161.exe.

HKLM\Software\Microsoft\Office\Outlook\Addins\TeamLook doesn't exist after I run the installer.


When I try to load the addin in Outlook (it appears in the list there) I get the following error:

Could not load file or assembly 'Teamlook, Version=1.6.11.161, Culture=neutral, PublicKeyToken=aa0dc0026a8c90af' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)


************** Exception Text **************
System.IO.FileLoadException: Could not load file or assembly 'Teamlook, Version=1.6.11.161, Culture=neutral, PublicKeyToken=aa0dc0026a8c90af' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Teamlook, Version=1.6.11.161, Culture=neutral, PublicKeyToken=aa0dc0026a8c90af'
   at Microsoft.VisualStudio.Tools.Applications.Runtime.AppDomainManagerInternal.HandleOnlineOffline(Exception e, String basePath, String filePath)
   at Microsoft.VisualStudio.Tools.Applications.Runtime.AppDomainManagerInternal.LoadStartupAssembly(EntryPoint entryPoint, Dependency dependency, Dictionary`2 assembliesHash)
   at Microsoft.VisualStudio.Tools.Applications.Runtime.AppDomainManagerInternal.ConfigureAppDomain()
   at Microsoft.VisualStudio.Tools.Applications.Runtime.AppDomainManagerInternal.LoadAssembliesAndConfigureAppDomain(IHostServiceProvider serviceProvider)
   at Microsoft.VisualStudio.Tools.Applications.Runtime.AppDomainManagerInternal.LoadEntryPointsHelper(IHostServiceProvider serviceProvider)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.Runtime
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.816
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.dll
----------------------------------------
Microsoft.Office.Tools.Common
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.816
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Office.Tools.Common/8.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Common.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------



Top 10 Contributor
Posts 104
Joe Buys replied on Tue, Mar 11 2008 12:40 AM

Hello,

Are you running Outlook 2003?  TFC 2005 or TFC 2008 or both?  Is there anything unique about how you installed either TFC or TeamLook (non standard install paths or anything)?

I haven't seen this issue before, but it appears that TeamLook cannot find one of our required dependancies (such as the right version of the Work Item Tracking assemblies...)

Thanks,
~Joe

Top 50 Contributor
Posts 2
IceTFS replied on Tue, Mar 11 2008 7:07 PM
I am using Outlook 2003 and TFC 2005 SP1. I don't believe there is anything unique about my install... :-(
 
Is there anything I could look at that might help me diagnose the problem a little better?
Top 10 Contributor
Posts 104
Joe Buys replied on Tue, Mar 11 2008 7:18 PM

The registry key is found under HKEY_CURRENT_USER (not HKLM as you were previously looking).  Verify that this registry key has been set.

Also, it may be that one of our assisting DLL's didn't get properly registered during the install.  Open a command window and go to the install directory (typically: c:\program files\personify design\teamlook).  From here, type in the command line: regsvr32 TeamlookRDO.dll

It may be that this DLL didn't get unregistered in the first place if you had a previous install.

If this doesn't solve the problem, my only other guess is that your TFS binaries are not matching the binaries we are trying to load.  During install, did you choose to install for TFC 2005?  If you tried to install for TFC2008, this would also explain the failure to load required DLL's.

Thanks,
~Joe

(If you care to take this offline, you can email me at my user name to the left (jbuys) (at) personifydesign (dot) com.)

Top 10 Contributor
Posts 104
Joe Buys replied on Mon, Mar 17 2008 7:41 PM

An update for this thread...

Unfortunately, there was an error with our installer for Outlook 2003 with TFC 2005.  We have posted a new build on our website that addresses this issue (v1.6.xx.161b). None of the underlying code has changed in this build, just the packaging of the installer. 

You can download it at:
www.personifydesign.com/products/teamlook/download.aspx

Thanks,
~Joe

Page 1 of 1 (11 items) | RSS