로그인
 
홈라이브러리학습다운로드지원커뮤니티포럼
Resources for IT Professionals >
> 
> 
IRM Event Log Errors 5037 and 5038

Proposed IRM Event Log Errors 5037 and 5038

  • 2011년 8월 2일 화요일 오후 6:22
     
     
    로그인하여 투표
    0

    About 30 days ago, the below two IRM event log entries started occurring every hour on one WFE but not the other.  The FARM includes two WFEs running v12.0.0.6550 and a SQL Server cluster.

     

    The WFEs are Server 2003 x64 R2 SP2

     

    In Central Admin Information Rights Management is set to “Do not use IRM on this server.”

     

    There is a question from 2009 on the forums but I really do not want to run a “repair.”

     

    Event ID:  5038

    -          Information Rights Management (IRM): Protector {4F9976DC-47C3-4518-B2A2-A258B379F970} could not be created as a generic COM object (IUnknown).

    Protector: {4F9976DC-47C3-4518-B2A2-A258B379F970}

    -          This indicates a major problem with the protector.  Any COM object can be created as an IUnknown.

     

    Event ID:  5037

    -          Information Rights Management (IRM): Protector {4F9976DE-47C3-4518-B2A2-A258B379F970} could not be created as an IRM protector COM object.

    Protector: {4F9976DE-47C3-4518-B2A2-A258B379F970}

    -          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.

    Any help to solve this issue would be grateful.

    • 이동됨 Mike Walsh FIN 2011년 8월 3일 수요일 오전 6:40 admin q (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
    •  
     

모든 응답

  • 2011년 8월 3일 수요일 오전 4:45
     
     
    로그인하여 투표
    0

    Hi,

    At the time when you get these entries in the event logs what are the entries in ULS logs?

    If you have not checked them so far have  a look at them s\and also paste them here so that we can also take a look of the issue.

     

    Thanks,

    Rahul Rashu

     
  • 2011년 8월 4일 목요일 오전 2:25
     
     
    로그인하여 투표
    0

    Hi,

     

    I agree with Rahul Rashu.

     

    Did you enable IRM configuration in your farm? If so, please look into the following article:

     

    Event ID 5038 (Windows SharePoint Services health model)

    http://technet.microsoft.com/en-us/library/cc561003(printer).aspx

     

    Thanks,

    Rock Wang

    Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Regards, Rock Wang Microsoft Online Community Support
     
  • 2011년 8월 8일 월요일 오전 11:58
     
     
    로그인하여 투표
    0

    Hello,

     

    Thanks for the reply and I included the requested information below.

    No, IRM is not enabled.  In Central Admin Information Rights Management is set to “Do not use IRM on this server.” 

    The SharePoint log entries are below.

    08/08/2011 06:19:43.35 w3wp.exe (0x2A60) 0x2A5C Windows SharePoint Services IRM 95lu Information Information Rights Management (IRM): The initialization of protector {4F9976DD-47C3-4518-B2A2-A258B379F970} was completed. Protector: {4F9976DD-47C3-4518-B2A2-A258B379F970} 

    08/08/2011 06:19:43.38 w3wp.exe (0x2A60) 0x2A5C Windows SharePoint Services IRM 95ly Warning Information Rights Management (IRM): Protector {4F9976DE-47C3-4518-B2A2-A258B379F970} could not be created as an IRM protector COM object. Protector: {4F9976DE-47C3-4518-B2A2-A258B379F970}  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. 

    08/08/2011 06:19:43.39 w3wp.exe (0x2A60) 0x2A5C Windows SharePoint Services IRM 95lz Critical Information Rights Management (IRM): Protector {4F9976DE-47C3-4518-B2A2-A258B379F970} could not be created as a generic COM object (IUnknown). Protector: {4F9976DE-47C3-4518-B2A2-A258B379F970}  This indicates a major problem with the protector.  Any COM object can be created as an IUnknown. 

    08/08/2011 06:19:43.41 w3wp.exe (0x2A60) 0x2A5C Windows SharePoint Services IRM 95ly Warning Information Rights Management (IRM): Protector {4F9976DC-47C3-4518-B2A2-A258B379F970} could not be created as an IRM protector COM object. Protector: {4F9976DC-47C3-4518-B2A2-A258B379F970}  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. 

    08/08/2011 06:19:43.41 w3wp.exe (0x2A60) 0x2A5C Windows SharePoint Services IRM 95lz Critical Information Rights Management (IRM): Protector {4F9976DC-47C3-4518-B2A2-A258B379F970} could not be created as a generic COM object (IUnknown). Protector: {4F9976DC-47C3-4518-B2A2-A258B379F970}  This indicates a major problem with the protector.  Any COM object can be created as an IUnknown. 

    Thanks,

    Scott

     

     
  • 2012년 6월 26일 화요일 오후 1:23
     
     제안된 답변
    로그인하여 투표
    0

    Hi AFRetired07,

    I know it is very late to reply to your post, but may this will help other people, i just faced same issue and just do repair for the SharePoint and issue gone:)

    Thanks & Best Regards Tarek Mostafa Kamel MCSE, MCTs - SharePoint, MCTs - Exchange, MCT tmk_emy_mcse@hotmail.com

    • 답변으로 제안됨 Tarek Mostafa 2012년 6월 26일 화요일 오후 1:23
    •