'secman64.OutlookSecurityManager64' COM object is not registered

Add-in Express™ Support Service
That's what is more important than anything else

'secman64.OutlookSecurityManager64' COM object is not registered
Registration of Outlook Security Manager (64 or 32 bits) does not recognized by SecurityManager.2005.dll 
Jean-François Davignon


Software Engineer


Posts: 4
Joined: 2010-09-26
Hi we have been happily using Outlook Security Manager (OSM) for a couple of years now but since upgrade to Security Manager 2010 we have encountered the following on both 32 and 64 bit machines and OS with both 32 and 64 bit Outlook on 64 bit machines running 64 bit Windows 7.

32 bit machines were running either XP, Vista, or Windows 7.

Excerpt from our logs:

Connector.exe Information: 0 : 2010-09-26 10:40:07.547 T(10): Scope Start >>> OutlookApi.connectToOutlook()
Connector.exe Information: 0 : 2010-09-26 10:40:07.550 T(01): 
A first chance exception of type 'System.ApplicationException' occurred in SecurityManager.2005.dll
Connector.exe Warning: 0 : 2010-09-26 10:40:07.580 T(10): Failed to connect OSM to Outlook:
System.ApplicationException: The 'secman64.OutlookSecurityManager64' COM object is not registered.
   at AddinExpress.Outlook.SecurityManager.ConnectTo(Object outlookApp)
   at OutlookAPI.OutlookApi.connectToOutlook() in C:svnSourceICOutlookAPIOutlookApi.cs:line 974


I have verifed the registration of, in this case, secman64.dll:


========================================
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOTCLSID{2F35794D-4574-4BCF-B0A5-3B16AF985788}]
@="OutlookSecurityManager64 Class"

[HKEY_CLASSES_ROOTCLSID{2F35794D-4574-4BCF-B0A5-3B16AF985788}InprocServer32]
@="C:\Program Files (x86)\Common Files\Outlook Security Manager\secman64.dll"

[HKEY_CLASSES_ROOTCLSID{2F35794D-4574-4BCF-B0A5-3B16AF985788}Programmable]

[HKEY_CLASSES_ROOTCLSID{2F35794D-4574-4BCF-B0A5-3B16AF985788}TypeLib]
@="{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}"

[HKEY_CLASSES_ROOTCLSID{2F35794D-4574-4BCF-B0A5-3B16AF985788}Version]
@="1.0"

[HKEY_CLASSES_ROOTTypelib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}]

[HKEY_CLASSES_ROOTTypelib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0]
@="secman64Lib"

[HKEY_CLASSES_ROOTTypelib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0]

[HKEY_CLASSES_ROOTTypelib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0win64]
@="C:\Program Files (x86)\Common Files\Outlook Security Manager\secman64.dll"

[HKEY_CLASSES_ROOTTypelib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0FLAGS]
@="0"

[HKEY_CLASSES_ROOTTypelib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0HELPDIR]
@="C:\Program Files (x86)\Common Files\Outlook Security Manager"

[HKEY_CLASSES_ROOTWow6432NodeTypeLib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}]

[HKEY_CLASSES_ROOTWow6432NodeTypeLib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0]
@="secman64Lib"

[HKEY_CLASSES_ROOTWow6432NodeTypeLib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0]

[HKEY_CLASSES_ROOTWow6432NodeTypeLib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0win64]
@="C:\Program Files (x86)\Common Files\Outlook Security Manager\secman64.dll"

[HKEY_CLASSES_ROOTWow6432NodeTypeLib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0FLAGS]
@="0"

[HKEY_CLASSES_ROOTWow6432NodeTypeLib{2C8CCB3A-CE4F-40A2-AA1C-E891338BF189}.0HELPDIR]
@="C:\Program Files (x86)\Common Files\Outlook Security Manager"
==================================================


The code did not change since we started using OSM.

On some machines manually re-registering the DLL seemed to work but right now on my machine (64 bit Win7 with 64 bit Outlook) I get the error listed above even though the registration is successful.

Any insight on what could be causing the .NET SecurityManager.2005.dll to not pickup the registration? Change in CLSID?

I verified that we do reference the SecurityManager.2005.dll that came with the 2010 update.

Regards,

JF
Jean-François Davignon
Software Architect
InGenius Software Inc.
www.InGenius.com
Posted 26 Sep, 2010 11:04:17 Top
Andrei Smolin


Add-in Express team


Posts: 14137
Joined: 2006-05-11
Hi Jean-François,

Please note that the bitness of the Security Manager depends on the bitness of Office, not the bitness of Windows. Please check if this is the cause of the issue. Also pay attention to a series of articles on our blog devoted to installing applications and add-ins using Security Manager on 32-bit and 64-bit systems for Office 32-bit and 64-bit, see

Outlook Security Manager 2010 deployment: Summary

Please let me know if this help.

Regards from Belarus (GMT+2),

Andrei Smolin
Add-in Express Team Leader
Posted 27 Sep, 2010 05:19:53 Top