Outlook 2003 Addin doesn't work on Windows 2003 Terminal Server

Outlook 2003 Addin doesn't work on Windows 2003 Terminal Server

• Oliver66

  Yes I did! But the addin didn't loaded. It is not not also visible in COM AddIns dialog of Outlook as it is visible when you install it on Win 2K or Win XP....

  
  

• motters

  Can you please create a shared addin only for the current user and install it and check if that is available in the COM Add-ins dialog

  Thanks
  Pallavi

  
  

• Gabbar Singh

  The addin will be installed for the currently logged in user. Did you install the addin logged in as the user who will be using it

  Thanks,
  Pallavi

  
  

• kmassey

  This procedural work for me.

  Part 1 of 2, Overview.

  http://msdn.microsoft.com/library/default.asp url=/library/en-us/odc_vsto2005_ta/html/officevstowindowsinstallerwalkthrough.asp

  Part 2 of 2, Procedural.

  http://msdn.microsoft.com/library/default.asp url=/library/en-us/odc_vsto2005_ta/html/officevstowindowsinstallerwalkthrough.asp

  Ron Blood |<:^)

  
  
  

• RoviWil

  Hi Apolizoi,

  we encounter similar problems with our outlook addin on w2003 TS.

  Did you come to any solution a year ago

  Thanks,

  Klaus

  
  

• G. Mustafa

  Zorb,

  I recommend that you run the PSS VSTO 2005 Troubleshooter (see Announcement on homepage for this forum) on the terminal server. You may detect installation pre-requisite issues. Please respond to this forum if this does not lead you to a solution.

  John.

  
  
  

• -_Cypher_-

  1)The first thing you need to check is open MS Outlook on the addin installed machine.

  Go to -> help -> click about microsoft outlook -> click disabled items.

  See whether your addin is disabled. If your addin is disabled then make it enable. if not go to step 2

  2) Tools -> macro ->security -> for the timebeing make the macro settings as "Medium" and in trusted publishers tab check in "trust all installed addins and templates".

  close your outlook and open it once again.

  If addin is still not visible then goto step 3.

  3)

  Goto registry editor --> Hkey_current_user ->Software ->Microsoft ->Office ->Outlook -> AddIns -> select your addin -> check the loadbehavior value.

  If you did not find your addin in the above registry key then check it in HKey_local_machine.

  Tell me the loadbehavior value.

  Cheers

  Praveen

  
  

• werwin

  Can anyone help me with this problem
  
  Thanks in advance
  
  

• Mark Vernon

  The loadbehavior value should not be 2.The value 3 is OK.

  The load behavior values are like this.

  0 = Disconnect - Is not loaded.
  1 = Connected - Is loaded.
  2 = Bootload - Load on application startup.
  8 = DemandLoad - Load only when requested by user.
  16 = ConnectFirstTime - Load only once (on next startup).

  value 3 means the addin is connected + bootload.

  value 2 means the addin is only bootload but not connected.

  If the value is 2 then change the value from 2 to 3 and also it seems to be you shoul handle all the errors appropriately otherwise the addin is not going to be connected and started.

  In addition to the above if it is a shared addin then apply the update KB908002.

  Cheers

  Praveen

  
  

  
  

• haeh

  Possible solution:

  If you don't know, when installing a application to a terminal server, you must use the add remove programs interface, to allow terminal server users access to the application. I don't know if this applies to add-ins aswell.

  
  

• PennyB

  Hello Praveen

  According Step 3 in my Windows 2003 Terminal Server,

  My loadbehavior value is 3 (Hex)

  In my development PC and in Windows XP and Win 2000 clients I 've setup the AddIn ( And Addin is working) the value is 2 (Hex)

  Many Thanks.

  
  

• Guaw

  Hi,

  unfortunatelly i can't make Outlook Addin to work in W2003 TS...

  
  

• Jeltz

  Hello and many thanks your replies.

  I setup through Add Remove Programs but there is no AddIn visible in COM addins dialog of Outlook.

  I also setup the Add In only for the current user, but also no AddIn is visble in COM addins dialog.

  I ran the PSS VSTO 2005 Troubleshooter and I have this report

  http://img214.imageshack.us/img214/4053/10bt.gif

  http://img138.imageshack.us/img138/2012/22yh1.gif

  I believe I have the apropriete configuration.

  Can you help me

  Thanks In advance

  
  

• Sentinel3304

  Well, these articles are fine but they didn't solve the problem.

  I have followed these instructions in my solution

  My problem is that i cannot deploy the solution in a Windows 2003 Server running in Terminal Server mode....

  I have succesfully deploy it in Windows 2000 and Windows XP.

  
  
• Outlook 2003 Addin doesn't work on Windows 2003 Terminal Server