Setup MSDTC Network Access
FineBuild can configure MSDTC network access.
If it is required for SQL Server to perform two-phase commit operations with processes that run on a different logical server, then MSDTC network access must be enabled.
For many installations it is not necessary to enable MSDTC network access. However, if MSDTC is being clustered then MSDTC network access must be enabled.
FineBuild MSDTC Network Access configuration
The MSDTC Network Access configuration relates to Process Id
2AC and is controlled by the parameters below:
| Parameter | Build | SQL 2005 | SQL 2008 | SQL 2008 R2 | SQL 2012 |
|---|
| SetupDTCNetAccess | FULL | Yes | Yes | Yes | Yes |
| SetupDTCNetAccess | WORKSTATION | Yes | Yes | Yes | Yes |
| SetupDTCNetAccess | CLIENT | N/A | N/A | N/A | N/A |
The MSDTC Network Access processing will always be performed if the
/SetupDTCCluster parameter is set to
YES.
Top
Manual MSDTC Network Access configuration
The following steps show what you would have to do for manual MSDTC Network Access configuration. FineBuild does all of this work for you automatically.
1) Start Component Services manager (Click Start, then Run, and type
comexp.msc). Navigate to
My Computer then right-click and select
Properties.
2) On the MSDTC tab, click on
Security Configuration.
3) Set the following options, then click
OK to continue.
For details of why this is done see KB817064.
| Network DTC Access | Checked |
| Allow Inbound | Checked |
| Allow Outbound | Checked |
| Mutual Authentication Required | Select only if you are not installing a MSDTC cluster |
| Incoming Caller Authentication Required | Select only if you are installing a MSDTC cluster |
4) Click
Yes to continue.
5) Click
OK to continue, then click
OK to close the
My Computer Properties window.
Copyright © 2012 Edward Vassie.
License and Acknowledgements