Home Forums ActiveX components Xceed Encryption for ActiveX Problem isoloating COM reference from C# in VS2005

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • User (Old forums)
    Member
    Post count: 23064
    #42991 |

    Each time I compile my C# library that references the exceed encryption library I see these warnings.

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3179: Problem isolating COM reference ‘XceedEncryptionLib’: Registry key ‘HKEY_CLASSES_ROOT\CLSID\{a0a61b00-96a6-457f-aa5e-afa5167852e5}\Insertable’ was not imported.

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3179: Problem isolating COM reference ‘XceedEncryptionLib’: Registry key ‘HKEY_CLASSES_ROOT\CLSID\{a0a61b00-96a6-457f-aa5e-afa5167852e5}\MiscStatus’ was not imported.

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3179: Problem isolating COM reference ‘XceedEncryptionLib’: Registry key ‘HKEY_CLASSES_ROOT\CLSID\{7ec04d5b-19a8-45ee-bcb0-6fe0067f9468}\Insertable’ was not imported.

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3179: Problem isolating COM reference ‘XceedEncryptionLib’: Registry key ‘HKEY_CLASSES_ROOT\CLSID\{7ec04d5b-19a8-45ee-bcb0-6fe0067f9468}\MiscStatus’ was not imported.

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3179: Problem isolating COM reference ‘XceedEncryptionLib’: Registry key ‘HKEY_CLASSES_ROOT\CLSID\{d865f1e7-bac6-4eca-b37b-0a5ddff2d031}\Insertable’ was not imported.

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3179: Problem isolating COM reference ‘XceedEncryptionLib’: Registry key ‘HKEY_CLASSES_ROOT\CLSID\{d865f1e7-bac6-4eca-b37b-0a5ddff2d031}\MiscStatus’ was not imported.

    When I try to install the library I get an error that says “Unable to load one or more of the requested types.” and the install fails. This has been working for the last 3 years. I am pretty sure the problem is that the COM registration of the encryption library is messed up. I have tried unregistering and re-registering using regsvr32 to no avail. I have also uninstalled and re-installed the xceed components. Does anyone have any idea how I can fix the regsitration without rebuilding my computer from scratch?

     Much Thanks,

    Brad Marshall

    Imported from legacy forums. Posted by Bradley (had 4955 views)

    User (Old forums)
    Member
    Post count: 23064

    It seems related to windows registry keys not properly set, according to the following thread on MSDN :

    http://social.msdn.microsoft.com/forums/en-US/winformssetup/thread/67c642dd-56bb-43ae-ae46-1b991efb5c1a/

    You might want to google the warning message for more information if this does not solve your issue.

    In any case, this is not caused by our library as such.

    Imported from legacy forums. Posted by André (had 2068 views)

    User (Old forums)
    Member
    Post count: 23064

    Hi Andre,

    Thanks for the response. I was not trying to imply that this was a bug in the encryption library. I have been using it for several years and am quite happy with it. I was hoping that someone could tell me how I can find what registtry entries are written when I regsvr32 the DLL so that I can try to clean up the registry manually. I have read the MSDN forum article you mentioned and it seems to imply the that the problem is messed  up COM registration.

    Thanks,

    Brad

    Imported from legacy forums. Posted by Bradley (had 5874 views)

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.