eConnect Connection Error
DavidM
when installed on the users PCs. Seems a simple enough issue, but I am
getting a onday morning block. What do I need to set up in SQL, or on the
user's PC, to get these programs to run?
Error:
--> System.Data.SqlClient.SqlException: Loging failed for user''. The user
is not
associated with a trusted SQL Server connection.
SQL is set for Mixed-Mode security. The connection string is
sConnectionString = "data source=" & vSQLServer & ";initial catalog=" &
GPCompany & ";integrated
security=SSPI;persist security
info=False;packet size=4096"
The call that is failing, for the users, is
eConCall.eConnect_EntryPoint(sConnectionString,
Microsoft.GreatPlains.eConnect.EnumTypes.ConnectionStringType.SqlClient,
MiscLogDocument,
Microsoft.GreatPlains.eConnect.EnumTypes.SchemaValidationType.None)
when uploading the XML document.
zman
Server account.
--
Lorren
Consulting Technology Lead
WennSoft Inc.
The views or opinions expressed in this post are mine and not those of
WennSoft.
Keith
You may also need to check and see that DTC is setup correctly on the
server and the client machine. Here are some steps to do this.
This error occurs if Microsoft Distributed Transaction Coordinator (MS DTC)
is disabled for network transactions.
Resolution Section
To resolve this issue, 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 box, 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 Great Plains 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.
Jan Smith (MSFT)
Checking in to see if there is anything else we can do for you on this
topic.
Please post again at your convenience and we will be here for you.
Have a great week!
Jan Smith
Microsoft Online Support Engineer
Get Secure! - www.microsoft.com/security
==============================================
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Jan Smith (MSFT)
Anything else we can do for you here on this query?
Please post back at your convenience and we will be here for you.
Thanks again for using the partner newsgroups!
Paul
I am also getting the same kind of error
I am using econnect 9 on windows 2000 professional system
On integrating data from client machine to SQL server on a different machine
with integrated security, system throws a message "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection."
We have workstation based network, not domain users , whether it can be the
reason for the error
Please give me a solution for this
Thanks in advance
Paul
Keith
You will also need to go through the DTC settings on the server and client
machine.
Paul
I am using windows 2000 professional , in MSDTC setting i didn't see any
security configuration and not able to set log on account to NT
AUTHORITY\NetworkService
Can you please tell how can i set it .
Thanks
Bibi
Kevin Johnson[MSFT]
You mentioned that you are in a workgroup environment rather than a domain.
In this setup, SQL server can only authenticate local accounts on the SQL
box and will have problems with calls from a remote machine.
However, a workaround that I have heard of is to create identical user
accounts (exact same username and password) on both the client and SQL
server machines. Then configure the eConnect COM+ application on the client
to use this account on the identity tab. Then go to the SQL server and give
this account a windows login and put it into the DYNGRP role of DYNAMICS
and company databases.
Each machine is still using a local account for everything, but in a
workgroup environment like this, DTC passes the user credentials as-is
(plain text I believe) over to the SQL server which will authenticate it
since it has an identical local user account with those credentials and
you've given this account the proper permissions in SQL.
Best Regards,
Kevin Johnson - GP Developer Support
Michelle Brayton
Kevin,
Does this work with econnect 10.0? I have a client on a workgroup setting
and needs econnect on client machines. They did setup a domain on the server
to install econnect but the clients are not part of the domain. Will adding
the econnect user as a local user allow for econnect to be installed and
connect to the client. Also, is this method of install supported by
Microsoft?