Connection failed: SQLState: ‘S1T00’
Rui Oliveira
when try to login in SQL.
Connection failed:
SQLState: ‘S1T00’
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired
I am using a ODBC string to connect to DB. This happened in two computers,
one with Windows XP Professional sp2, with last updates, and the other with
Windows Vista Premium.
Apparently these computers are similar to a lot of others, but in this two
appears the message error. When I click OK appears the dialog to introduce
again user and password. And I just click OK again, without change
user/password values, and the application enters without more errors.
What could be? Someone have any suggestion?
Thanks,
Rui Oliveira
Frank Hickman
news:3413D460-2A8B-4572...@microsoft.com...
If the connection succeeds the second time, the initial connection may just
be experiencing lag (dropped packets). You mention "just a few in
thousands", is the network bandwidth high enough for the amount of data
being transferred?
--
============
Frank Hickman
NobleSoft, Inc.
============
Replace the _nosp@m_ with @ to reply.
Rui Oliveira
Could be lag, but it is strange the problem to appear always in same
computers, and every time I open application in that computers.
I said “just a few in thousands”, but thousands are not in same network. The
last computer detected with the problem, has been the first client that I
have installed in a new application network.
Tks. Rui
Frank Hickman
> Thanks for reply.
> Could be lag, but it is strange the problem to appear always in same
> computers, and every time I open application in that computers.
> I said "just a few in thousands", but thousands are not in same network.
> The
> last computer detected with the problem, has been the first client that I
> have installed in a new application network.
> Tks. Rui
>
In that case, if at all possible, you should examine the NIC configuration
to ensure that it is not sending short packets and that it is configured
properly. If that is the case, and you have access to the switch/hub the
system in connected to, try a different port. If it is on a hub, recommend
to the ptb to upgrade to a switch.
Rui Oliveira
it is configured properly?
Tks. Rui
Frank Hickman
> How could I check if the NIC configuration it is sending short packets or
> if
> it is configured properly?
> Tks. Rui
>
Well you can start by making sure the metric for the controller is not set
to high. Sometimes when the network drivers are set to the defaults, the
metric is set to around 20. I find that this setting often causes
misdirection when the system tries to pick a good route to the destination
system. You can check this by opening a command window and type "route
print". The metric should be the last option. If it is anything higher
than one in any option do the following: In Control Panel under Network
Connections, open the properties for the NIC. Select the Internet Protocol
(TCP/IP) option and click properties. Click on advanced and you will see if
the NIC is using Automatic metric. If it is, unselect the option and put
"1" in the edit box.
As for as the packet size, you can check this my going to www.broadband.com
and using the tool there for analyzing the NIC. There are also detailed
instructions on how to modify the settings if needed. If I remember
correctly they have a tool, or can point you to where it is, that you can
download and make the changes for you. Otherwise, you would need to change
the registry settings manually.
Rui Oliveira
I have tried to use Named Pipes in ODBC configuration and solved some of the
clients initially with the problem.
What could be wrong with TCPIP? How could I repair this?
Tks,
Rui
Frank Hickman
>I have changed metric to "1" but didn't solve the problem.
>
> I have tried to use Named Pipes in ODBC configuration and solved some of
> the
> clients initially with the problem.
>
> What could be wrong with TCPIP? How could I repair this?
>
> Tks,
> Rui
>
>
What are you using for the server address? Is it an IP address or a
computer name? If it is an IP address it should be able to get right to it,
if it is a computer name, the problem may be in the DNS resolution. If the
problem is consistent and your using the computer name, try changing it to
the IP address to see if that helps. If it does, you will need to research
why the DNS is taking so long to resolve the IP address. This could be a
network issue with the DNS server.
Rui Oliveira
problem disappears.
Tks, Rui
Frank Hickman
>I used the "WinsockFix" tool to clean TCPIP configuration. After that the
> problem disappears.
> Tks, Rui
>
>
Glad to hear you fixed your problem.
Rui Oliveira
when tried to login in SQL.
Connection failed:
SQLState: ‘S1T00’
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired
When I click OK appears the dialog to introduce again user and password. And
I just click OK again, without change user/password values, and the
application enters without more errors.
I am using an ODBC string to connect to DB.
This happened in computers with the firewall client of ISA server. Even when
I stop the firewall client of ISA server service, the error appears.
When I run the "WinsockFix" tool to clean TCPIP configuration, the problem
disappears but the firewall client of ISA server don’t work anymore. When I
reinstall the firewall client of ISA server, the problems appears again.
What could be? Someone have any suggestion?
Thanks,
Rui Oliveira
lherre...@starmedica.com
regards
