Cannot log into Microsoft Dynamics GP 10 (one user and any new user) due to ODBC DSN
Posted on 2010-11-11
After a day of troubleshooting why (1) user (plus any newly created users) could not log into GP, we finally have a workaround.
Unfortunately, we don't have a solution or explanation as to what's happening.
Received a call from 'UserA' that they could not log into GP this morning. Checked logs and saw this:
Login failed for user ‘UserA'. Reason: Failed to open the explicitly specified database.
Error: 18456, Severity: 14, State:38
Turning on SQL logging in the dex.ini file, we find that it's opening a company database, by default, of a company she does not nor should have access to.
We cannot figure out why it's opening up to database 'compabc' when it is supposed to default either to 'master' or 'DYNAMICS'.
We checked the ODBC connections, and nothing was explicitly set there. Furthermore, this happens from any computer in the domain for this username, or for any username we newly create (all other older users work fine).
We use Dynamics GP as the DSN on all workstations; we found that we could go to a workstation and change the DSN to DynamicsGP (no space) and 'UserA' could login to GP just fine and we confirmed she was accessing the default database of DYNAMICS,
What is going on here? Somehow the Dynamics GP DSN for the Native Client connector is tied to the wrong default database for this user and all new users, but none of the other older users (some of which also explicitly do not have access to 'compabc' database, but are just fine).
Any ideas on what's going on?