在 Visual Studio 中验证 BizTalk 架构 - “自定义组件调用失败”
好吧,该错误消息根本没有帮助。我有一个无法工作的平面文件架构。
XML 有效,但 BizTalk 无法使用它。有没有办法在调用验证架构时启用详细错误日志记录?有没有比 Visual Studio 更好的工具来验证/测试 BizTalk 架构?
我是 BizTalk 的新手,我很困惑。
Well, that error message doesn't help at all. I have a flat file schema that I cannot get working.
The XML is valid, but BizTalk can't work with it. Is there a way to enable verbose error logging when calling Validate Schema? Is there a better tool for validating/testing BizTalk schemas than Visual Studio?
I'm new to BizTalk and I'm stumped.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
听起来您验证架构的调用中出现了问题。您是否忘记设置“输入实例文件名”属性?
It sounds like something is wrong in your call to validate the schema. By any chance, did you forget to set the Input Instance Filename property?
有两个问题: 使用平面文件向导构建的架构莫名其妙地默认为 Xml 源。所以它不知道它没有处理 .txt。另外我把它设置为期望 0 条记录。
There were two problems: Schemas built using the flat file wizard inexplicably default to Xml source. So it didn't know it wasn't dealing with .txt. Plus I had it set to expect 0 records.
嗨我也遇到过同样的问题。
我构建了一个工具来将 TDS1 格式模式转换为平面文件模式。 xml 架构是正确的,但未得到验证。然后我与现有的平面文件架构进行比较,发现子分隔符类型是错误的。我的工具正在创建平面文件架构,并将所有记录信息的分隔符类型设置为十六进制。
但 ;是一个字符而不是十六进制。
原始记录信息属性:child_delimiter_type="hex"
更改的记录信息属性:child_delimiter_type="char"
因此,请检查您的分隔符类型和其他记录信息属性。
希望这会有所帮助......
Hi I had faced the same problem.
I had build a tool to convert TDS1 format schema to flat file schema. The xml schema was correct but it was not getting validated. Then i compared with my existing flat file schema and i found that child delimiter type was wrong. My tool was creating flat file schema with delimiter type set to hex for all the record info.
But ; is a character and not hex.
original record info attribute: child_delimiter_type="hex"
Changed record info attribute: child_delimiter_type="char"
So please check your delimiter type and other record info attributes as well.
Hope this will help....