Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 837854 - Last Review: January 23, 2007 - Revision: 3.2
You may not be able to add more than one inbound connection to a script functoid in BizTalk Mapper
When you create a Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2004 script
functoid that contains Microsoft Visual Basic .NET scripts or Microsoft
Visual C# .NET scripts, or when the functoid links to an external assembly, you may not be able to
add more than one inbound connection to the functoid in BizTalk
Mapper.
This issue may occur when the functoid that you created contains
scripts or when the functoid links to an external assembly that has an unknown number of parameters or a variable number
of parameters.
To resolve this issue, configure the script in the functoid
to use a specific number of parameters.
To download the updated
BizTalk Server 2004 product documentation that includes information about the script functoids in BizTalk Server 2004, visit the following Microsoft Web
site:
For information about how to add script functoids to a map in BizTalk Server 2006, visit the following Microsoft Developer Network (MSDN) Web site:
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
For more information about BizTalk Server 2006 or BizTalk Server 2004,
visit the following Microsoft Web site:
APPLIES TO
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
| kbbiztalk2004-2006swept kbtshoot kbprb KB837854 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate