Biztalk2010安装及配置问题集

在安装Biztalk2010时，碰到很多问题，有的是粗心有的也是比较bt的，如：

1）在win7 64下引入x86 的cab，有点粗心，幸亏给我报错版本不兼容（呵呵）；

2）安装的时候不知道为什么计数器被损坏 bam计数器无法注册，这个耗时好长，通过查询才发现使用 lodctr /r’重建计数器设置，然后再安装就ok了

3）配置的时候，sql server sp1 一定要安装

如下是我查询到的安装介绍，蛮好的，分享给大家（msdn上的ftp下载的）

Readme for BizTalk Server 2010

Welcome to the Microsoft BizTalk Server 2010 Readme. This document contains information about BizTalk Server installation and known issues in BizTalk Server 2010.

To view the most recent Readme for Microsoft® BizTalk® Server 2010, see <?XML:NAMESPACE PREFIX = [default] http://ddue.schemas.microsoft.com/authoring/2003/5 NS = "http://ddue.schemas.microsoft.com/authoring/2003/5" />http://go.microsoft.com/fwlink/?LinkID=183138.

Install BizTalk Server 2010

For software requirements, preparing your computer for installation, and installing and configuring BizTalk Server 2010 instructions, see the BizTalk Server 2010 Installation Guides.

Microsoft BizTalk Server 2010, Microsoft UDDI Services and Microsoft BizTalk RFID are logo certified for Windows Server 2008 R2. Microsoft BizTalk Adapters and AppFabric Connect are not logo certified for Windows Server 2008 R2.

What’s New in BizTalk Server 2010?

The following features are introduced in BizTalk Server 2010.

AppFabric Connect

BizTalk Server 2010 introduces a new feature “AppFabric Connect”, which combines rich proven features of BizTalk Server and the flexible development experience of .NET to allow users to easily develop simple integration applications. This enables users to:

Develop custom .NET applications that require connectivity to backend Line of Business (LOB) systems like SAP, Oracle database, Oracle E-Business Suite, Seibel, and SQL Server without writing custom code for LOB connectivity.
Develop XML-based data transformation using the easy-to-use and rich user interface of BizTalk Mapper that can be launched and used right within a .NET project.

AppFabric Connect uses Windows Workflow Foundation (WF) activities to programmatically access BizTalk’s LOB connectivity and data transformation capabilities. This enables users to easily create new composite applications using the WF model, which can be deployed, hosted, managed in Windows Server AppFabric. AppFabric Connect also enables a class of scenarios (such as Web-based queries) that are best effort, short running and don’t require the durability/persistence provided by the traditional BizTalk Server message box architecture. For more information on how to use AppFabric Connect, see http://go.microsoft.com/fwlink/?LinkID=190331.

BizTalk Server Settings Dashboard

The BizTalk Settings Dashboard in BizTalk Server 2010 collates all the performance settings and provides a central console to manage them. For more information about how to use Settings Dashboard for performance optimization, see the Managing BizTalk Server Performance Settings section in the BizTalk Server 2010 Help.

Improved Management Pack

System Center Operations Manager (SCOM) provides capabilities that can improve the manageability of Microsoft products through centralized and proactive availability and health monitoring. The BizTalk Server Management Pack for Operations Manager provides comprehensive discovery and monitoring of BizTalk Server components and applications. With BizTalk Server 2010, the following enhancements are introduced in BizTalk Server management pack:

Separate views for enterprise IT administrators and BizTalk administrators
Optimized discovery of artifacts across multiple computers
Optimized discovery of relationships between artifacts
Visual representation of health status
Diagnostic support
Other performance enhancements

FTP Adapter Enhancements

The BizTalk FTP adapter exchanges data between BizTalk Server and an FTP server and enables integration of data stored on varied platforms with different line-of-business applications. With BizTalk Server 2010, the FTP adapter is enhanced to provide the following feature additions:

Support for transferring data to and from a secure FTP server
Support for downloading file from locations marked as read-only
Support for atomic file transfer in ASCII mode

Enhanced Trading Partner Management

While BizTalk Server 2010 continues to provide support for EDI and AS2, it rebuilds the fundamental concepts around how to manage and store information about partners and their business. EDI standards, AS2 messaging, and the new concepts put together form the building blocks of a B2B communication or a Trading Partner Management (TPM) solution. For more information about the enhancements to the Trading Partner Management feature in BizTalk Server 2010, see the Building Blocks of a Trading Partner Management Solution section in BizTalk Server 2010 Help.

Enhanced Support for HIPAA documents

BizTalk Server 2010 provides enhanced support for HIPAA. For more information about the enhanced HIPAA support in BizTalk Server 2010, see the HIPAA Document Schema Version 5010 section in BizTalk Server 2010 Help.

Enhanced BizTalk Mapper

BizTalk Server 2010 builds on the Mapper feature to provide a enhanced user experience. For more information about the enhancements to the BizTalk mapper feature in BizTalk Server 2010, see the Enhancements to BizTalk Mapper section in BizTalk Server 2010 Help.

Support for .NET Framework 4

BizTalk Server 2010 supports building new applications only on .NET Framework version 4. You can build both BizTalk applications as well as custom applications (such as custom functoids, custom pipeline components) using .NET Framework 4. However, BizTalk Server 2010 continues to support the BizTalk Server 2006 R2 and BizTalk Server 2009 applications (BizTalk applications and custom applications) built on .NET Framework 3.5 SP2. For more information about how BizTalk Server 2010 supports .NET Framework 4, see the Updated .NET Framework Support section in BizTalk Server 2010 Help.

SQL Server Backup Compression in BizTalk Server

SQL Server backup compression is a new feature that is introduced in SQL Server 2008 Enterprise edition. In BizTalk Server 2010, backup compression enables you to create compressed backups of BizTalk Server databases that are business critical and consume large amounts of disk space.

For more information on how BizTalk Server 2010 uses this new feature, see the topic New Features in BizTalk Server 2010 in the BizTalk Server 2010 Help.

SQL Server Transparent Data Encryption (TDE) in BizTalk Server

Transparent data encryption (TDE) is a new encryption feature introduced in Microsoft® SQL Server® 2008. It provides protection for the entire database “at rest”, meaning the data and log files without affecting existing applications.

In BizTalk Server 2010, the transparent data encryption (TDE) feature of SQL Server can be used to protect data that contains confidential and sensitive information such as customer orders with credit card information in messages. For more information, see the topic New Features in BizTalk Server 2010 in the BizTalk Server 2010 Help.

Customer Experience Improvement Program (CEIP) in BizTalk Server

Microsoft introduces the Customer Experience Improvement Program (CEIP) in BizTalk Server 2010. As part of this support, you are automatically opted-in to provide useful feedback to Microsoft regarding your usage of BizTalk Server. The data collected from you is anonymous and cannot be used to identify you. Microsoft collects feature usage statistics as part of this program. By participating in this program, you can help improve the reliability and performance of various features of

