工作流运行时所有权已过期
我在 Windows 工作流基础中面临一个奇怪的问题。 我创建了一个状态机工作流程,它在一次构建中运行得非常好,但由于一些要求,我改变了工作流程,构建并重新安装了应用程序。 现在,当我尝试访问在先前构建中创建的工作流实例时,它会给出一个 WorkflowOwnershipException
:
此工作流不属于 WorkflowRuntime。 WorkflowRuntime 的所有权已过期,或者另一个 WorkflowRuntime 拥有该工作流。
是否有解决方法或方法来解决此问题的根本原因?
I am facing a strange problem in windows workflow foundation. I have created a State Machine Workflow, and it worked very fine in one build, but due to some requirements I altered the workflow, built and re-installed the application. Now when I am trying to access workflow instances that I created in a previous build, it gives me a WorkflowOwnershipException
:
This workflow is not owned by the WorkflowRuntime. The WorkflowRuntime's ownership has expired, or another WorkflowRuntime owns the workflow.
Is there a workaround or way to fix the root cause of this problem?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
持久化服务的锁定时间是多长? 我假设您正在使用内置的 SqlWorkflowPersistenceService。
也许此信息对您有帮助:
http: //www.dotnetconsult.co.uk/weblog2/PermaLink,guid,9c484cc4-ddd7-4dfd-b8e3-d5517fe9b0a2.aspx
How long is the lock time for the persistence service? I'm assuming you're using the built in SqlWorkflowPersistenceService.
Maybe this infomation helps you:
http://www.dotnetconsult.co.uk/weblog2/PermaLink,guid,9c484cc4-ddd7-4dfd-b8e3-d5517fe9b0a2.aspx