工作流SqlTrackingService不保存数据 [英] Workflow SqlTrackingService Not Saving Data

问题描述

我正在尝试为Workflow Foundation实现SqlTrackingService。我已经安装了架构&逻辑并已将相应的代码添加到web.config文件的Service元素中。我知道我的应用程序正在尝试访问
跟踪表，因为如果我重命名它们会引发错误。

I’m trying to implement the SqlTrackingService for Workflow Foundation. I’ve installed the schema & logic and have added the appropriate code to the Service element of the web.config file. I know that my application is trying to access the tracking tables because if I rename them it’s throws an error.

我已经创建并完成了工作流但没有数据出现在跟踪表中。从我所读到的它应该工作OOB但我错过了什么？

I’ve created and completed a workflow but no data is appearing in the tracking tables. From what I’ve read it should work OOB but am I missing something?

其他几个问题。我最初将跟踪表放在一个单独的数据库中，但我的应用程序并不像跟踪是在应用工作流的内容的单独数据库中。这是跟踪必须实现的方式吗？

Couple of other questions. I originally put the tracking tables in a separate database but my application didn’t like the tracking being in a separate database to the content to which workflow was being applied. Is this how tracking has to be implemented?

我们将数据库连接详细信息放在与web.config不同的文件中，我可以对跟踪数据库连接执行相同的操作，还是这样做？到服务的属性/

We put our database connection details in a separate file from the web.config, can I do the same for the tracking db connection or does this have to an attribute of the service/

应用程序是.Net 3.5& SQL Server 2005.它还使用SharedConnectionWorkflowCommitWorkBatchService& SqlWorkflowPersistenceService并查看其他一些线程，我想知道这是否有影响。

Application is .Net 3.5 & SQL Server 2005. It also uses SharedConnectionWorkflowCommitWorkBatchService & SqlWorkflowPersistenceService and looking at some other threads I wondered if this has an impact.

提前致谢

Neil

推荐答案

只有持久性和跟踪在同一个数据库中并共享相同的连接字符串时，SharedConnectionWorkflowCommitWorkBatch才有用。您提到与工作流内容位于不同的数据库中。使用TransactionScope活动或IPending工作时，您的工作流是否会执行任何其他
交易数据工作？这些会导致项目与工作流持久性保持在同一个事务中，如果未启用DTC，则会导致问题。

The SharedConnectionWorkflowCommitWorkBatch is only useful if persistence and tracking are in the same database and share the same connection string. You mention being in a separate database from the content of your workflow. Does your workflow do any other transactional data work, with TransactionScope activity or IPending work? These would cause items to be persisted in the same transaction as the workflow persistence and if DTC is not enabled it would cause a problem.

您是否完成了WorkflowTrace.log？这将准确显示运行时中发生的情况，并对确定问题很有用。您可以按照以下步骤启用它：

http://blogs.msdn.com/b/madhuponduru/archive/2008/01/17/workflow-trace.aspx

Have you done a WorkflowTrace.log? This will show exactly what is happening in the runtime and is useful for determining problems. You can enable that by following the steps here: http://blogs.msdn.com/b/madhuponduru/archive/2008/01/17/workflow-trace.aspx

另外，你有吗？在事务模式下配置的跟踪服务（排队所有跟踪记录并在工作流程持续存在时提交它们）？如果是这样，并且工作流因任何原因而无法保留，则不会写入跟踪。如果是这种情况，workflowtrace.log
将显示错误条件。

Also, do you have the tracking service configured in transactional mode (queue up all tracking records and commit them when the workflow persists)? If so, and the workflow fails to persist for any reason, the tracking will not get written. The workflowtrace.log will show error conditions if this is the case.

请查看workflowtrace.log所说的内容并告诉我们。

Please take a look and see what the workflowtrace.log says and let us know.

谢谢，

Steve Danielson [微软]

此帖子提供"按现状"没有保证，也没有授予任何权利。

使用包含的脚本样本须遵守
http://www.microsoft.com/info/cpyright.htm

Steve Danielson [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

这篇关于工作流SqlTrackingService不保存数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！