SQL connection problem

[Agung]

I connected my NT Ws to my SQL server but always failed

Connection Failed
SQL State: 'HYT00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver] Timeout expired

I installed SQL client to my PC but still fail and when I try connecting from Windows 98 to connection was successfull. Is there any way how to connect to SQL server with VFP except from ODBC? Please help.

 

[jjgraf]

http://www.microsoft.com/downloads/release.asp?ReleaseID=33503&area=search&ordinal=21

here is the link to the latest MDAC which includes the sql drivers download and install and see if that fixes your problem.

 

[Agung]

Hi I installed the latest MDAC and Office 2000 already but still got the same error. Please advise

 

[DEDMOD]

How are you trying to establish your ODBC connection? You do have SQL Server up and running when you're trying, don't you? And a network connection between your server and your work station?

Dave Dardinger

 

[jjgraf]

I connect to SQL server 7.0 and 2000 on a daily bases on win95 all the way to winXP.

Go into the Data sources /odbc manager and try to make a System DSN and then test the connection from the manager and see what the error is. Allso change the Method of connection to tcp/ip from Named Pipes which is the default. ( in some very rare cases this errors out for no reason.)

This should work, the error you posted i found no Info on the MS knowledge base

 

[Agung]

To DAVE:
1. I using Data Source (ODBC) from Control Panel
2. Yes I do, My SQL Server up and running
3. I am using Windows NT for OS and TCP/IP for connection.

To JJGRAF:
The strange is after I upgraded my MDAC then I try to connecting again with TCP/IP and still not working but when I try to connecting with named pipes it's working, I got connection to my SQL server, why it's different with yours? Thanks for your effort to solve my problem.

 

[DEDMOD]

I'm not certain how close NT is to Windows 2000 which is what I have, though I believe they're supposed to be pretty close. Are you selecting the proper SQL Server? In Windows 2000 the box for selecting is on the same page where you name your connection. I believe it defaults to your local server. I note that my system defaults to named pipes too. Maybe you have tried using the wrong TCP/IP parameters. Anyway if named pipes are working, it'd seem you're home free.

Dave Dardinger

 

[jjgraf]

Named pipes is Uses Remote Procdure Call interface or RPC to do the work, its slower becasue of the added over head that RPC creates and is not the preferred method MS wants us to use anymore.


With MDAC 2.6 the default protocol change from Named pipes to TCP

Which yes i agree with DEDMOD TCP is not configure properly if it does not work. It should use the NetBIOS name or IP address to the server then use port 1422 which is the default port Unless someone changed it on the SQL or client. MDAC 2.6 can dynamicly configure the port.