eConnect errors

Error: Login failed for user 'User name'.
Cause: The user does not have a Windows Authentication Login ID in the SQL Server.
Solution: Create a Windows Authentication Login ID in the SQL Server

Error: Server process could not be started because the configured identity is incorrect. Check the username and password.
Cause: The user has changed the System Password after the eConnect installation.
Solution: Change the eConnect Identity .
1.Go to Start --> Run, type dcomcnfg and click the OK button.
2.In the Component Services window, Expand Component Services > Computers > My Computer > COM+ Applications.
3.Under COM+ Applications, locate eConnect 8 for Great Plains and Right Click it and select Properties.
4.In the Properties window, select the Identity Tab. In that click the This User option button and enter the new Login Credentials for the user and click the Apply button.

Error :The partner transaction manager has disabled its support for remote/network transactions. An error occurred while enlisting in a distributed transaction.
Cause : This error comes up when you are doing inter sever transactions via Distributed Transaction Cordinator MSDTC.
Solution:
In Control Panel > Adminstrative Tools > Component Services > Expand Component Service > Right Click My Computers > Properties > MSTDC Tab > Click on Security Configuration button > Check Network DTC if not checked and Check Allow Inbound, Allow Outbound and select NO AUTHENTICATION REQUIRED

Error:The transaction has already been implicitly or explicitly committed or aborted
Cause:Network security for the particular user.
Solution: Add enlist=false in the connection string. Connection string would be like this;
ConnectionString = @”data source=SERVERNAME;initial catalog=DBNAME;integrated security=SSPI;persist security info=False;packet size=4096;enlist=false”;