N
Nick Hebb
When my Excel COM Add-in, written in VB6, is installed by an Admin, it
no longer loads when someone with User level permissions logs into the
PC. This used to work fine until recently. When SP3 was released, I
had concerns about this, but I tested it and everything worked fine. I
was notified by a user today that this no longer works, and I
confirmed it on a test system.
Does anyone know of any recent Excel / Office changes that might be
causing this?
The details are below.
======= Details =======
Here are the things I've checked:
1. The registry settings:
My setup file sets a HKLM registry entry as follows, so it will be
available to all users (except with my real add-in name and Connect
class):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins
\MyAddin.Connect
With these subkeys:
- FriendlyName
- Description
- LoadBehavior (3)
- CommandLineSafe (0)
2. KB 938815 (http://support.microsoft.com/kb/938815)
My add-in doesn't use RTD, so it didn't seem applicable.
3. KB 938814 (http://support.microsoft.com/kb/938814/)
This one didn't seem applicable, but I tried the steps in it anyway -
to no avail.
4. I went through the COM add-in troubleshooting guide here:
http://blogs.msdn.com/msdnts/archiv...ubleshoot-the-com-add-ins-loading-issues.aspx
Most of the settings checked out, except I don't have \CurVer and
\VersionIndependentProgID subkeys.
5. Lastly, I ran the officeins tool (http://www.nirsoft.net/utils/
officeins.html - very handy). As expected, as an Admin the add-in and
its CLSID were properly set in the registry - in both HKLM and HKCU
even though the installer only sets the HKLM settings. But in User
level, the add-in registry settings only appear in HKLM but no CLSID
is associated with it.
=====================
Thanks,
Nicholas Hebb
no longer loads when someone with User level permissions logs into the
PC. This used to work fine until recently. When SP3 was released, I
had concerns about this, but I tested it and everything worked fine. I
was notified by a user today that this no longer works, and I
confirmed it on a test system.
Does anyone know of any recent Excel / Office changes that might be
causing this?
The details are below.
======= Details =======
Here are the things I've checked:
1. The registry settings:
My setup file sets a HKLM registry entry as follows, so it will be
available to all users (except with my real add-in name and Connect
class):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins
\MyAddin.Connect
With these subkeys:
- FriendlyName
- Description
- LoadBehavior (3)
- CommandLineSafe (0)
2. KB 938815 (http://support.microsoft.com/kb/938815)
My add-in doesn't use RTD, so it didn't seem applicable.
3. KB 938814 (http://support.microsoft.com/kb/938814/)
This one didn't seem applicable, but I tried the steps in it anyway -
to no avail.
4. I went through the COM add-in troubleshooting guide here:
http://blogs.msdn.com/msdnts/archiv...ubleshoot-the-com-add-ins-loading-issues.aspx
Most of the settings checked out, except I don't have \CurVer and
\VersionIndependentProgID subkeys.
5. Lastly, I ran the officeins tool (http://www.nirsoft.net/utils/
officeins.html - very handy). As expected, as an Admin the add-in and
its CLSID were properly set in the registry - in both HKLM and HKCU
even though the installer only sets the HKLM settings. But in User
level, the add-in registry settings only appear in HKLM but no CLSID
is associated with it.
=====================
Thanks,
Nicholas Hebb