Print Page | Close Window

No toolbars? Try installing .NET Prog support

Printed From:
Category: RECORDLINKwriter
Forum Name: Tech stop
Forum Discription: Questions, known issues and fixes for Network Managers.
Printed Date: 29 Sep 2020 at 6:18pm

Topic: No toolbars? Try installing .NET Prog support
Posted By:
Subject: No toolbars? Try installing .NET Prog support
Date Posted: 16 Jul 2008 at 9:58am
Program Support for .Net may be missing in an incomplete or typical installation of Office 2003 on end user PCs. You can fix by reloading Office 2003 from your original media and selecting a 'complete' install or download the .Net Program Support elements.

You can check if the .net programmability support elements are installed by looking in C:\Windows\Assembly. There should be files like:

•     Microsoft.Office.Interop.Excel
•     Microsoft.Office.Interop.Outlook
•     Microsoft.Office.Interop.Word


If you only want to install the .Net Program Support Elements you will need to install four elements, one each for Word, Excel and Outlook and one for Office Tools.

There are detailed instructions on - msdn , look about half way down the page.

If this doesnt do the trick, check you have - the missing patch for SP3, and - .Net framework 2 installed.

Hint: If you need to apply the patch, uninstall RLw and reinstall after the patch.

Tim Hampton
Cohesion Software

Posted By:
Date Posted: 08 Oct 2010 at 9:41am
After the .net interop files the other possibility is that the toolbar has been disabled in Excel/Word due to it failing to load at some point – again this is separate for each part of Office. There is a registry value for each of them located at (something like):

HKEY_CURRENT_USER\Software\Microsoft\Office\[Application Name]\Addins\

Where [Application Name] is either Outlook, Excel or Word and it is called LoadBehavior – the value should be 3 if the add in is to be loaded at startup. If it is any other value, then change it to 3 – close all Office apps and try loading again.

If the problem is identified as the first problem (missing Interoperability components) then you should also check the second registry values since they would fail to load and normally get marked as not loaded at startup.

Again, this only applies to Office 2003.

Tim Hampton
Cohesion Software

Print Page | Close Window