Hi Carl,
I have installed .NET 3.5 SP1 on a Windows Vista Home machine/Windows XP SP3/Windows XP SP2 and Office 2007 and it works fine, no intermitant behaviour I can close Excel and run it back and the toolbar is there and fully functional.
So the problem does not seam to be .NET 3.5 SP1, actually when you install the latest version of .NET you always get all previous versions + service packs which include .NET 2.0 the one required by the Excel Connector. The original suggestion was to uninstall .NET 3.5 and just install .NET 2.0 just to isolate any problem realted to .NET setup on your system.
Now, it looks like there is something specific to your environment that is causing some problem at startup of the plug in. So the following are steps I will ask you to follow, just to isolate the problem and give us an idea of what exactly is going on:
1) Can you verify the content of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\AddIns\PrestoConnector4Excel.Connect
it should look like this:
Default: (value not set)
Description: Enables Excel to connect to Presto Mashup Server
FriendlyName: PrestoConnetor4Excel++
LoadBehavior: 3
2) The following are steps to follow that act on your specific environment:
2.1 Close all instances of the Office applications. Make sure there is no running instance of an Office application by checking in the task manager.
2.2. If the excel connector's LoadBehavior is set to 2 make sure it is set to 3. This is necessary because, whenever an Add-In load fails, Office disconnects the Add-In (Loadbehavior changes to 2).
3) Make sure your Excel Connector is not listed in the Disabled Items. In Office 2007, you can access “Disabled Items” list from: Office menu > Excel Options > Under “Manage” select “Disabled Items” and then click Go.
Note that Excel Connector requires mscoree.dll so look if it is listed in the “Disabled Items” list. If you find that Excel Connector and/or mscoree.dll is/are listed in the list, enable it/them and retry.
4) The Antivirus on the system may be blocking the Add-In load. Run latest updates for the Antivirus and retry. If this doesn’t help, disable the Antivirus program completely and retry. Sometimes the Antivirus software also installs additional Office add-in, you may need to disable these additionally by running through the Antivirus control panel (Settings). Here is one such KB article that talks about Norton Antivirus:
How to use Office programs with the Norton AntiVirus Office plug-in
http://support.microsoft.com/kb/329820
5) There may be a conflict with other add-ins that are being loaded in the Office application. Disable all other Add-Ins except Excel Connector and retry.
To disable COM Add-Ins, look at the following registry path:
HKEY_CURRENT_USER\Software\Microsoft\Office\ExcelAddins
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\AddIns\
and change the LoadBehavior for each Add-In where the LoadBehavior is “3” (3 = Load on startup + Connected) to “2” (2=Load on startup)
6) Make sure you have Office Primary Interop Assemblies (PIAs) installed on the target machine. You can check this by going to the Global Assembly Cache, GAC, (%systemroot%\assembly) and looking for assemblies beginning with “Microsoft.Office”.
Also, make sure that you are referencing the Office PIAs (not Interop Assemblies) in the project references. You can confirm this by looking at the properties for the reference added. They should point to GAC.
Please let my know
Ivan.
I have been trying to install and use the excel connector but the registration of he connector is intermitant. By that I mean that sometimes I can register it and use it but when I close excel the registration is lost and I have to do it again but it will never stick.
The most obvious manifestation of the problem is the "Not loaded. A runtime error occurred during the loading of the COM add-in" as shown in the scren shot.
I did a connect-to session with JackBe personnel and they saw me reproduce the problem but said they couldn't reproduce on their machines but suspected it was caused by my use of .net 3.5 as they were only using and supporting .net 2.0
Is anyone using this connector with .net 3.5 SP1 installed and Office 2007? If you are and can register and use this connector then the version of .net 3.5 SP1 is not the issue.
Thanks,
Carl