通过Web.config在WorkflowServices中的持久性 [英] Persistence in WorkflowServices via Web.config

查看:53
本文介绍了通过Web.config在WorkflowServices中的持久性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我对工作流程服务的BETA 2的持久性有疑问.我有一个实现关联的工作流服务,并且可以完美地工作,直到在web.config中放入以下行:

<

I'm having a problem with persistence in BETA 2 for a workflowservice.  I have a workflowservice that implements correlation and works perfectly UNTIL I put the following line in the web.config:

<

sqlWorkflowInstanceStore connectionString 数据源=.\ SQLEXPRESS;初始目录= InstanceStore;集成安全性= True "

sqlWorkflowInstanceStore connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=InstanceStore;Integrated Security=True"/>

 


当我将该行放入时,会出现以下错误:

已经添加了具有相同键的项.


When I put that line in, I get this error:

An item with the same key has already been added.

服务器堆栈跟踪:在System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(消息答复,MessageFault错误,字符串操作,MessageVersion版本,FaultConverter faultConverter)中的
在System.ServiceModel.Channels.ServiceChannel中. HandleReply(ProxyOperationRuntime操作,ProxyRpc& rpc)
在System.ServiceModel.Channels.ServiceChannel.Call(字符串操作,布尔型单向,ProxyOperationRuntime操作,Object [] ins,Object [] outs,TimeSpan超时)
在System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall,ProxyOperationRuntime操作)
在System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage消息)

Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

在[0]处抛出异常:在System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg,IMessage retMsg)
在System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke( MessageData&msgData,Int32类型)
在ICreateAutoQuote.Init(InitRequest请求)
在CreateAutoQuoteClient.ICreateAutoQuote.Init(InitRequest请求)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at ICreateAutoQuote.Init(InitRequest request)
   at CreateAutoQuoteClient.ICreateAutoQuote.Init(InitRequest request)

推荐答案

碰碰...有人吗?谁在做托管在IIS中的WorkflowServices的持久化?我错过了一些设置吗?我找不到关于此的任何文档-非常令人沮丧!
Bump...anyone?  Who's doing persistence of WorkflowServices hosted in IIS?  Is there some setup that I missed?  I cannot find any doc on this - so frustrating!!


这篇关于通过Web.config在WorkflowServices中的持久性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