外部激活只启动ssis一次
这是一个很好的例子，而且效果很好。我已配置此示例以使用 sbea 启动 ssis 包。在测试中，包会触发，但只有一次。我知道它有效，因为当它触发时我有可能数据库的包日志。如果我再次测试，该包不会启动。
有趣的是，如果我结束对话并清除队列。然后拆解激活，重建它，然后再次测试，包触发并记录到数据库。
我修改了 easervice 配置并将最大并发数设置为 4，这没有什么区别。
事件查看器中只有一个事件，它来自我的包，并且仅用于初始包成功。 easervice 日志中没有添加任何内容。 sql 日志中什么也没有。
我目前不知所措，需要一些帮助。谢谢
This was an excellent example and it works well. I have configured this example to start an ssis package using sbea. In testing the package fires, but only once. I know it works because I have the package log to may database when it fires. If I test it again, the package does not fire up.
Whats interesting is that if I end the conversations and purge the queues. Then teardown activation, rebuild it then test again, the package fires and logs to the db.
I modified the easervice config and set the max concurrecny to 4 it makes no difference.
There is only one event in the event viewer and it's from my package and only for the intital package success.
There is nothing added to the easervice log.
And nothing in the sql log.
I am at loss currently and could use some help. Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我能够确定我的问题出在包本身的接收语法中。
我没有正确处理对话句柄，所以我的回应永远不会结束对话。然而令人失望的是，即使包内有三个级别的日志记录也没有在任何地方记录该问题。今天我将回顾该方法。
干杯
I was able to determine that my issue resided in my recieve syntax within the package itself.
I was not handling the conversation handle correctly so my response was never ending the conversation. It is disappointing however that even with three levels of logging within the package did not log the issue anywhere. I will be reviewing that methodology today.
Cheers