| Event Id | 5038 |
| Source | Windows SharePoint Services 3 |
| Description | Information Rights Management (IRM): Protector %1 could not be created as a generic COM object (IUnknown). Protector: %2 This indicates a major problem with the protector. Any COM object can be created as an IUnknown. |
| Event Information | According to Microsoft : Cause : This event is caused by the following conditions 1)A Windows Rights Management Services (RMS) server refused access to a computer running Windows SharePoint Services 3.0. 2)The RMS server is not available. 3)The locally-stored licenses have become corrupt. 4)One or more IRM manifest is not valid. You must be a member of the SharePoint Administrators group to perform the following task. Workground: To determine which server is specified in Central Administration 1.In Central Administration, on the left navigation pane, clickOperations. 2.On the Operations page, in the Security Configuration section, clickInformation Rights Management. 3.On the Information Rights Management page, if the Use this RMS server option is selected, the server name appears in the box. 2.To determine if the RMS server is available 1.At the command-prompt on a computer that should have access to the RMS server and that is not the same computer that received this event, type the following and press ENTER: ping The ping should reply in a timely manner. If it does not, the RMS server is not available on the network. 2.At the command-prompt on the Windows SharePoint Services 3.0 computer that received this event, type the following and press ENTER: ping The ping should reply in a timely manner. If it does not, the network between the Windows SharePoint Services 3.0 computer and the RMS sever might be down. Resolution : To resolve this issue,These are the following Resolution 1.Configure RMS server to accept requests An RMS server refused access to a computer running Windows SharePoint Services 3.0. This alert indicates that a front-end Web server contacted the RMS server but the RMS server denied access to the Web server. Generally, this error occurs when an administrator is first enabling IRM for the Web farm in Central Administration. If this is the case, IRM cannot be enabled in Central Administration, and list administrators will not be able to enable IRM on a document library or list until the error is resolved. To resolve this issue, the RMS server must be configured to accept requests from the server running Windows SharePoint Services 3.0 that caused this error. The RMS server settings that are required differ depending on whether: a)You want the RMS server to accept requests from all computers on the domain, and Windows SharePoint Services 3.0 is installed as a single server on the same domain as your RMS server. b)You do not want the RMS server to accept requests from all servers on the domain, and Windows SharePoint Services 3.0 is installed as a single server. c)Windows SharePoint Services 3.0 is installed in a Web farm configuration. To discover the correct service account name 1.In Central Administration, on the left navigation pane, clickOperations. 2.On the Operations page, in theSecurity Configuration section, clickInformation Rights Management. 3.On the Information Rights Management page, click either Use the default RMS server specified in Active directory or Use this RMS server, and then type the URL for the RMS server you want to use. 4.ClickOK. Use the procedure that is appropriate for your situation. You must be an administrator on the RMS server to make these changes. To configure the RMS server to accept requests from all servers in the domain 1.On the RMS server, navigate to the folder containing the ServerCertification.asmx file. This file is typically located in the %systemdrive%\Inetpub\wwwroot\_wmcs\Certification folder. 2.Add the computer account of the Windows SharePoint Services 3.0 Server to the access control list (ACL) of the ServerCertification.asmx file and assign it the Read & Execute permission. To configure the RMS server to accept requests from Windows SharePoint Services installed as a single server 1.On the RMS server, navigate to the folder containing the ServerCertification.asmx file. This file is typically located in the %systemdrive%\Inetpub\wwwroot\_wmcs\Certification folder. 2.Add the FQDN or NetBIOS name of the server that cannot access the RMS server to the ACL of the ServerCertification.asmx file, and assign it the Read & Execute permission. 3.To configure the RMS server to accept requests from Windows SharePoint Services 3.0 installed in a farm 1.On the RMS server, navigate to the folder containing the ServerCertification.asmx file. This file is typically located in the %systemdrive%\Inetpub\wwwroot\_wmcs\Certification folder. 2.Add each service account assigned to an application pool for the Web application on the server that cannot access the RMS server to the ACL of the ServerCertification.asmx file, and assign it the Read & Execute permission. 2.Check RMS server status and settings This problem might be caused by a problem with the availability or health of the RMS server. You can check the health of the RMS server by using the procedures below: You must be a member of the SharePoint Administrators group to perform the following task. a)To check IRM settings in Central Administration 1.In Central Administration, on the top navigation bar, clickOperations. 2.On the Operations page, in theSecurity Configuration section, clickInformation Rights Management. 3.On the Information Rights Management page, perform one of the following steps:a)If your organization specifies the RMS server in Active Directory, verify that Use the default RMS server specified in Active Directoryis selected. b)If you are manually specifying the location of the RMS server, verify that Use this RMS server is selected and that the URL specified for the RMS server that you want to use is correct. b)To check the health and availability of the RMS server Browse to http:// (or https://) If the page is not successfully loaded, the RMS server is not operational and the problem is not specific to the site. If the RMS server is down for maintenance or otherwise inoperative, normal operations might resume after the server is back online. In this case, it is not necessary to make any changes in Windows SharePoint Services 3.0. c) Delete stored licenses The stored licenses might be corrupt. You must delete the current licenses. They will be automatically re-created. You must be a member of the SharePoint Administrators group to stop and start the Windows SharePoint Services 3.0 Web application. You must have write access to the license directories to delete these directories. To delete stored licenses 1.Stop the Windows SharePoint Services 3.0 Web application by running the following command at the command prompt. iisreset /stop 2.On the Windows SharePoint Services 3.0 front-end Web server, navigate to the %allusersprofile%\Application Data\Microsoft\DRM\Server\ folder. 3.Delete all folders named after the Windows SharePoint Services 3.0 application pool identity account. The application pool identity is the user account that Windows SharePoint Services 3.0 is running under. 4.Restart the Windows SharePoint Services 3.0 process by running the following command at the command prompt. iisreset /start Reload IRM manifests To reload the IRM manifests provided with Windows SharePoint Services 3.0, you must reinstall Windows SharePoint Service 3.0. If the problem persists after reinstallation, check the server for malicious software. |
| Reference Links | Event ID 5038 from Source Windows SharePoint Services 3 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.