Great Plains on Terminal Server ODBC problem

[IsilZha]

We're trying to deploy a Terminal Server with Great Plains 10 and we have an issue - users that log onto a terminal session can only logon as sa - not their own users. Once I noticed this happening, I created a user account for testing purposes and run into all the same problems and other users.

For some strange reason, the only account that works to be able to log on to any GP account through a terminal session is my regular user account, not my admin account - I did not even install anything with this account that works.

Here's several things I've tried so far:

Logging in with the test user to a terminal session and attempting to login to GP with any account other than sa gives me a "login attempt failed" message.

Logging on with my account into a terminal session does allow me to login to all users.

Logging in with my account and doing a Run As... on GP and running it as the test user account also allows me to login with all user accounts.

Logging onto the TS directly (not a terminal session) with the test user account works intermiddenly - sometimes it'll work, sometimes it won't (most of the time it won't.)

Logging onto the TS directly, with my account that also works through terminal sessions, and then doing a runas with the test user account also works.

Making the test user account an administrator on the TS machine doesn't fix the problem.

I used the trace in the ODBC Data Source Administrator to get a log of calls to the ODBC driver and found this message (which I also found through packet capturing of port 1433.)

DIAG [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user '<account name removed>'. (18456)

DIAG [08S01] [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
(10054)

DIAG [08S01] [Microsoft][SQL Native Client]Communication link failure (10054)

 

[jazgeek]

I would start by deleting your odbc connection and re-creating it.

sounds like you might have a file or user dsn instead of a system DSN

-----------
and they wonder why they call it Great Pains!

jaz

 

[klewis10367]

Make sure your odbc connection is set up for SQl Authentication. When you creat the users in Great Plains a sql user is created that accesses the Great Plains data. Make sure when you set up the odbc you do not select a default Database and uncheck all of the default check marks. Also make sure that the users AD account are in the correct Group on the Terminal server.

 

[IsilZha]

I had already tried recreating it and everything - but I found the problem:

I found out that Great Plains does not support mandatory profiles - there are no workarounds except to not use mandatory profiles.

I figured this would be good to know for anyone else that comes across the problem.