web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2013 Web Client GP ...
Microsoft Dynamics GP (Archived)

GP 2013 Web Client GP Login

(0) ShareShare
ReportReport
Posted on by IceMan 1,115

I'm running an initial GP 2013 Test environment with the supporting web\processor servers configured.  I'm able to successfully authenticate through the initial Microsoft Dynamics GP web client and open the GP Company login window.   At the second authentication screen you have choices for Windows login or SQL Server login.  I can successfully choose SQL Server Login and complete the login process under the 'sa' account but no other Windows or SQL accounts that I have created in GP are working through Web Client.  I can use the same SQL GP Account and login through traditional Client\Server approach but not through the GP Web Client.  I authenticate to the initial Web Client login with Domain credentials and then reach the company login, i enter different GP SQL specific credentials and it fails with the message to contact my administrator.  

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at
    RE: GP 2013 Web Client GP Login

    Hi,

    Have you created GP login in desktop GP through SA user?

    if the users are created then have you check the respective users are login\access their client GP without encountering errors?

    In Desktop GP, The respective GP users  have been granted access permissions to various companies?

    if the error occurs in desktop case, please make sure ODBC configuration should be same for both server and client.

    I guess you are in GP 2013 R2, if it is you can map the Domain\Windows credentials though respective user setup screen. if it is properly configured you can login Web Client through Domain\Windows credentials alone.

    if the desktop side woks fine then you need to make sure the Web client was configured properly.

  • Suggested answer
    soma Profile Picture
    soma 24,410 on at
    RE: GP 2013 Web Client GP Login

    Have you try to login desktop client through the GP users (rather than sa user)? Also check the ODBC connection and instance name for GP installed SQL server.

    Hope this helps!!!

  • IceMan Profile Picture
    IceMan 1,115 on at
    RE: GP 2013 Web Client GP Login

    I am able to successfully login to the desktop client with the GP user account.  When I go to try the web client I can successfully authenticate to the first set of web client credentials but when I get to the actual GP application login it fails when set to SQL Server Authentication.    That is strange since the desktop client has no problem logging in with the same credentials.  If the first Web Client authentication works then the problem is not the Active Directory group assignment and if I can authenticate successfully to the second Web Client authentication as 'sa' it tells me the web client solution is configured correctly.   I copied access rights from the 'sa' account when setting up these users in GP.  

  • soma Profile Picture
    soma 24,410 on at
    RE: GP 2013 Web Client GP Login

    Yes. This is strange scenario. Better contact your partner to get the help then resolve the issue.

    Hope this helps!!!

  • Suggested answer
    IceMan Profile Picture
    IceMan 1,115 on at
    RE: GP 2013 Web Client GP Login

    So it looks like I got burned on the ODBC Server name reference on the Process Server.   If the ODBC Server Name reference does not match the reference on the server on which the accounts were created GP fails to un-encrypt the password.   Basically one server had the full DNS name and the other had just the server name reference in ODBC.  

  • soma Profile Picture
    soma 24,410 on at
    RE: GP 2013 Web Client GP Login

    Is your problem solved?

  • Verified answer
    IceMan Profile Picture
    IceMan 1,115 on at
    RE: GP 2013 Web Client GP Login

    Yes, the problem was the Server Name reference in ODBC was different on the Process Server compared to the SQL Server on which the GP accounts had been created.  

  • IceMan Profile Picture
    IceMan 1,115 on at
    RE: GP 2013 Web Client GP Login

    Just an FYI, if the Database Server name reference in the ODBC is not the same on all Session Hosts and Database Server you will also have a problem with the Windows Authentication through the web client as well.  It is not just the SQL authentication that will fail. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans