DataBase - GP 9.0 User Login Failed

Asked By Janakiram on 15-Oct-08 01:52 AM
Hi

I've encountered a strange situation in GP9.0. This client is using
workgroup environment. When GP is installed on server and Clients are
connected to server. User accounts have been created. However, when we
try to login as a User in a different machine apart from the computer
where the User is originally created, the login will fail. But, "sa"
login works perfectly on all machines.

What I then did is delete the User login ID, create a User in his own
PC, then it works. If I try creating a User DSN for the same user for
the machine, it fails except for "sa" login.

Do anyone have any thoughts on why the User DSN fails in this case?

Thanks

Janakiram

+973 39475299


MarianoGome replied on 12-Oct-08 06:41 PM
Are you authenticating the User DSN with sa? If so, are you able to connect
to the server with sa (from the DSN)?

Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com
calle replied on 12-Oct-08 06:41 PM
I always create system DSNs. MS recommends users be part of the local admin
group on their machines.

Make sure you're using TCP/IP as the protocol with name resolution provided
by a server or host files.


--
Charles Allen, MVP
dmusgra replied on 13-Oct-08 04:19 AM
------=_NextPart_0001_13317546
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

You might find my blog post on password encryption useful as it explains why passwords can fail to work.

http://blogs.msdn.com/developingfordynamicsgp/archive/2008/10/02/why-does-microsoft-dynamics-gp-encrypt-passwords.aspx

David Musgrave [MSFT]
Escalation Engineer - Microsoft Dynamics GP
Microsoft Dynamics Support - Asia Pacific

Microsoft Dynamics (formerly Microsoft Business Solutions)
http://www.microsoft.com/Dynamics

mailto:David.Musgrave@online.microsoft.com
http://blogs.msdn.com/DevelopingForDynamicsGP

Any views contained within are my personal views and not necessarily Microsoft policy.
This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_13317546
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang3081{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 You might find my blog post on password encryption useful as it explains why passwords can fail to work.
\par
\par http://blogs.msdn.com/developingfordynamicsgp/archive/2008/10/02/why-does-microsoft-dynamics-gp-encrypt-passwords.aspx
\par
\par David Musgrave [MSFT]
\par Escalation Engineer - Microsoft Dynamics GP
\par Microsoft Dynamics Support - Asia Pacific
\par
\par Microsoft Dynamics (formerly Microsoft Business Solutions)
\par http://www.microsoft.com/Dynamics
\par
\par mailto:David.Musgrave@online.microsoft.com
\par http://blogs.msdn.com/DevelopingForDynamicsGP
\par
\par Any views contained within are my personal views and not necessarily Microsoft policy.
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_13317546--
Janakiram replied on 15-Oct-08 01:52 AM
Just to update on this - If I try creating User DSN, it fails to
authenticate possibly because the users are not part of local admin
group. What I did is create System DSN with "sa" authentication and
then login to GP as sa, then create User ID in the same machine where
the User will be working.

Thanks

Janakiram

On Oct 13, 11:19=A0am, dmusg...@messengeruser.com (David Musgrave
why passwords can fail to work.
osoft.com/Dynamics
gForDynamicsGP
osoft policy.
s. =A0
Japheth Nolt replied on 13-Oct-08 10:58 AM
In your ODBC Data Source Administrator, click on the Configure button to
configure your Data Source.  Make sure that the value in the Server field is
the same on all workstations.  Reset your user's passwords.  You should then
be able to login from any workstation with any user id.

--
Japheth Nolt
Microsoft SBF Specialist
Landis Computer
www.landiscomputer.com


Just to update on this - If I try creating User DSN, it fails to
authenticate possibly because the users are not part of local admin
group. What I did is create System DSN with "sa" authentication and
then login to GP as sa, then create User ID in the same machine where
the User will be working.

Thanks

Janakiram

On Oct 13, 11:19 am, dmusg...@messengeruser.com (David Musgrave