|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 883960 - Last Review: August 12, 2004 - Revision: 1.2 How to enable MSDTC communications with Commerce Server 2002 Developer Edition in Windows XP Service Pack 2 (SP2)Important This article contains information that shows you how to help
lower security settings or how to turn off security features on a computer. You
can make these changes to work around a specific problem. Before you make these
changes, we recommend that you evaluate the risks that are associated with
implementing this workaround in your particular environment. If you implement
this workaround, take any appropriate additional steps to help protect your
system. After you install Microsoft Windows XP Service Pack 2 (SP2), any sites that are hosted by Microsoft Commerce Server 2002 Developer Edition and that connect to a Microsoft Windows 2000 Server or a Microsoft Windows Server 2003 Microsoft SQL Server backend may not be
able to perform network Microsoft Distributed Transaction Coordinator (MSDTC) operations. Windows XP SP2 includes Microsoft Windows Firewall, the updated firewall software that replaces Internet Connection Firewall (ICF). If Windows Firewall blocks a port that is used by a service or by a program, you can configure the Windows Firewall to create an exception. For MSDTC to work correctly, you must create an Exception in the Windows Firewall. After you install Windows XP SP2, Commerce Server 2002 sites
that are hosted on Windows XP SP2 and that connect to a Windows 2000 Server or
a Windows Server 2003 SQL Server backend may not be able to perform network
MSDTC operations. You may receive error messages that indicate
problems with MSDTC. For example, you may receive the following error message
during a checkout: New transaction cannot enlist in
specified transaction coordinator.
After
you install Windows XP SP2, take the following actions:
- Turn on Network MSDTC Access.
- Change your Windows Firewall configuration.
Turn on Network MSDTC Access-
Open the Component Services Microsoft Management Console (MMC)
snap-in. To do this, use one of the following methods:
- In Control Panel, open Administrative Tools, and then
double-click Component Services.
- Click Start, click
Run, type
%windir%\System32\Com\Comexp.msc, and then click
OK.
- In the left pane, expand Component Services. If a dialog box appears, click
Unblock.
- Expand Computers, expand My Computer, right-click My Computer, and then click Properties. The My Computer Properties dialog box appears.
- On the MSDTC tab, click Security
Configuration under Transaction Configuration, and
then click to select the Network DTC Access check box.
- Note Only if you are connecting to a Windows 2000 Server from a Windows XP
SP2 computer, click No Authentication Required under
Transaction Manager Communication.
- In the Security Configuration dialog box,
click OK.
- In the MS DTC service will be stopped and
restarted. All dependent services will be stopped. Please press Yes to
proceed dialog box, click Yes.
- In the My Computer Properties dialog box,
click OK two times to return to the Component Services MMC
snap-in.
Change your Windows Firewall configurationWarning This workaround may make your computer or your network more
vulnerable to attack by malicious users or by malicious software such as
viruses. We do not recommend this workaround but are providing this information
so that you can implement this workaround at your own discretion. Use this
workaround at your own risk. Important Every time that you enable an exception for a program or a
service to communicate through Windows Firewall, your computer is made more
vulnerable. We recommend that you only enable an exception when you really need
it, never enable an exception for a program that you do not recognize, and
remove an exception when you no longer need it. To change your Windows
Firewall configuration, follow these steps:
- Log on as an administrator.
- Click Start, click Run,
type Wscui.cpl, and then click
OK.
- In the Windows Security Center window,
click Windows Firewall.
- On the Exceptions tab, click Add
Program.
- In the list of programs, click Browse,
and then locate %WINDIR%\System32\Msdtc.exe.
- Click OK to return to the
Exceptions tab.
- Click Add Port, and then click
Open.
- In the Name box, type a friendly name such as Port
135 for MSDTC.
- In the Port Number box, type
a port number, and then click TCP. For example, the port number could be 135.
- Click OK, and then follow the prompts when
you return to the Firewall Exceptions dialog box. You may have
to restart your computer.
For additional information
about Windows XP Service Pack 2 Firewall, click the following article number to
view the article in the Microsoft Knowledge Base: 875357Â
(http://kbalertz.com/Feedback.aspx?kbNumber=875357/
)
Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
875356Â
(http://kbalertz.com/Feedback.aspx?kbNumber=875356/
)
How to configure the Windows Firewall feature in Windows XP Service Pack 2
APPLIES TO- Microsoft Commerce Server 2002 Developer Edition
- the operating system: Microsoft Windows XP Service Pack 2 (SP2)
| kbinfo kbfirewall KB883960 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
Chris
- chrissmith1998 NOSPAM-AT-NOSPAM yahoo.com
|
Reported as Irrelevant
|
| Written:
2/1/2005 3:15 PM |
|
|
|
 |
 |
 |
 |
 |
 |
 |
| |