Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How to implement Microsoft Distributed Transaction Coordinator with eConnect for Microsoft Dynamics GP


INTRODUCTION

This article describes how to implement Microsoft Distributed Transaction Coordinator (MS DTC) for eConnect for Microsoft Dynamics GP.

MORE INFORMATION

Follow these steps on a computer that is running Microsoft Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack (SP1):
1. Make sure that the eConnect object is running under a specific account:
a. Click Start , click Control Panel , click Administrative Tools , and then click Component Services .
b. Expand Component Services , expand Computers , expand My Computer , and then expand COM+ Applications .
c. Right-click eConnect 8 for Great Plains , and then click Properties .
d. Click the Identity tab.
e. In the Account list, click This User .
f.

Specify a Windows user account that has the following characteristics:

• The user account has access to the computer that is running Microsoft SQL Server.
• The user account has been added to SQL logins.
• The user account has at least DYNGRP permissions.



     


Note This user account must be at least a local administrator. Make sure that you specify a user account where the administrator is the only person who knows the logon information. This approach lets users start the eConnect methods, but the users cannot use the account to gain access to all the Microsoft Dynamics GP tables.
2. The DTC Service must use the NT AUTHORITY\NetworkService account, and the Network DTC Access check box must be selected. To make sure that the DTC service uses this account, follow these steps:
a. Click Start , click Control Panel , click Administrative Tools , and then click Component Services .
b. Expand Component Services , and then expand Computers .
c. Right-click My Computer , and then click Properties .
d. Click the MSDTC tab, and then click Security Configuration .
e.

Make sure that the following check boxes are selected:

Network DTC Access
Allow Remote Clients
Allow Remote Administration
Allow Inbound
Allow Outbound
No Authentication Required



     
f. Make sure that the DTC Logon Account is set to NT AUTHORITY\NetworkService.
3. Add MSDTC.exe as an exception in Windows Firewall.
For all these changes to take effect, you must restart MS DTC and SQL Server.

↑ Back to the top


Keywords: kb, kbhowto, kbinfo, kbMBSPartner, kbMBSMigrate, BemisKB907668

↑ Back to the top

Article Info
Article ID : 907668
Revision : 1
Created on : 3/7/2017
Published on : 3/7/2017
Exists online : False
Views : 90