BizTalk Server. For more information about this program and its privacy policy, see Microsoft BizTalk Server CEIP Privacy Policy (http://go.microsoft.com/fwlink/?LinkID=188553).

Updated Platform Support

BizTalk Server 2010 includes support for the following software versions:

Windows Server 2008 R2
Windows Server 2008 SP2
Windows 7
Windows Vista SP2
SQL Server 2008 SP1
SQL Server 2008 R2
Visual Studio 2010
Microsoft Office 2007
Microsoft Office 2010

BizTalk Server 2010 also supports upgrade from BizTalk Server 2006 R2 and BizTalk Server 2009. For more information, see http://go.microsoft.com/fwlink/?LinkID=183138

Supported Languages

BizTalk Server 2010 includes support for the following languages:

English (EN)
Chinese (CN)
German (DE)
Spanish (ES)
French (FR)
Italian (IT)
Japanese (JA)
Korean (KO)
Tiwanese (TW)

Known Issues

The following are the known issues in BizTalk Server 2010.

Known Issues with Setup and Configuration

BizTalk Server installation may not launch automatically after a system restart
If .NET Framework 4 is not installed, the BizTalk Server setup installs .NET Framework 4 and then restarts the computer. After rebooting, the BizTalk Server setup may not start automatically. In such cases, you must manually start the BizTalk Server installation.
Running BizTalk Server 2010 Setup after installation causes error
On a BizTalk Server 2010 Standard/Developer/Branch edition, after you install and configure UDDI services, if you try to repair BizTalk Server 2010 by running the BizTalk Server 2010 setup from the product DVD, you may receive the following error:
Setup has detected that the Enterprise Edition of BizTalk Server 2010 was installed. Upgrading from the Enterprise Edition to the Standard Edition is not supported. Please uninstall the Enterprise Edition and then run the setup again.
Workaround:
1. Open the Control Panel, and then double-click Program and Features.
2. In the Program and Features dialog box, double-click the Microsoft BizTalk Server 2010 entry.
3. Click Repair.
Default settings have changed for ‘Maximum Worker Threads’ and ‘Maximum IO Threads’ from BizTalk Server 2009
In BizTalk Sever 2009, the default value for Maximum Worker Threads and Maximum IO Threads is the same as the .NET default values, but, in BizTalk Server 2010, the default value for the threads is lower than the values in the .NET default, this may result in performance degradation in certain scenarios. For example, the scenarios which have multiple running orchestrations.
Workaround: You need to change/increase the values for Maximum Worker Threads and Maximum IO Threads at the Host instance level in BizTalk Server Settings Dashboard.
Reinstalling Visual Studio 2010 in a computer which already has Microsoft BizTalk Server 2010 configured causes an error
You may encounter an error "Error 5009. Registration of BAM performance counters failed. Return code -1." after you reinstall Visual Studio 2010 on a computer which already has BizTalk Server 2010 configured. This error occurs because the performance registry counters are damaged and needs to be rebuilt.
Workaround: You need to rebuild the performance registry counters by using the command ‘lodctr /r’. For more information, see Lodctr.
Corrupted BizTalk Server 2010 installation may leave stale registry information which causes an error when you try to re-install BizTalk Server 2010
On trying to re-install BizTalk Server 2010, you may receive an error "Another version is already installed", but BizTalk Server 2010 is not installed in the computer nor is it a part of the list of installed programs. This error comes up if previous uninstallation/installation of BizTalk Server 2010 got corrupted and left stale registry information.
Workaround: You need to run ‘msizap’ which cleans up the corrupt entries and allows you to install a clean version of BizTalk Server 2010. For more information, see msizap.
BizTalk Server Group Configuration does not add the read/write permissions to ‘\WINDOWS\TEMP’ folder
When configuring Groups in BizTalk Server Configuration wizard, the read/write permissions are not added to \WINDOWS\TEMP folder. This causes the following error when trying to deploy a schema:
"Attempt to deploy the schema for Microsoft.BizTalk.DefaultPipelines.PassThruReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 failed during call to .NET Framework method. This might be due to lack of permission to generate temporary Xml serializer assembly. Ensure that \WINDOWS\TEMP folder has the write permission for NETWORK SERVICE account set."
Workaround: You need to manually add read/write permissions to \WINDOWS\TEMP folder.
SQL Server Browser Service is required when BizTalk Server is using a named instance of SQL Server
SQL Server Browser Service is not required in the following cases:
- Microsoft BizTalk Server is using the default instance of SQL Server with TCP/IP running on port 1433.
- User has full identification information (port number and named pipe) to connect to SQL Server.
For more information on SQL Server Browser Service, see http://go.microsoft.com/fwlink/?LinkID=199971.
BizTalk TDDS (Tracking Data Decode Service) fails to copy data from Message Box to DTA database on Turkish builds of Microsoft SQL Server
Workaround: After BizTalk Server 2010 configuration, database collation of all BizTalk Server databases should be changed to Latin1_General_CS_AS, Latin1_General_Bin, or Latin1_General_Bin2. Run the following commands to change the database collation:
```
alter database <Database name> set single_user with rollback immediate

alter database <Database name> collate Latin1_General_BIN

alter database <Database name> set multi_user
```
Immediately after BizTalk Server 2010 installation, if you try to create a BizTalk Server project, or try to add certain BizTalk Server artifacts, some templates may not appear
You encounter this because the installation of Visual Studio templates is still running and is yet to complete.
Workaround: You need to close all the instances of Visual Studio, and then wait till all the instances of devenv.exe process has completed. You can monitor running processes in the Task Manager. After completion of devenv.exe, if the templates still do not appear then you need to open Visual Studio command prompt (2010) as ‘Run as Administrator’, and then run the command devenv /InstallVSTemplatesto ensure that all the templates are installed.
BizTalk Server 2010 Korean build installation may cause an error due to performance registry
You may get an error "Error 5009. Registration of BAM performance counters failed. Return code -1." during BizTalk Server 2010 Korean build installation because the performance registry counters are damaged and needs to be rebuilt.
Workaround: You need to rebuild the performance registry counters by using the command ‘lodctr /r’. For more information, see Lodctr. After rebuilding performance registry, you should be able to reinstall BizTalk Server 2010.

Known Issues with BAM Portal configuration

You can't access the BAM Portal
You will not be able to access the BAM Portal unless you do both of the following:
- Upgrade your 64-bit computer from Windows XP/Windows Server 2003 to one of the following: Windows 7, Windows Vista SP2, Windows Server 2008 R2, Windows Server 2008 SP2 .
- Upgrade to BizTalk Server 2010 from BizTalk Server 2009, BizTalk Server 2006 R2 SP1, or BizTalk Server 2006 R2.
Workaround: The workaround for this is documented in Upgrading to BizTalk Server 2010 from BizTalk Server 2009/2006 R2 guide. For more information, see http://go.microsoft.com/fwlink/?LinkID=183138.
When upgrading from BizTalk Server 2009/2006 R2 to BizTalk Server 2010, BAM Portal entry is listed under the Microsoft BizTalk Server 2009 or Microsoft BizTalk Server 2006 folder in program menu instead of Microsoft BizTalk Server 2010 folder.
Note

The issue applies only to non-English builds.

Known Issues with Migration

Migration of a project from Visual Studio 2005 to Visual Studio 2010 fails if the project does not have the solution file
Workaround: Ensure that the .sln and .btproj files are present in the BizTalk project during migration.
BAM migration from BizTalk Server 2009/2006 R2 to BizTalk Server 2010 might fail if there are active handles to the BAMAlerts service
Workaround: Before starting the BAM migration process, ensure that all the active handles (ex: service explorer window) are closed.

Known Issues with UDDI

Users cannot access the UDDI portal if the ‘Application Pools’ setting points to .NET Framework 4
Workaround: Ensure that the Application Pool Default settings points to.NET Framework 2.0 before configuring UDDI. The steps to change the Application Pool Default Settings in Internet Information Service (IIS) are:
1. Open IIS Manager on the computer where UDDI needs to be configured:
  1. Click Start > Run.
  2. Type inetmgr to open IIS Manager, and then click OK.
2. In the Connections pane of IIS Manager, expand <Computer Name> node, and then click Application Pools.
3. In the Actions pane, click Set application pool defaults.
4. In the General section, ensure that the .NET Framework version is set to 2.0, and then click OK.

Known Issues with TPM

The following are the known issues in TPM:

When viewing agreements in the BizTalk Server Administration console, you get an error
Users get the following error when viewing agreements and protocol settings through the BizTalk Server Administration console when SSO is not configured on the computer:
Could not contact the SSO server 'MM2009X86SSO'. Check that SSO is configured and that the SSO service is running on that server.
Workaround: Install and configure SSO on every computer running the BizTalk Server Administration console.
Overridden EDI headers of ID type are not validated against the enumeration, only length validation is performed

Known Issues with Orchestration

When redeploying an existing Orchestration solution, you do not receive a warning message
You do not receive a warning message when referring to an older assembly from GAC; also, there is no way to figure out if you are getting an old assembly instead of a new assembly.
Workaround: Before doing redeployment from Visual Studio, terminate BizTalk management console (mmc.exe), and then make sure you have checked the RestartHostInstance checkbox in BizTalk Server project deployment tab.
When Add Web reference in Design Tools does not show port type in BizTalk Orchestration Designer
The unexpected behavior in BizTalk Design tools is due to a known limitation of Visual Studio 2010.
Workaround: You need to install QFE patch for Visual Studio 2010 to fix this issue.

Known Issues with Developer Tools

Known issue with import of older binding files with EDI party migration
Importing older binding files for BizTalk Server applications that include EDI party data is not blocked. We recommend that you do not import bindings to migrate EDI party data from BizTalk Server 2006 R2 or BizTalk Server 2009 to BizTalk Server 2010.
TIP: Use the party migration tool for all EDI party migrations.
Assemblies having Unit testing enabled should not be deployed in both the production and testing environment
Microsoft Windows Server 2000 does not support Party Migration Tool
Workaround: You need to install Microsoft Windows Vista, and then install BizTalk Server Administration console to run the Party Migration Tool.
On adding an existing BizTalk Pipeline file to a BizTalk project, if the build fails due to some errors in the BizTalk Pipeline file then you need to do the following:
- Add all the desired assemblies from %BTSINSTALLPATH%Pipeline components to the project references.
- If the BizTalk project has Custom Component(s), then you need to add all the relevant assemblies and projects to the project references. For more information on Developing Custom Pipeline Component, see http://go.microsoft.com/fwlink/?LinkID=200466.

Known Issues with RosettaNet Accelerator

Errors related to BTARNHttpReceivePool application pool. You might encounter the following warnings when working with the Microsoft BizTalk 2010 Accelerator for RosettaNet:
- The identity of application pool BTARNHttpReceivePool is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request.
- Application pool BTARNHttpReceivePool has been disabled. Windows Process Activation Service (WAS) did not create a worker process to serve the application pool because the application pool identity is invalid.
- Application pool BTARNHttpReceivePool has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.
If you encounter similar warnings, you must set the correct password for 'BTARNHttpReceivePool' application pool in IIS.
On Configuring/Unconfiguring Microsoft BizTalk 2010 Accelerator for RosettaNet, you may receive an error on closing configuration/unconfiguration completion window
The error window which comes up on closing the configuration/unconfiguration completion window has no functional impact and can be ignored.

Known Issues with SWIFT Accelerator

You may see an unexpected event error (Event ID: 1040) during the installation of Microsoft BizTalk Accelerator for SWIFT
Workaround: You need to unconfigure and then reconfigure Microsoft Biztalk Accelerator for SWIFT.
Microsoft BizTalk Accelerator for SWIFT 2010 Message Pack configuration does not start automatically after the installation and configuration of Microsoft BizTalk Accelerator for SWIFT
As part of BizTalk Accelerator for SWIFT installation, BizTalk Accelerator for SWIFT 2010 Message Pack gets installed as a pre-requisite. After BizTalk Accelerator for SWIFT installation, its Configuration User interface is launched automatically, but there is no intimation given to the users to configure BizTalk Accerlerator for SWIFT 2010 Message Pack. As a result, warning messages may be reported in the event log and message processes may fail.
Workaround: You need to manually configure Microsoft BizTalk Accelerator for SWIFT 2010 Message pack after installing and configuring Microsoft BizTalk Accelerator for SWIFT. It should be done from Start> All Programs> Microsoft BizTalk Accelerator for SWIFT 2010 Message Pack > BizTalk Accelerator for MessagePack Configuration.

Known Issues with WCF LOB Adapter SDK

You might encounter the following issues when working with the BizTalk Adapter Pack:
- An error for unrecognized element is shown when you try to open the AppFabric Endpoint Management tool or IIS Config Editor in IIS Manager for a service that uses BizTalk Adapter Pack.
  Workaround: apply the hotfix given in http://support.microsoft.com/kb/980423
- On a 64-bit computer on which both 64-bit and 32-bit versions of BizTalk Adapter Pack is installed, uninstallation of one will lead to configuration properties not showing up on IIS Config Editor.
  Workaround: Run the setup again and repair the installation.
Known Issues with Mapper Activity
- You might encounter the following error message when building a workflow project with mapper activity:
  The referenced assembly "Microsoft.ServiceModel.Channels.MapperActivity" could not be resolved because it has a dependency on "System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is not in the currently targeted framework ".NETFramework,Version=v4.0,Profile=Client".
  Workaround: Change/retarget the project to .NET Framework 4. For more information, see How to: Target a Specific .NET Framework Version or Profile
- Maps defined in a referenced assembly or a referenced project cannot be edited or opened from the associated Mapper activity.
  Workaround: Open the project containing the map and edit the map. You are required to rebuild the project once you update the map.

Known Issues with Runtime

BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart.
Workaround: You can use either of the following to start the BizTalk Server Application Service:
- Manually start the BizTalk Service BizTalk Group : BizTalkServerApplication Service from Services.msc.
- In Services.msc, set the Startup type for Enterprise Single Sign-On Service and BizTalk Service BizTalk Group : BizTalkServerApplication service to Automatic (Delayed Start).
BizTalk Server Application Service (BTSNTSvc.exe) fails when you try to manually start or stop it. You will see the event error Event ID: 1053.
Workaround: Ensure that the credentials for SQL Server service are correct. You should be able to restart SQL Server service and BizTalk Server Application Service (BTSNTSvc.exe) successfully.

Known Issues with Documentation

In some cases, accessing the BizTalk Server 2010 context-sensitive help may either show an incorrect topic or result in an error. For example, accessing the context sensitive help from the BizTalk Server Configuration user interface does not show the desired topic.
Workaround: Access the latest BizTalk Server 2010 documentation from Start> All Programs> Microsoft BizTalk Server 2010> BizTalk Server Documentation.
Updated UDDI documentation shipped with BizTalk Server 2010 is included in the UDDI.chm which can be found in %installdir%\Microsoft UDDI Services\config\documentation.
For the individual adapters that are part of Microsoft BizTalk Adapters for Enterprise Applications, the documentation that gets installed with the product under <installation drive>\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\<Adapter name>\Documentation is not updated. For the updated documentation, see the documentation for the adapters included in the BizTalk Server helphttp://go.microsoft.com/fwlink/?LinkID=200189.
On executing the command unpack.exe from C:\Program Files (x86)\Microsoft BizTalk Server 2010\SDK\Tutorial, you may receive a message Tutorial files are now unpacked to C:\tutorial, but, there is no tutorial folder created in the installation drive.
Workaround: You can download the tutorials from http://go.microsoft.com/fwlink/?LinkID=200293, and then place it in the location C:\tutorial.
Localized documentation for Microsoft BizTalk 2010 Accelerator for RosettaNet does not get installed with the product
Workaround: You can download the localized documentation from http://go.microsoft.com/fwlink/?LinkId=200955.

Interop binaries

The files in the list below are interop binaries packaged with BizTalk Server 2010, and by design, do not contain valid file information like Product version and Copyright.

C:\Program Files (x86)\Microsoft BizTalk Server 2010\InterOp.ActiveDS.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Interop.WUApiLib.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Interop.XceedFtpLib.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Microsoft.BizTalk.Adapter.MQS.Agent.Interop.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Microsoft.Biztalk.Interop.Agent.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Microsoft.BizTalk.Interop.TransportProxy.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Microsoft.BizTalk.KwTpm.StsOmInterop3.exe
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Microsoft.BizTalk.KwTpm.StsOmInterop4.exe
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\interop\Microsoft.BizTalk.Interop.DTS.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\interop\Microsoft.BizTalk.Interop.Excel.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\interop\Microsoft.BizTalk.Interop.MSOLAPADMINLib2.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\interop\Microsoft.BizTalk.Interop.VBA.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\interop\VBIDE.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\Microsoft.BizTalk.Interop.DSO.dll
C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking\Microsoft.BizTalk.Interop.POMInterfaces.dll
C:\Program Files (x86)\Microsoft UDDI Services\config\Interop.ActiveDS.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\Interop1.1\Microsoft.BizTalk.Interop.SSOClient.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\Microsoft.BizTalk.Interop.SSOClient.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\Microsoft.EnterpriseSingleSignOn.Interop.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\SDK\Bin\Interop1.1\Microsoft.BizTalk.Interop.SSOClient.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\SDK\Bin\Microsoft.BizTalk.Interop.SSOClient.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\SDK\Bin\Microsoft.EnterpriseSingleSignOn.Interop.dll
C:\Program Files\Common Files\Enterprise Single Sign-On\Win32\InterOp.ActiveDS.dll
C:\Program Files\Microsoft BizTalk RFID\BREConfiguration\InterOp.ActiveDS.dll
C:\Program Files\Microsoft BizTalk RFID\BREConfiguration\Interop.WUApiLib.dll

Copyright

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Microsoft, Active Directory, ActiveX, BizTalk, Excel, InfoPath, JScript, IntelliSense, Internet Explorer, MSDN, Outlook, PivotChart, PivotTable, PowerPoint, SharePoint, Tahoma, Visio, Visual Basic, Visual C++, Visual C#, Visual SourceSafe, Visual Studio, Win32, Windows, Windows NT, Windows PowerShell, Windows Server, Windows Server System, and Windows Vista are trademarks of the Microsoft group of companies.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

All other trademarks are property of their respective owners.