locked
Error Logging Into GreatPlains RRS feed

  • Question

  • Trying to log into GP on a client computer and get the following error:

    "This login failed. Attempt to log in again or contact your system administrator"

    We can log into the sa account just fine, but any other user we try fails.  Also, we can log into this account on another client running GP just fine as well.  I tested the DSN connection and it tests fine.

    Thanks in advance.

    Monday, January 19, 2015 5:16 PM

All replies

  • Hello,

    Could you examine the SQL Server error log and see if you can get a more detailed dscription of the error?


    http://msdn.microsoft.com/en-us/library/ms187109.aspx


    The error state will provide you the reason behind the login failed.

    http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx


    Hope this helps.


    Regards,



    Alberto Morillo
    SQLCoffee.com



    Monday, January 19, 2015 8:57 PM
  • The error is saying that the password doesn't match even though we changed it and we know that we are using the correct one??

    Monday, January 19, 2015 10:29 PM
  • The error is saying that the password doesn't match even though we changed it and we know that we are using the correct one??

    My experience that when it comes to such issues, it is useless to argue with a computer. They are always right.

    Maybe you changed it on a different instance. Maybe you did not change it to what you think you changed it to. Maybe the Caps Lock key is pressed.

    Also try to use the username/password in SSMS rather in Great Plains.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Monday, January 19, 2015 10:37 PM
  • As I stated before, I can go to another client computer and enter the exact same credentials and it works fine.  
    Monday, January 19, 2015 10:43 PM
  • Is there perhaps a client alias configured on one or the other clients?

    David


    David http://blogs.msdn.com/b/dbrowne/

    Monday, January 19, 2015 10:49 PM
  • No, sir.  There isn't.
    Monday, January 19, 2015 10:53 PM
  • As I stated before, I can go to another client computer and enter the exact same credentials and it works fine.  

    And still: computers don't lie. If a computer tells you that the password is incorrect - it is incorrect.

    You can use SQL Server Profiler and the Login failed event to capture what login SQL Server sees, in case the login name is mutilated or replaced along the way.

    Did you try to login from this computer with something else than Great Plains?


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Tuesday, January 20, 2015 8:24 AM
  • Everything else on this computer works without issue.  Just trying to log into GP is a problem.  Also, the COMPUTER isnt saying that the password is incorrect.  It just says that the server denied the connection.  Here is a screenshot from the computer when trying to configure DSN:


    Tuesday, January 20, 2015 2:48 PM
  • Also, been reading a lot about the system DSN properties and that they have to be the same.  THe system dsn entry will not resolve the server name, but works with an ip address instead.  Now, I know that wont work, but the computer itself resolves the server name just fine.

    Im sure this might have something to do with it, but I cannot get the System DSN to resolve the server name.  I can ping and resolve the server name just fine in other areas of the computer, however.

    Tuesday, January 20, 2015 6:30 PM
  • Everything else on this computer works without issue.  Just trying to log into GP is a problem.  Also, the COMPUTER isnt saying that the password is incorrect.  It just says that the server denied the connection.  Here is a screenshot from the computer when trying to configure DSN:

    That error message is completely different from incorrect password. This error message means that you tries to connect to a port where there is no SQL Server instance listening.

    I am not sure what DSNs has to do with this. Does Great Plains use ODBC and DSN for connection?


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    Tuesday, January 20, 2015 10:51 PM
  • Yes, it does.
    Tuesday, January 20, 2015 10:56 PM
  • Hello,

    Based on the following article, please configure Windows Firewall or any security software to allow SQL Server access.

    http://blogs.msdn.com/b/spike/archive/2008/11/07/sql-server-error-10060-sql-server-error-10061.aspx


    In case, Windows Firewall is enabled, use the following article to configure it or disable it.


    https://msdn.microsoft.com/en-us/library/ms175043.aspx


    Hope this helps.



    Regards,

    Alberto Morillo
    SQLCoffee.com


    Wednesday, January 28, 2015 7:06 PM