SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL State Error 'HYT00'


SQL State Error 'HYT00'

Author
Message
Andy Warren
Andy Warren
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: Moderators
Points: 25043 Visits: 2746
Hey Dan,

You can ping the IP address from the client, correct? Have you tried connecting via Query Analyzer on the client? DSN's use ODBC, QA does also. There's no magic to a DSN, it's really just a way to keep your connect string external to the app. Also as far as connecting there is really no difference between system, user, and file DSN's. Are you using SQL or NT authentication? Have you run Profiler while you're testing to see what if anything is coming across? What kind of lag are you seeing when you ping/tracert? I would suspect a network issue more than a SQL issue. Only other thought is to install latest MDAC on one client and test.


Andy

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Antares686
Antares686
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: Moderators
Points: 26390 Visits: 785
When you get to the autchenication screen there is a button for client config. Did you check in there to make sure that it is deffiently using the TCP/IP network library and also make sure it does not dynamcially determine the port, uncheck that option and put the correct port in. To me it looks like the server has answered as it is there but does not answer the authorization fast enough before the timeout occurrs. I don't believe this is MDAC related or server side configuration but I am still trying to directly reporduce. You may if your company owns one wanrt to put a packet sniffer of the connection from the user or the local router to the SQL server to see if you are suffering a packet problem. Also run Performance monitor at the client and the server to see if you have a high number of packets being lost this could explain why the client sees the server but is having troubles talking to it.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)



DanG
DanG
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 5
Hello guys,

Yes I can ping the SQL machine from the clients and the response is good. When I tried using QA from the client, I got the following:

Unable to connect to server P4
ODBC: Msg 0, Level 16, State1
.... Timeout Expired

I just made sure it is using TCP and unchecked determine dynamically, so it is using 1433.

I still have the same error.

When I test a DSN on the machine with SQL, it is successful and the response is immediate.

Appreciate the help,

Dan



DanG
DanG
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 5
Ok, here is something strange...

I decided to enable MultiProtocol on the server. Once I did that, I came back to the Client and set the DSN to MultiProtocol. Click Next and after waiting a bit - Error. I then went back into the configuration and set the DSN back to TCP. Click Next and it moved on and the test was successful and quick.

Does this give any clues as to the problem...

Dan



Antares686
Antares686
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: Moderators
Points: 26390 Visits: 785
No not really, could have been a corruption in the configuration that reset when you moved off TCP/IP then back on, but I would have to dig in the registry and try to force it myself. If I get a chance I have a test machine to play like this and will.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)



DanG
DanG
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 5
OK, you are probably right.

Well at least I am able to create a couple of new DSN's to get me going.

If you find anything further, please post.

Thanks again,

Dan



K. Brian Kelley
K. Brian Kelley
Keeper of the Duck
Keeper of the Duck (24K reputation)

Group: Moderators
Points: 24406 Visits: 1917
The way Multiprotocol works, it'll pass the computer name to RPC, and RPC will attempt to make a connection to the server using each supported NetLibrary present: Named Pipes, TCP/IP, IPX/SPX, whatever is there. It'll also do name resolution based on those methods (broadcast, WINS, SAP). Perhaps it was just too much traffic all at once?

K. Brian Kelley
bkelley@sqlservercentral.com
http://www.sqlservercentral.com/columnists/bkelley/

K. Brian Kelley
@‌kbriankelley
Michael-288452
Michael-288452
SSC Rookie
SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)

Group: General Forum Members
Points: 29 Visits: 1
I am facing the same error. I have Cisco VPN installed on a few PCs that need access from home. It used to work fine. Now, issues. I don't know what may have changed. Service pack??
I can connect to the server. I can see the server shared drives, etc. I can get to my Outlook mail (albeit incredibly slow).
However, when I try anything dealing with SQL databases I get the error. I can't connect to my databases (SQL Server 2000). I tried creating a new odbc connection. The server list box shows the servers, but I get the error if I try to connect to them.
My server is Windows 2000 server.

berto
berto
SSC-Addicted
SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)

Group: General Forum Members
Points: 449 Visits: 281
Hello,
I have similar problem. Two application server exactly the same configuration one works fionr one reports this error. I use TCP/IP only, telnet works fine but in ODBC or OLE DB provider this error.
Any ideas?

MCP ID# 1115468 Ceritified Since 1998
MCP, MCSE, MCP+I, MCSE+I, MCSA,
MCDBA SQL7.0 SQL 2000, MCTS SQL 2005
Erin.
Erin.
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2011 Visits: 558
This link maybe helpful.

http://jesseorosz.spaces.live.com/blog/cns!E322FD91218E57CF!176.entry
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search