04/10/2009 10:06:03.00* w3wp.exe (0x13A4) 0x150C Windows SharePoint Services Workflow Infrastructure 72fs Unexpected ...rkflow, SPWorkflow workflow, Collection`1 events, SPRunWorkflowOptions runOptions)
04/10/2009 10:06:03.00 w3wp.exe (0x13A4) 0x150C Windows SharePoint Services Workflow Infrastructure 98d7 Unexpected Microsoft.SharePoint.SPException: at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(String assmNameIn, SPWeb web) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(Guid trackingId, SPWorkflow workflow) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow originalWorkflow, SPWor...
04/10/2009 10:06:03.00* w3wp.exe (0x13A4) 0x150C Windows SharePoint Services Workflow Infrastructure 98d7 Unexpected ...kflow workflow, Collection`1 events, SPRunWorkflowOptions runOptions)
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(6)
工作流调用应该是工作流.cs 文件中的第一个活动,然后是其他代码段。 构建将编译。
Workflow invoke should be the first activity in your workflow.cs file and thereafter have other code pieces. The build will compile.
我认为这与您在工作流程中使用的条件规则有关,但我不记得 WF 如何存储和访问它们的具体内容
I'm thinking it's something to do with the condition rules that you use in your workflow but I can't remember the specific's about how they're stored and accessed by the WF
棘手。 此时,我的猜测是,最好的选择是打开工作流文件,您可以从 SharePoint Designer 访问该文件(在其中打开原始/根/模板 Web)。
找到工作流文件后,不要在可视化设计器中打开它们,而是尝试在记事本中打开它们,以便看到 XML 源代码。 现在不要搞乱它,但这样您应该能够找到在模板导出的网络中失败的规则和活动“13”和“21”。 查找 ID13、__Rule_ID13、ID21 和 __Rule_ID21。 这里的想法是找出哪两个活动/条件对失败。 一旦您知道它们是什么,您可以:
不要认为有一个简单的答案。 一般来说,SharePoint Designer 工作流(特别是在仅 WSS 的环境中)确实有其局限性和故障。
Tricky. At this point my guess is that your best bet is to open your workflow files, which you can access from SharePoint Designer (open your original/root/template web in it).
Once you've located the workflow files, instead of opening them in the visual designer, try opening them in Notepad so you see the XML source code. Don't mess with it right now, but this way you should be able to find the rules and activities "13" and "21" that fail in template-exported webs. Look for ID13, __Rule_ID13, ID21 and __Rule_ID21. The idea here is to find out which two of your activity/condition pairs fail. Once you know which they are, you can:
Don't think there is an easy answer. SharePoint Designer workflows in general, particular in a WSS-only environment, certainly do have their limitations and glitches.
警告!!在生产环境中打开诊断日志记录可能会使服务器崩溃。
在中央管理> 操作> 诊断记录> 事件限制:
类别 = 所有
事件日志 = 信息
跟踪日志 = 详细 !!危险!!
查看 C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS 中的最新日志(复制并粘贴到 Excel 中)
筛选“类别”以查找“工作流程基础设施”。 这应该开始引导您走上正确的道路。 希望它有帮助并祝你好运
Ian Philpot
Warning!! Turning on Diagnostic Logging in production could crash the server.
In Central Admin > Operations > Diagnostic Logging > Event Throttling:
Category = All
Eventlog = information
tracelog = verbose !!Danger!!
Look at the most recent log in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS (copy and paste into excel)
Filter "Category" for "Workflow Infrastructure". This should start leading you down the right path. Hope it helps and wish you luck
Ian Philpot
问题在于 SharePoint 设计器工作流使用该列表的 GUID 与特定列表实例关联。 当您将网站另存为模板并使用该模板重新创建新网站时,创建的列表将使用与该模板所基于的列表相同的列表模板,但它将具有不同的标识 GUID。 重复使用使用 SharePoint 设计器创建的工作流是一个常见问题。
这是一种可能的解决方案,尽管每次从模板创建新站点时都需要一些繁重的工作:http://nickgrattan.wordpress.com/2007/10/17/applying-a-sharepoint-designer-workflow-to-multiple-lists/< /a>
您最好做的可能是创建一个站点定义(要小心,因为您必须遵循公认的做法,这是一个开始 http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=117) 包含一个列表实例,其中已使用 Visual Studio 创建为功能的附加工作流。
The problem is that SharePoint designer workflows are associated with a particular list instance using the GUID of that list. When you save a site as a template and recreate a new site using that template the list that is created will use the same list template as the list the template was based off but it will have a different identifying GUID. Re-use of workflows created with SharePoint designer is a common problem.
Here is one possible solution though it requires some grunt work each time a new site is created from the template: http://nickgrattan.wordpress.com/2007/10/17/applying-a-sharepoint-designer-workflow-to-multiple-lists/
What you'd probably be best to do would be to create a site definition (be careful because you must follow accepted practice, here is a start http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=117) that contains a list instance with an attached workflow that has been created as a feature using Visual Studio.
这是 Simon Fox 所说的 GUID 问题
It is the GUID problems as stated by Simon Fox