Logins that Fail in Microsoft Dynamics GP

For years there has been a strong push toward using identical DSNs on every workstation at a given site. From a consultant's perspective, this makes life easier. But there is another reason for this consistency as well -- password encryption!

Take for example a scenario where the network and GP install were performed by a team or IT person who is no longer there. The terminal server may have one DSN defined while the SQL server has a different one.
If you create a new user ID using the SQL server based GP client and then switch to the Terminal Server, your password won’t work! Microsoft has increased the password encryption security level. Now, when a
GP password is encrypted, the specs from the DSN are used. This means that differences between the DSNs on workstations can prevent a password from working! To make sure that a password created at one workstation will work at all work stations, make sure that the DSNs are built the same on all workstations.

No comments:

Post a Comment