Quantcast
Channel: SharePoint 2010 - Development and Programming forum
Viewing all articles
Browse latest Browse all 11571

Custom IRM Protector Protector {GUID} could not be created as a generic COM object (IUnknown).

$
0
0

Hey guys,

We have a Sharepoint Enterprise 2010 on a Windows 2008 R2 Server.

We tried to create a custom IRM protector based on this model here:

http://pdfirmprotector.codeplex.com/releases/view/58093

The model we used to deploy was taken from the Microsoft site:

http://msdn.microsoft.com/en-us/library/ms436515(v=office.14).aspx


We also adapted the default cmd files from c:\Protectors to install our own protector in the same manner it installs the microsoft.office.irm.msoprotector.dll & microsoft.office.irm.ofcprotector.dll (we tried with both WOW and default: MsoprotectorWoW.cmd& Msoprotector.cmd)

We have checked the registry and it was similar to what the default protectors have.

After we enabled the irmprotectors with :

stsadm -o setproperty -propertyname irmaddinsenabled -propertyvalue TRUE

the Information Rights Management (IRM)  library menu appears and it shows that we can enable the protector on the library.

However, the protector doesn't get loaded correctly as we receive the following errors:

 Warning  Information Rights Management (IRM): Protector {2C16543F-AF1B-4247-B55E-C59F3F4B79D0} could not be created as an IRM protector COM object. Protector: {2C16543F-AF1B-4247-B55E-C59F3F4B79D0}  Protectors must implement an IRM protector interface in order to be created as an IRM protector COM object.  Next, the protector will be created as a generic IUnknown COM object. fdacd481-4895-4b85-bb2f-8969070e76e0

And the following

Information Rights Management ( 5038 Critical Information Rights Management (IRM): Protector {2C16543F-AF1B-4247-B55E-C59F3F4B79D0} could not be created as a generic COM object (IUnknown). Protector: {2C16543F-AF1B-4247-B55E-C59F3F4B79D0}  This indicates a major problem with the protector.  Any COM object can be created as an IUnknown. fdacd481-4895-4b85-bb2f-8969070e76e0

Do you have any idea what could be wrong with the custom IRM protector?

Have we missed something?

Thank you in advance,

Dan



Viewing all articles
Browse latest Browse all 11571

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>