加载和运行事件接收器 Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver 时出错
我有一个附加到自定义 ItemAdded 事件接收器的自定义 SharePoint 工作流，该工作流一直运行良好，直到我使用 WSPBuilder 升级它的最后一个类型。
我的代码非常接近这个示例： http://www.codeproject.com/KB /sharepoint/MOSS_FolderContentTypeWF.aspx
我过去使用过 WSPBuilder，但没有用于这个项目，它似乎以某种方式破坏了我的工作流程。
我的工作流程即使应该启动也没有启动，当我查看事件日志时，我看到以下错误：
加载和运行事件时出错 接收者 Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver 在 Microsoft.SharePoint 中， 版本=12.0.0.0，文化=中立， 公钥令牌=71e9bce111e9429c。
其他信息如下。
：指定的对象不属于 到一个列表。
因此，我禁用了事件处理程序，甚至将其删除，但该文档库仍然出现错误。其他站点的文档库上不会生成该错误。我是否破坏了 SharePoint 内部的事件接收器？
有想法吗？
I have a custom SharePoint workflow attached to a custom ItemAdded event receiver that was working fine up until the last type I promoted it using WSPBuilder.
My code is very close to this example: http://www.codeproject.com/KB/sharepoint/MOSS_FolderContentTypeWF.aspx
I used WSPBuilder in the past but not for this project and it seems to have broken my workflow somehow.
My workflow doesn't start even though it should and when I look in the event logs I see the following error:
Error loading and running event
receiver
Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver
in Microsoft.SharePoint,
Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c.Additional information is below.
: The object specified does not belong
to a list.
So I disabled my event handler and even removed it and the error still happens for this document library. The error isn't generated on other site's doc libraries. Did I break an event receiver in the guts of SharePoint?
Ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
考虑到它工作正常，您在源代码管理中是否有以前的工作副本？如果是这样，请尝试部署它以查看问题是否得到解决。
如果这解决了问题，则问题出在 Visual Studio 项目中。然后，您可以通过使用某种 diff 工具（例如 WinMerge）比较更改来纠正它。
更新响应答案/评论：SharePoint Manager 等工具一种查看 SharePoint 网站“内部结构”的绝佳视觉方式。使用它可以将 SharePoint 中的预期内容与实际内容进行比较。
Considering it was working fine, do you have the previous working copy in source control? If so try deploying that to see if the problem is rectified.
If this fixes it the problem lies within the Visual Studio project. You can then correct it by comparing the changes with some sort of diff tool such as WinMerge.
Update in response to answer/comment: A tool such as SharePoint Manager is a great visual way to see the "guts" of your SharePoint site. Use this to compare what you're expecting in SharePoint with what's actually there.