Can't connect to both Live and Test from the same GP client

(0) Share

Report

Posted on by Community Member

Hi-

I've recently been handed the responsibility of administering our GP 2010 environments (3). I have a bit of experience with user administration in ver. 9, but have not been involved with our GP implementation(s) for just over a year now. Since I last touched GP, we've upgraded to GP 2010 and, clearly, there are some differences.

I have a few users who would like to perform testing in our TEST environment. Based on my knowledge of ver. 9, an ODBC needs to be configured on the client for each environment. What I want to accomplish is to allow users to select the server they would like to log into. My problem is, after setting up an ODBC (System DSN) to the TEST server, it doesn't appear as a choice in the drop-down on the GP Welcome screen. I've checked this connection several times, to make sure that I didn't miss anything, still, I have a feeling that I did.

Are there any suggestions on items that I can check?

Thanks, in advance.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (2)

Verified answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

When you initially created the ODBC on the client machine, have you logged on as Administrator ?

As you are logged on as Admin on the machine, have you tested the ODBC when it was completed ? Have you tried to open Dynamics GP as the admin and check whether you can see the ODBC connection or not ?

A reference for creating ODBC for Dynamics GP How To Create An ODBC For Microsoft Dynamics GP 2010

Let us know if all the above doesn't apply to your situation,

Your feedback is highly appreciated,

Was this reply helpful? Yes No
Suggested answer

Redbeard 12,931 on at

Like (0)

Report

It is possible you have configured a SYSTEM DSN for Dynamics GP on a 64 bit workstation with a 32 bit ODBC Administrator Tool, which is accessed through the Control Panel. If you want to see SYSTEM DSN on a 64 bit machine you should create it with the 64 bit ODBC Administrator Tool in the SysWoW64 folder. Here is a link to a KB article on this issue:

support.microsoft.com/.../942976

Was this reply helpful? Yes No
Manikandan 2,845 on at

Like (0)

Report

Hi,

It seems to be that you have done ODBC set up in the 64 bit. Please make sure the required ODBC connections is available in the following location for connecting Test and Live environment.

Example: C:\Windows\SysWOW64\odbcad32.exe.

If the ODBC configuration not available in this location, please configure new connection here and use that for your live and test GP server.

Was this reply helpful? Yes No
Suggested answer

Joshua Page on at

Like (0)

Report

As a few people have already noted, you most likely setup a 64 bit ODBC connection, GP must use a 32 bit connection.

The link in Mahmoud's post will walk you through setting up the ODBC connection to work with GP.

If you have any questions please feel free to let us know!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Mahmoud-

Thanks so much for your response. To answer your questions:

1. Yes. My Domain Admin account is an administrator on the workstation that I am testing on. I did not log onto the client workstation as the local Administrator.

2. Yes. During the ODBC setup wizard, the connection tested successfully. I've just tried launching GP as Administrator and there is no change. I still only see my Production server.

3. I found the page, at the link you've posted, earlier today. When I initially experienced this problem, and none of my troubleshooting helped, I googled the process to make certain that I had followed the correct steps.

As an additional note, there is an installation of GP 2010 on the sever where the TEST SQL instance lives. I have no problem logging in from the client on the server. Though I have not tried to configure an ODBC to any of the other environments from this server.

Thanks again-

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Redbeard-

Thanks, I appreciate your response. Yes, I used ODBCAD32.exe, in C:\Windows\SysWOW64\. I read about this requirement, while I was researching, this afternoon.

Thanks again-

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report

Adam

Could you please try to log in as the domain admin to this specific machine and try to create a new ODBC 32 accordingly ?

Your feedback is highly appreciated,

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

As several have suggested that I possibly didn't configure a 32 bit connection (which I did), I decided to delete the connection and set it up again from scratch. I noticed that, on the client machine, I do not have a SQL Server Native Client 11.0 driver. I have been using the SQL Server Native Client 10.0 driver in my setup.

In the link that Mahmoud posted, it instructs, "For Microsoft Dynamics GP 2010, the SQL Server Native Client 11.0 (or SQL Server Native Client 10.0 if you’re using SQL Server 2008) must be selected." The databases are actually running on MS SQL 2012. Could this be the issue?

Was this reply helpful? Yes No
Suggested answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

Go to the following link: SQL Native Client

Do not click on the Download button. Rather, go to the button of the page as shown below:

You will get the SQL Native Client 11.0 driver, for SQL 2012.

Let us know if you have any further inquiries,

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

I'm marking Mahmoud's post as the solution, because it led me to the actual solution, which was a name conflict. I didn't name the client ODBC consistently with the server connection. Once the connection names were consistent, my issue was resolved. I was able to see the TEST server in the drop-down.

Because I did not have a SQL Server Native Client 11.0 driver. I searched for a possible reason/solution. I stumbled upon a comment in this forum post that suggested that the Server and Client connection names needed to be consistent. The previous GP admin, who built my TEST environment had configured the TEST server connection with the same name as the current production connection. When I installed the GP client on the workstation, the first connection was to the Production environment. In my attempts at creating the second connection on the client, I appended TEST to the name, so that I would be able to distinguish between the different server connections. Ultimately, I created a second ODBC on the server, naming it distinctively, then created the connection on the client with the exact same distinctive name. I was then able to see the second server in the drop-down in the GP Welcome screen. I confirmed successful login to the TEST environment.

Thanks to everyone who posted a response. Helping out us underdogs is sure to bring you good Karma. :-)

http://scn.sap.com/thread/3445619

Was this reply helpful? Yes No