Troubleshooting BizTalk Server SetupWord格式文档下载.docx

1、 2010 Microsoft Corporation. All rights reserved.Microsoft, Windows, Windows Server, Windows Vista, Active Directory, BizTalk, Excel, SharePoint, SQL Server, Visual C#, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countri

2、es.All other trademarks are property of their respective owners.ContentsTroubleshooting BizTalk Server 2010 Setup 4Introduction 4Review Installation Steps 4Some BizTalk EDI/AS2 artifacts are still active after unconfiguring 5If the BizTalk Server Computer or SQL Server computer is renamed after BizT

3、alk Server configuration, the Configuration Wizard will fail 5The BizTalk Server Business Rules Configuration Wizard fails 6Configuration Logging 7Troubleshooting Tools 7Known Issues with Enterprise Single Sign-On 13Known Issues in this Release of BizTalk Server 15Custom Action 18Troubleshooting Biz

4、Talk Server 2010 SetupDocumentation FeedbackMicrosoft values your feedback. To send feedback and comments about this topic to the documentation team, click here.IntroductionThis Troubleshooting Guide lists known issues as well as the most common problems you may encounter while installing BizTalk Se

5、rver 2010. This guide also includes Custom actions which provides details about BizTalkServer2010 certification for the Windows Server logo program. It provides you a list of custom actions that might be performed during BizTalkServer Setup operation.Review Installation StepsThe majority of BizTalk

6、Server setup problems occur because the BizTalk Server computer was not properly prepared before BizTalk Server was installed, or a previous installation of BizTalk Server was not fully uninstalled before a new installation was attempted. Review the two checklists below, which you can also find in t

7、he BizTalk Server 2010 Installation Guides, to ensure that your computer（s） are properly configured to support BizTalk Server. If, after reviewing this information, your setup still does not succeed, the troubleshooting tips in the rest of this document may be useful.Preparing your computer for inst

8、allation Install any critical updates for Windows Enable Internet Information Services （IIS） 7.5 or 7.0 Install Microsoft Office Excel 2010 or 2007 Install Visual Studio 2010 Install SQL Server 2008 R2/SP1 Install SQL Server 2005 Notification Services （required only for BAM Alerts） Install prerequis

9、ites for MQSeries Agent （required only for MQSeries Agent） Install .Net Framework 4 and 3.5 SP1 Install SharePointFoundation2010 or Windows SharePoint Services 3.0 SP2Note SharePoint2010 is the new version of Windows SharePoint Services. Configure Windows SharePoint Services* Extend the Default Web

10、Site as a Virtual server* Disable shared Memory Protocol Join the local Administrators group Configure the Application Event Log*Only necessary if you are using the Windows SharePoint Services Adapter Web Service. Installing and configuring BizTalk Server Install BizTalk Server 2010 Verify your inst

11、allation Configure BizTalk Server Enable TCP/IP and named pipes in the SQL Server Configuration Manager Enable Microsoft Distributed Transaction Coordinator （MS DTC） on the Local Host Server （LHS）Some BizTalk EDI/AS2 artifacts are still active after unconfiguringProblemAfter you unconfigure the BizT

12、alk EDI/AS2 feature of BizTalk Server, some BizTalk Server artifacts related to EDI and AS2 processing will still be active in the context of the BizTalk group configuration. These artifacts will include EDI and AS2 pipelines and the batching orchestration. As a result, you will still be able to per

13、form basic EDI and AS2 processing even after unconfiguring the BizTalk EDI/AS2 feature. CauseThere are active ports associated with EDI and AS2 processing. Some artifacts will continue to function while these ports remain active.ResolutionTo disable all EDI/AS2 artifacts, you should disable, stop, o

14、r delete the ports associated with EDI and AS2 processing.If the BizTalk Server Computer or SQL Server computer is renamed after BizTalk Server configuration, the Configuration Wizard will failThis problem may manifest itself in several ways: The configuration manager will load the Overview page cor

15、rectly, 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.The BizTalk Server configuration stores the computer network name. Wh

16、en 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.Do not rename the BizTalk Server computer or the SQL Server computer. If a server mus

17、t be renamed, unconfigure all BizTalk features before renaming the computer. After renaming the computer, reconfigure BizTalk Server features.The BizTalk Server Business Rules Configuration Wizard fails The Business Rules Configuration Wizard fails with the error “Configuration failed for some compo

18、nents and no settings were applied for those components.” On BizTalk Server computers for which the Business Rules Engine has already been successfully configured, the Rules Engine Update service fails to start and cannot be started manually.When this problem occurs, an error similar to the followin

19、g may be generated in the BizTalk Server computer Application log:Service could not be started. : System.Net.Sockets.SocketException （10061）: No connection could be made because the target machine actively refused it :1:3132The Microsoft Malware Protection Center released an updated signature file o

20、n March 9th, 2010 to address a possible threat from SettingsModifier:Win32/PossibleHostsFileHijack. This updated signature file can cause Microsoft Malware Detection software such as Windows Defender to update the local HOSTS file to mitigate threats from SettingsModifier:Win32/PossibleHostsFileHija

21、ck. As a result of these changes, the BizTalk Server Rules Engine Update service may fail to start.Update the local HOSTS file to include the following line:127.0.0.1 localhostThe HOSTS file is located in the %systemroot%driversetc directory.For more information about the Microsoft Malware Protectio

22、n Center signature update that addresses a possible threat from SettingsModifier:Win32/PossibleHostsFileHijack, see Configuration LoggingThe configuration program writes detailed information to a configuration log file which by default is located in the temp directory of the computer running BizTalk

23、 Server. To determine the folder that is specified by the TEMP environment variable open a command prompt on this computer, type the following command, and then press ENTER:echo %TEMP%The configuration log file contains a summary of the configuration steps performed, as well as diagnostic informatio

24、n about any failures that may occur during the configuration process. If a configuration error occurs, open the configuration log in a text editor such as Notepad and check the log file for possible causes of the error.Troubleshooting ToolsUse SQL Server Profiler, Filemon, or Regmon to gather additi

25、onal information about configuration failures. For more information about these tools, see Tools and Utilities to use for Troubleshooting （Configuration fails when BizTalk Server and SQL Server are installed on separate computersConfiguration fails with errors similar to the following when attemptin

26、g to configure the Enterprise Single Sign-On （SSO） component:An error occurred while attempting to access the SSO database. Function: FieldInfoCreate -or-Failed to enable the Single Sign-On （SSO） Service （error code 0X800706BA）If BizTalk Server and SQL Server are installed on different computers, th

27、en the configuration operations are performed under the context of a Microsoft Distributed Transaction Coordinator （MSDTC） transaction and MSDTC functionality must be available over the network between these computers. If MSDTC functionality is not available over the network between the computers running BizTalk Server and SQL Server, then this error can occur.Follow the steps in Troubleshooting Problem