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.
BizTalk Server 2006 R3预期在CY09的第一季度发布，Beta版大概在今年年底。
R3新的功能包括：
- 支持Visaul Studio 2008和SQL Server 2008;
- 大部分ESB现有的功能
- SOA Patterns
You’re invited to join the BizTalk Server Group. Joining will allow you to find and contact other BizTalk Server Group members. The goal of this group is to help members:
- Reach other members of BizTalk Server Group
- Accelerate careers/business through referrals from BizTalk Server Group members
- Know more than a name – view rich professional profiles from fellow BizTalk Server Group members
Here’s the link to join:
[BizTalk Server Group]
Hope to see you in the group,
— The BizTalk Group Team
BizTalk Server logs information, warnings, and errors to the event log of the BizTalk Server-based computer. When troubleshooting problems in a BizTalk Server component or dependency, the event logs should be the first place to look for information to help diagnose the problem. For more information about Event Viewer, see "Event Viewer" in the Windows Server 2003 product Help at http://go.microsoft.com/fwlink/?linkid=104797.
Use Network Monitor to capture network traffic between BizTalk Server and remote clients or servers. Captured network traffic can then be analyzed to diagnose network related problems.
Network Monitor is available on Windows 2000 Server and Windows Server 2003 through the Add or Remove Windows Components option that is available in Add or Remove Programs.
Network Monitor functionality is provided for Windows XP through the use of the NETCAP.exe utility that is installed with the Windows Support Tools available on the Windows XP CD. For more information about the NETCAP.exe utility, see "Description of the Network Monitor Capture Utility" at http://go.microsoft.com/fwlink/?LinkId=66227.
For information about how to capture network traffic with Network Monitor, see "How to Capture Network Traffic with Network Monitor" at http://go.microsoft.com/fwlink/?LinkId=66230.
Use Fiddler to record all HTTP traffic between BizTalk Server and remote clients or servers. Fiddler is compatible with Visual Studio Team Edition for Testers and allows you to save recordings as Web test files that can be added to Visual Studio Team Edition for Testers projects.
Fiddler is available at http://go.microsoft.com/fwlink/?LinkId=107050. For more information about how to use Fiddler, see http://go.microsoft.com/fwlink/?linkid=84796.
Microsoft SQL Server Profiler can be used to capture Transact-SQL statements that are sent to SQL Server and the SQL Server result sets from these statements. Since BizTalk Server is tightly integrated with SQL Server, the analysis of a SQL Server Profile trace can be a useful tool for analyzing problems that may occur in BizTalk Server when reading from and writing to SQL Server databases. For information about how to use SQL Server Profiler, see the "Using SQL Server Profiler" in the SQL Server 2005 Books Online at http://go.microsoft.com/fwlink/?linkid=104423.
SQL Server 2000 Query Analyzer and the SQL Server 2005 SQL Server Management Studio can be used to execute SQL statements directly against SQL Server databases. This functionality may be useful for querying the BizTalk Server databases or for updating the BizTalk Server databases in certain scenarios. For more information about Query Analyzer, see "SQL Query Analyzer Help" in the SQL Server 2000 Books Online at http://go.microsoft.com/fwlink/?linkid=104424. For more information about using SQL Server Management Studio to execute SQL statements, see "Writing, Analyzing, and Editing Scripts with SQL Server Management Studio" in the SQL Server 2005 Books Online at http://go.microsoft.com/fwlink/?linkid=104425.
Most BizTalk Server runtime operations require Microsoft Distributed Transaction Coordinator (MSDTC) support to ensure that the operations are transactionally consistent. If MSDTC transaction support is not available, then the associated BizTalk Server runtime operations cannot proceed. Use the DTCTester tool to verify distributed transaction support across firewalls or against networks. The DTCTester utility uses ODBC to verify transaction support against a SQL Server database and therefore requires that SQL Server is installed on one of the computers being tested. For more information about DTCTester, see "How to Use DTCTester Tool" in the Microsoft Knowledge Base article at http://support.microsoft.com/kb/293799.
Use the DTCPing tool to verify distributed transaction support across firewalls or against networks. The DTCPing tool must be installed on both the client and server computer and is a good alternative to the DTCTester utility when SQL Server is not installed on either computer. For more information about using DTCPing to verify distributed transaction support, see "How to troubleshoot MS DTC firewall issues" in the Microsoft Knowledge Base article at http://support.microsoft.com/kb/306843.
Use the Performance Console to capture performance monitoring data in your BizTalk Server environment. See "Performance Counters" in BizTalk Server 2006 R2 Help at http://go.microsoft.com/fwlink/?linkid=104641 for a comprehensive list of the performance counters included with BizTalk Server 2006. For more information about using Performance Console, see the Windows documentation.
RegMon displays registry access activity in real time, listing each call to the registry that an application makes, and logging the outcome. This tool allows you to identify when an application cannot access a registry key. Similarly, FileMon displays file system activity in real time, listing each system call that an application makes and registering the outcome. DebugView lets you monitor debug output on your local system, or any computer on the network that you can reach via TCP/IP.
RegMon and FileMon enable administrators to test an application and to identify the failure of any calls that the application makes to the registry or file system. The administrator can then mitigate that failure, for example, by changing file system or registry key permissions.
DebugView enables administrators to test an application and monitor debug output on your local system, or any computer on the network that you can reach via TCP/IP.
For more information about these utilities, see the Windows Sysinternals Web site at http://go.microsoft.com/fwlink/?LinkID=86409.
The Debug Diagnostics Tool of the IIS Diagnostics toolkit can generate a memory dump of a failing process and perform a basic analysis of the generated dump file. For more information about using the Debug Diagnostics Tool of the IIS Diagnostic Toolkit to capture a memory dump see "How to Capture a Memory Dump of a BizTalk Server Process" in BizTalk Server 2006 R2 Help at http://go.microsoft.com/fwlink/?linkid=104642.
Microsoft BizTalk LoadGen 2007 Tool
Microsoft LoadGen 2007 generates message transmission loads to run performance and stress tests for your Microsoft BizTalk Server applications, and provides performance counters to monitor the performance of the infrastructure running BizTalk Server.
This tool is intended for developers and IT professionals to simulate load on a BizTalk Server. Using this tool, you can simulate load to instrument performance and stress against a BizTalk deployment. In addition, this tool may also be extended by developers to simulate load for custom transports. This tool should be used in a test environment only, and should not be used in a production environment. This tool is provided "as-is" and is not supported.
BizTalk Server 2006 Best Practices Analyzer
The BizTalk Server 2006 Best Practices Analyzer performs configuration-level verification by reading and reporting only. The Best Practices Analyzer gathers data from different information sources, such as Windows Management Instrumentation (WMI) classes, SQL Server databases, and registry entries. The Best Practices Analyzer uses the data to evaluate the deployment configuration. The Best Practices Analyzer does not modify any system settings, and is not a self-tuning tool.
BizTalk Server Restore Script for BizTalk 2006 Standard Edition
This script is needed for replacement of BizTalk Servers running BizTalk Server 2006 standard edition after they encounter an irrecoverable failure. Please BizTalk Server product documentation on Disaster Recovery for BizTalk servers for more details on usage of the script.
This topic describes several tools and utilities that can be useful for diagnosing the root cause of a problem in a Microsoft BizTalk Server component or dependency.
Below tools can be found under BizTalk Installation package:
PSSDiag for BizTalk
PSSDiag for BizTalk is a troubleshooting tool for Microsoft support engineers to capture diagnostic data.
BizTalk Server 2006 Assembly Checker and Remote GAC Tool
This tool is designed to check the versions of Assemblies that have been deployed in a BizTalk 2006 Environment and to make sure the correct versions are registered in the GAC when you have a multiple BizTalk Servers in a Management DB. When you are using multiple machines in a BizTalk Server 2006 environment, it is very important to make sure the same version of the Assembly has been deployed to all the machines.
You can also use this tool to selectively deploy the Assemblies to the remote servers using the GAC Tool.
Problem
You need to find a special character when use the String Find Mapping functoid, such as a (carriage return) or a NL line feed).
Solution
BizTalk provides a String Find functoid: Use the String Find functoid to return the position in a string at which another specified string begins. This functoid requires two input parameters: the string that is being searched through, and the string which is being sought.
Sometimes you need to search a special character, for example, the original string looks like as below:
"This is a testing.
This is another testing"
The string is a multi-line string, which you only want to get the first line, so you may imagine to use String Find Mapping functoid to return the position of <CR> and then to use String Left Mapping functoid to return the first line. However, you cannot directly input a special character in String Find Mapping functoid!
Luckily, there is another functoid named ASCII to Character functoid 
to return a character when given an ASCII value as input. You can just input "13" as this functoid's parameter, as below:
The final solution should looks like as below:
症状：调用Rule/Policy后，无法得到结果，或处理的消息没有如期的结果
原因：
1，首先在Orchestration Designer中，检查有没有指定需要传递的参数（消息）
2，在Business Rule Composer中检查Document Type值，是否与Message的namespace匹配
3，如果Fact用到数据库，还需要检查Database binding type得值
This problem may manifest itself in several ways:
- The configuration manager will load the Overview page correctly, but when attempting to configure a feature the feature options do not display on the screen.
- The configuration wizard cannot connect to the SQL Server.
- Attempting to Unconfigure All unconfigures some features, but not all.
Cause
The BizTalk Server configuration stores the computer network name. When the computer is renamed the configuration manager and configuration wizard cannot locate the BizTalk Server. A similar problem will occur if the SQL Server computer is renamed after BizTalk Server is configured.
Resolution
Do not rename the BizTalk Server computer or the SQL Server computer. If a server must be renamed, unconfigure all BizTalk Features before renaming the computer. After renaming the computer, reconfigure BizTalk Server features.
If you rename a SQL server you have to do this as well:
select @@servername
go
--If name is not correct to what you connect to, change it:
sp_dropserver OLDServerName
go
sp_addserver NewServerName, local
go
-- Restart SQL Service and verify with select @@servername again
Never thought its worth that much. I am not quite convinced.
