New Install of GP 10 doesn't detect data source name (server name) when logging in

(0) Share

Report

Posted on by MarianneRM

330

I have seen this issue before when installing GP 10 where GP doesn't seem to find the datasource at the login (server name). I can't for the life of me remember how to correct this issue. Has anyone had this problem and know the answer?

Thanks,

Marianne

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (0)

Frank Hamelly | MVP... 46,619 Super User 2025 Season 2 on at

Like (0)

Report

Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

If you're using SQL 2008, you need to create a 32 bit ODBC connection for GP to 'see' it. Read thru the GP installation guide for instructions on how to set that up.

Was this reply helpful? Yes No
Prakash P 800 on at

Like (0)

Report

Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

Hi Marianne,

Delete the configuration in the ODBC if any and create a new Data Source in the ODBC.

And now try to login in to GP.

Thanks,

Prakash

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

Hi,

Frank is dead on if your new install is on a 64-bit machine. Is it?

Kind regards,

Leslie

Was this reply helpful? Yes No
Sheri Ibbotson 712 on at

Like (0)

Report

Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

you need to setup a 32bit odbc possibly - if this is a 64 bit machine that may be the cause.

goto the runcommand and enter C:\windows\sysWOW64\ click ok

locate then odbcad32.exe right click hit create shortcut

then rename the shortcut to odbc 32 bit

now copy the shortcut you created

open the control panel and click administrative tools - click paste -in otherwords paste the shortcut in the admin tools folder

Now click the obdc32bit you just pasted in the admin tools folder and create your GP odbc using the system dsn tab

you should see the gp servername now when you launch gp utils now

Hope this solves the issue for you

Was this reply helpful? Yes No
MarianneRM 330 on at

Like (0)

Report

Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

It is a 64bit server with 64 bit windows 7 clients. I was able to get the server to respond by turning off UAC (user account controls) . I was using the 32bt obdc connection. So the server is happy go lucky. But the windows 7 64 bit clients are not so happy. With UAC off and using 32bit ODBC, I'm still not able to get the clients to respond to the sql instance. I'm getting error 08001 which states there is no allowance for remote connetion to sql. There is allowance to remote connection to the instance. I still think it has to do with the 64 bit enviroment. Any other ideas?

Thank you all who have responded. I really appreciate the help.

Was this reply helpful? Yes No
Renchan Li 40 on at

Like (0)

Report

Re: Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

Hi,

Using Named Pipes in configuring local ODBC 32-bit might work. Also the Windows client's ODBC DSN configuration may need to use SQL Server rather than SQL Native Client (for either SQL 2005 or SQL 2008 server 64-bit) so that Named Pipes option could become available. The general idea is like this: On SQL server, use MSSQL 2008's "Configuration Utility" to enable the named Pipes in Client Protocols. On Windows 7 client, Client ODBC DSN configuration is using SQL Server (vs. SQL Native Client 10.0). There are instances that Windows Server's SQL Server Browser service need be started.

Also, in Windows 7 Client's Windows Firewall with Advanced Security screen, you might want to create the new Outbound Rules to allow TCP1433 and UDP1434 ports open for GP10. I don't know much about the security consequance for opening UDP port 1434; my apology.

There is also a place that needs to change Windows client's setting for UDP 1434 to All; but that is in one of the instances and I don't remember where that setting is located.

For some Windows 7 workstations, PartnerSource's Knowledgebase article for ODBC configurations work.

Was this reply helpful? Yes No
Sheri Ibbotson 712 on at

Like (0)

Report

Re: Re: Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

You can install the SQL client code from the SQL CD on the windows 7 clients with the UAC off and create the odbc using SQL instead of the SQL Native client

Was this reply helpful? Yes No
Victoria Yudin 22,768 on at

Like (0)

Report

Re: Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

Marianne,

Are you not able to connect from ANY client machine? If so, a few other suggestions:

1. Make sure SQL Browser Service is turned on.

2. Depending on the version and edition of SQL Server, I believe sometime automatically have remote connectivity disabled when installed and you need to manually turn it on.

3. Turn off Windows firewall on the server.

I don't see if you mentioned whether it's SQL 2005 or SQL 2008, here is a link to a connectivity troubleshooting blog post for SQL 2005: http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx.

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Re: Re: Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

Hi Marianne,

I'll put in a little bit here. When you set up your ODBC were you successful in testing the connection? Is the port open on the server? As Victoria suggested, if you turn off the firewall and everything works - then you know security/permissions is the problem. I would look at the ports and make sure the appropriate one is open. For SQL I believe the default is 1433 - but it can be changed to anying in your ODBC.

Leslie

Was this reply helpful? Yes No
MarianneRM 330 on at

Like (0)

Report

Re: New Install of GP 10 doesn't detect data source name (server name) when logging in

I'm using sql 2005 express service pack 2 . The ODBC connections works great on the server. Remote is access able. I gave sql permisions more than I should have to see if that would work. TCP\IP is activated Browser service is on. I think this has to do with windows 7 64bit - windows 2008 64 bit combination. Has any one install sql \gp to this environment?

Was this reply helpful? Yes No