Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
unable to logon client user only sa account gets through
danielad
Member Posts: 2
I have installed the Great Plains Client Application on my desktop and configured the ODBC drive to connect to the SQL Server with sa account and with default database as being the GP company database.
When I open Great Plains with my user account I get a message saying "The Login failed. Attempt to log on again or contact your System Administrator".
I have no problem loggin on to GP from the GP server with this specific user account, only when I try to connect to it from a client GP.
In addition if I enter the sa account in the GP client logon screen I am able to logon. This seems to be the only account that allows access to GP from the client application.
Any ideas? Thank you so much for your input!
When I open Great Plains with my user account I get a message saying "The Login failed. Attempt to log on again or contact your System Administrator".
I have no problem loggin on to GP from the GP server with this specific user account, only when I try to connect to it from a client GP.
In addition if I enter the sa account in the GP client logon screen I am able to logon. This seems to be the only account that allows access to GP from the client application.
Any ideas? Thank you so much for your input!
0
Comments
It seems the user you are using to login from the client machine has permission restrictions or the ODBC is corrupted in a way.
First, try to change the name of the ODBC and try to log on, then make sure you run the script grant sql to give the user access to the DYNGRP.
Hope this solves your problem
Good Luck
MCLC,MCT,MCITP,MCTS,MCSA,MCP
You will never know what power you have until you take decisions in a hard time.