为什么我的 Sharepoint IRM 模块无法间歇性地重新初始化?
我有一个在大部分时间都可以工作的 Sharepoint IRM 模块。然而,大多数早晨,当我进来尝试锻炼时,它都不起作用。 IISReset 通常会让它再次运行。
大多数早上 01:45 左右,Windows 事件日志都会显示以下错误(本文中 GUID 为空白)。
Information Rights Management (IRM): Protector {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} experienced a problem while being initialized.
Protector: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
Additional Data
Error value: 80070005
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
此错误与其他三个 IRM 模块成功重新初始化的其他事件一起发生(我相信这些是内置的)。
Sharepoint 日志包含非常相似的内容:
09/22/2010 01:45:20.39 w3wp.exe (0x11EC) 0x1338 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}
09/22/2010 01:45:20.56 w3wp.exe (0x11EC) 0x1338 Windows SharePoint Services IRM 95lu Information Information Rights Management (IRM): The initialization of protector {4F9976DC-47C3-4518-B2A2-A258B379F970} was completed. Protector: {4F9976DC-47C3-4518-B2A2-A258B379F970}
09/22/2010 01:45:20.58 w3wp.exe (0x11EC) 0x1338 Windows SharePoint Services IRM 95lu Information Information Rights Management (IRM): The initialization of protector {4F9976DE-47C3-4518-B2A2-A258B379F970} was completed. Protector: {4F9976DE-47C3-4518-B2A2-A258B379F970}
09/22/2010 01:45:20.61 w3wp.exe (0x11EC) 0x1338 Windows SharePoint Services IRM 95lt Critical Information Rights Management (IRM): Protector {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} experienced a problem while being initialized. Protector: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} Additional Data Error value: 80070005
IRM 模块在 HrSetLangId 和 HrInit 中也有自己的日志记录。在此故障情况下,模块未记录任何内容。
Microsoft 针对处理此错误代码的建议主要围绕检查 Sharepoint 是否可以与 RMS 服务器通信。对于我们的 IRM 模块,我们实际上不需要 RMS 服务器,因此还没有设置。由于问题是间歇性的,这似乎不太可能是原因。
IISReset 后,模块似乎已正确初始化(在所有 3 个日志中)并再次开始工作。
FWIW 该模块是用 C# 编写的。
任何有关如何解决此问题的建议将不胜感激。
I have a Sharepoint IRM module that works most of the time. However, most mornings when I come in and try to exercise it it fails to work. An IISReset will generally get it going again.
The Windows event log shows the following error most mornings at around 01:45 (GUID blanked for this post).
Information Rights Management (IRM): Protector {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} experienced a problem while being initialized.
Protector: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
Additional Data
Error value: 80070005
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This error occurs along with three other events for three other IRM modules successfully re-initializing (I believe these are built-in ones).
The Sharepoint log contains something very similar:
09/22/2010 01:45:20.39 w3wp.exe (0x11EC) 0x1338 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}
09/22/2010 01:45:20.56 w3wp.exe (0x11EC) 0x1338 Windows SharePoint Services IRM 95lu Information Information Rights Management (IRM): The initialization of protector {4F9976DC-47C3-4518-B2A2-A258B379F970} was completed. Protector: {4F9976DC-47C3-4518-B2A2-A258B379F970}
09/22/2010 01:45:20.58 w3wp.exe (0x11EC) 0x1338 Windows SharePoint Services IRM 95lu Information Information Rights Management (IRM): The initialization of protector {4F9976DE-47C3-4518-B2A2-A258B379F970} was completed. Protector: {4F9976DE-47C3-4518-B2A2-A258B379F970}
09/22/2010 01:45:20.61 w3wp.exe (0x11EC) 0x1338 Windows SharePoint Services IRM 95lt Critical Information Rights Management (IRM): Protector {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} experienced a problem while being initialized. Protector: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} Additional Data Error value: 80070005
The IRM module also has its own logging in HrSetLangId and HrInit. In this failure case nothing was logged by the module.
Microsoft's suggestions to deal with this error code mainly revolve around checking that Sharepoint can talk to an RMS server. In the case of our IRM module we actually don't need an RMS server and so have not set one up. As the problem is intermittent this doesn't seem likely to be the cause.
After an IISReset the module appeared to initialize correctly (in all 3 logs) and started working again.
FWIW the module is written in C#.
Any suggestions on how to cure this problem would be gratefully received.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我仍然不确定到底是什么问题,但删除 HrSetLangId 和 HrInit 中的日志记录后,错误就消失了。因此,模块重新初始化的方式与第一次初始化的方式有所不同,在前一种情况下,日志记录会失败,但在后一种情况下,日志记录不会失败。
I'm still not sure exactly what the problem was after but removing the logging in HrSetLangId and HrInit the error went away. So something about the way the module is re-initialised is different from the first initialisation in such a way that the logging fails in the former case but not the latter.