SYMPTOMS
The error message appears when you use BizTalk’s Cumulative Functoids.
-----------------------------------------
Error Details: “error btm1050: XSL transform error: Unable to write output instance to the following <file:///C:\…..\Map1_output.xml>. Function 'userCSharp:MyConcat()' has failed. Value was either too large or too small for an Int32.”
This problem may occur when the Cumulative Functoid accept a Null input argument.
The script detail:
RESOLUTION
Change the script to below code:
-----------------
public int MyConcat(double param1)
{
if (param1 > 0 && param1 < 100)
return (int)param1;
else
return 0;
}
----------------------
SYMPTOMS
The error message in the event log as below:
A message sent to adapter "SMTP" on send port "Orders_1.0.0.0.Orders.Email_DynamicSendPort_e369e0033a074fb3" with URI "mailto:xxx@xxx.xxx" is suspended.
Error details: Unknown Error Description.
RESOLUTION
A known issue with the SMTP Adapter, especially with a dynamic port. Set a value to SMTP.EmailBodyTextCharset, you will work out the issue.
Sample Code:
msgEmail(SMTP.EmailBodyTextCharset) = “UTF-8”;
SYMPTOMS
The error message appears on the status bar when you try to add a BizTalk 2009 project in Visual Studio 2008.
-----------------------------------------
Error Details: “Create BizTalk Project …. Project Creation Failed”
This problem may occur after you applied SP1 for VS.
RESOLUTION
Browse to the installation folder of BizTalk 2009, run setup.exe, and choose “Repair” button, after that, you will work out the issue.
SYMPTOMS
The SQL Adapter may fail and you may receive an error message that is similar to the following:
-------------------
Error details: HRESULT='xxxxx' Description="Could not find stored procedure 'sp_xxxxx". as below:
This problem may occur when there is no SP in Database or you changed the name of store procedure.
RESOLUTION
Once changed the name of the store procedure, make sure you finish the one of below steps:
1. Re-generate all related schemas and other artifacts.
Or 2. If you choose to modify the schema manually, you must change annotation value & node name to tailor the new SP's name.
As Below:
When you try to refresh Admin Console, you get an error message.
SYMPTOMS:
PaintTabBackgroundError - rect:{X=86,Y=2,Width=98,Height=18} - extraRampWidth:12
------------------------------
ADDITIONAL INFORMATION:
A generic error occurred in GDI+. (System.Drawing)
As Below:
CAUSE:
This annoying error message is always due to another session is also using the console, such as a remote console, no solution, but you can find some clues from below link:
Bitmap and Image constructor dependencies
When you try to using Biztalk WCF Service Consuming Wizard, you get an error message.
Error details: "Error consuming WCF service metadata. Object reference not set to a instance of an object."
As Below:
Resolutions:
1, Generate WSDL and XSD files by using svcutil tool
> svcutil.exe /t:metadata http://yourservice
2, Verify <xsd:schema> nodes in WSDL file, make sure the node has a target namespace define. It doesn't matter what attribute value you use, maybe just looks like <xsd:schema targetNamespace=http://any.
3, Select Metadata Files(WSDL and XSD) as the source
4, Everything should be fine.
Run regedt32, expand to HKEY_LOCAL_MACHINE->SOFTWARE->Microsoft->BizTalk->3.0;
If the value of the the ProductVersion key is greater than 3.6.1404.0, the version of BizTalk Server is 2009.
BizTalk Server是一个大型应用程序，它通常会为完成一些事情提供几种方法。 但是由于各种各样的原因，一些方法存在陷阱需要避免使用:
- 避免使用 BizTalk Server 2006 中的 BizTalk 浏览器。此功能在 BizTalk Server 2004 中至关重要，因此，Microsoft 决定不将它从 BizTalk Server 2006 中去除，但新的应用程序打包功能和经过重新设计的 BizTalk 管理控制台已使其成为多余的。在某些情况下使用它会造成麻烦。
- 在 Visual Studio® 2005 解决方案资源管理器中，永远不要在“项目”一级上单击“部署”。 在解决方案中独立构建项目是可以的，但您只应在“解决方案”一级上单击“部署”。 原因是： Visual Studio 会尝试自动跟踪依赖关系，而单独为 BizTalk 部署程序集可能会导致它无法进行跟踪。
- 仔细编辑命名空间属性（以确保匹配）就能将架构文件 (.XSD) 从一个项目复制到另一个项目。 记住这一点，不然您肯定会遇到让您大为头疼的问题。
- BizTalk 专家从不使用 Quick Promote。 等到您采取必要的步骤来纠正它提供给您的类型时（假如您还记得这样做），您会发现其实您自己本来可以快速显式地创建这些类型。
- 不要将映射放入业务流程中，除非您需要将多个传入消息映射到一个消息中，或者您需要以现有消息的经过修改（映射后）的内容为基础生成一条新消息。 为简化部署，最好将您的映射放到“接收”和“发送”端口上。 如果您的业务合作伙伴对其架构进行了修改，或者如果您添加了需要新映射的新合作伙伴，您将不得不同时更新您的架构和业务流程，而这不是您所希望的。
The following table indicates the supportability of BizTalk Server in the different virtual environments. In this table, "Yes" means that it is fully supported.
BizTAlk Server 2006 R3 will now be called BizTalk Server 2009, What to expect in the 2009 release of BizTalk:
- Support for the latest Microsoft Platforms including Hyper-V Virtualization, Visual Studios 2008, .Net 3.5, SQL 2008, and Windows Server 2008.
- Enhancements to SOA and Web Services, B2B Integration, and Developer Productivity.
- Additional enhancements driven by customer feedback
Change IP Address of the BizTalk boxes is supported except below senarios:
1, If the server has the MSMQ adapter, in which case the server needs to be reinstalled(http://support.microsoft.com/kb/836487)
2, If you are using IP Addresses anywhere in your configuration instead of of server names (eg.remote host IP) , then you have to export all of your bindings in the server and make sure you are not pointing back to the server itself somehow.
3, During installations period, sometimes the entire system run with IP Addresses instead of host names (MS DTC with no authentication). Check it in your BizTalk Configuration Tool, on the View Menu select Databases and review the database server list to make sure they are all using Server names not IP Addresses. Then in the Configuration tool, select each node and make sure nothing is using IP Addresses.
Error Message: The catalog export process failed
Error Message:
Event Type: Error
Event Source: Commerce Server Web Services
Event Category: None
Event ID: 1
Date: 5/1/2008
Time: 10:14:06 AM
User: N/A
Computer: WSECOMBPDEV1
Description:
An exception occurred in the 'ExportCatalog' Web service. Exception details follow:
Microsoft.CommerceServer.Catalog.CatalogDatabaseException: Failed to log the start import, export or rebuild operation. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at ......
Resolution:
when you Enable a receive location with Catalog Adapter, nothing happened. If you check the event from Commerce Server, you will find above Error Messages.
There are two ways to fix this issue:
1, Change the value of "Connection Timeout" to an appreciate value.
2, Add below line to Web.config of Webservice(For example, CatalogWebservice):
<httpRuntime executionTimeout="400"/>
Note: You may be required to do both actions.
This application will determine a text file encoding using visual inspection.
Encoding
Format that defines how the values of certain types are represented, in terms of bits. Examples: American Standard Code for Information Interchange (ASCII), a 7-bit character set; and Unicode, a 16-bit character set.
