[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1856
  • Last Modified:

Dynamics GP Utilities login error

We have recently installed Dynamics GP 9.0 onto a fresh Win 2k3 Server.
When we attempt to run Dynamics GP, it brings up the GP Utilities window login.
Regardless of what is entered in the username and password fields (correct or not), a message comes up stating the login failed.
Has anyone experienced this issue before? What login is it expecting here?
We have confirmed the sa username and password as being correct but it doesn't appear to check it.
  • 3
  • 3
1 Solution
James GlaubigerCommented:
Can you please post a screenshot of the error message or the full text of the error?
James GlaubigerCommented:
Also make sure that SQL has been configured correctly for TCP/IP connections.
Was SQL installed in mixed mode?  Also, are you sure that you are using the proper DSN?  Was it a System DSN or a User DSN?  Screen shot would be
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

IT-CSAuthor Commented:
Hi Guys,

I've attached GPerror.doc.
This has the screen shots of what happens when running GP.
In this instance I have entered the correct sa password and received that pop-up message. This message appers, however, no matter what is entered in the username and password fields.

The SQL Server has the TCP/IP protocol enabled on the default port of 1433 - what else needs to be checked to "make sure that SQL has been configured correctly for TCP/IP connections."?

Yes, SQL has been installed in mixed mode. The "LocalServer" is listed under the System DSN (see screenshot in attached) - is that what you mean?

James GlaubigerCommented:
Please follow these steps to correctly setup an ODBC to GP.   You cannot use Local Server as the ODBC DNS.
To set up an ODBC data source connection for SQL Server by using the ODBC data sources, follow these steps:
1. To open the ODBC data sources window, click Start, and then click Control Panel. 
2. Double-click Administrative Tools, and then double-click Data Sources (ODBC). 
3. Click the System DSN tab, and then click Add to create a new ODBC data source. 
4. Follow the appropriate step:" If the computer is running SQL Server 2000, select SQL Server, and then click Finish. 
" If the computer is running SQL Server 2008 or SQL Server 2005, select SQL Native Client, and then click Finish.
5. Provide an ODBC name and description. For "Server," enter the instance of SQL Server to which Microsoft Dynamics GP or Microsoft Business Solutions - Great Plains will connect. Then click Next.
Note For the information that is required in this step, specify the following parameters:
Name: Type the name that you want to use for the data source. This name is stored in the ODBC.ini file. If you use process servers, use the same name for the 32-bit ODBC Data Source for all client workstations.
Description: Type a description of the data source. This field is optional.
Server: Type the name that you assigned to the instance of SQL Server when you installed Microsoft SQL Server to run together with Microsoft Dynamics GP or together with Microsoft Business Solutions - Great Plains.  
6. Click the With SQL Server Authentication using a login ID and password entered by the user option.
Note We recommend that you enter the same name on all the workstations. This includes the server. For example, if you use server_name\instance as the name on the server, use that name on all the workstations. Do not use the IP address on some workstations and the server name on other workstations. 
7. In the Connect to SQL Server to obtain default settings for the additional configuration options area, type the user name and password for the sa user.
Note The sa user name and password are not required. However, we recommend that you use them. If the sa user name and password are entered, the credentials are not stored in the ODBC setup. 
8. Click Client Configuration.  
9. In the Network libraries section, click TCP/IP. Verify that the instance of SQL Server that you are using for or Microsoft Dynamics GP or for Microsoft Business Solutions - Great Plains appears in the Server alias section and in the Server name section. Verify that the Dynamically Determine Port box is cleared, and then enter the appropriate port number. Click OK, and then click Next.
10. Clear all the options, and then click Next.
Note Do not change the default database even if you will use this ODBC for only one company. 
11. Clear all the options, and then click Finish. 
12. Verify all the information, and then click Test Data Source. If the connection tests successfully, click OK. 
13. Click OK two times to exit the ODBC Data Source Administrator. 

Open in new window

IT-CSAuthor Commented:
Thanks opster,

Have created ODBC to GP following the steps you outlined. I can now log in to the GP utilities using the new DSN cerated.

The wizard runs and throws up the following error - actually I've attached the screen shot.

What would cause this error?
IT-CSAuthor Commented:
This is a different issue that has to do with the collations and the sort orders of the DYNAMICS database and of the company database not matching the collations and the sort orders of the Microsoft SQL Server system databases.

Will need to investigate that further. This question has been asnwered though - thanks opster.

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now