Timeout errors

[Erland Sommarskog]

Re: Timeout errors

pb648174 (google@webpaul .net) writes:[color=blue]
> I used the same script and specified a bogus machine name and got
> "Specified SQL Server not found", so it isn't a network issue I
> guess... I'm at a loss as to what to do from here.[/color]

Yes, that's the message I would expect if the server is entierly
unavailable. But what if some packets make it, and others not?

I'm about as lost as you are, but what about running ping -n 200 in
conjunction with running the backup job, and then check for packet
loss?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

Books Online for SQL Server 2005 at

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

Books Online for SQL Server 2000 at

http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[pb648174]

Re: Timeout errors

Ok, I'll try that and report back in a week or two most likely - thanks.

[das]

Re: Timeout errors

Just my 2 cents, I faced a similar problem sometime ago:

I would try to backup my SQL Server DB (not from a script, but
manually) and I would get timeout's after sometime. I found out that
this happens when you are running the backup remotely to write to a
drive on the SQL Server (basically a n/w issue)

So I started logging into the actual m/c and then backing up there was
not a problem anymore. Also my DB was huge by then about 10GB.

Hope that helps.

[Erland Sommarskog]

Re: Timeout errors


An interesting observation. I have installed some Internet Firewall
Client on my box at work, as per request from my sysadmin.

When I connect from home, I now have troubles of accessing my machine,
and relevant to this thread is that some attempts to connect with
OSQL gave the message "Timeout expired". I am able to connect to the
machine with Remote Desktop and by file system. When I added the
option -l 30, to get a longer connection timeout, the only change
was that it took longer time for "Timeout expired" to appear.

I'm not saying that you have exactly the same problem as I have, but
at least it is an indication that my theory that the connection is
initiated, but then fails somewhere.

I had some more ideas that I should try, but alas now I only get the
message "SQL Server does not exist or access denied".

--
Erland Sommarskog, Stockholm, esquel@sommarsk og.se

[pb648174]

Re: Timeout errors

We have multiple database servers and want to keep it centralized so I
don't think we will do the back job from the SQL Server.. Also, that
doesn't seem to make sense because all osql or enterprise manager does
is issue a command to the SQL Server.. It isn't actually making a
backup from the connecting client and transferring the file. I guess
for now we will just live with the intermittent backups problems. I
have the ping command in there so I'll know once it fails again if the
entire network connection is down.

Erlans, I take it you have unblocked ALL traffic to 1433 for your
firewall? It might consider your home connection as a different type of
connection. Also, I have had problems with Authenticated logins through
firewalls and use only SQL Authentication when just 1433 is open.

[Erland Sommarskog]

Re: Timeout errors

pb648174 (google@webpaul .net) writes:[color=blue]
> We have multiple database servers and want to keep it centralized so I
> don't think we will do the back job from the SQL Server.. Also, that
> doesn't seem to make sense because all osql or enterprise manager does
> is issue a command to the SQL Server.. It isn't actually making a
> backup from the connecting client and transferring the file. I guess
> for now we will just live with the intermittent backups problems. I
> have the ping command in there so I'll know once it fails again if the
> entire network connection is down.[/color]

The error "timeout expired" has nothing to do with the backup command.
You could just as well have a "PRINT 'Howdy!'" in that input file. You
would get the same error. OSQL fails to connect to SQL Server for some
reason that I don't know.
[color=blue]
> Erlans, I take it you have unblocked ALL traffic to 1433 for your
> firewall? It might consider your home connection as a different type of
> connection. Also, I have had problems with Authenticated logins through
> firewalls and use only SQL Authentication when just 1433 is open.[/color]


It used to work, but then I installed this Internet Firewall Client. There
is some ISA Server in the mix too. I have not investigated where the
problem might be, and I think I will leave to my sysadmin to find out. :-)
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

Books Online for SQL Server 2005 at

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

Books Online for SQL Server 2000 at

http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[pb648174]

Re: Timeout errors

As per previous posts in this thread, I have added the ping statement
to the server in question to the backup script.. Here we are a few
weeks later with the same intermittent
problem, ping works fine.

Pinging dbserver [192.168.23.154] with 32 bytes of data:

Reply from 192.168.23.154: bytes=32 time<10ms TTL=128

Reply from 192.168.23.154: bytes=32 time<10ms TTL=128

Reply from 192.168.23.154: bytes=32 time<10ms TTL=128

Reply from 192.168.23.154: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.23.154:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

8:00:19.85
Timeout expired
8:00:37.23

[Erland Sommarskog]

Re: Timeout errors

pb648174 (google@webpaul .net) writes:[color=blue]
> As per previous posts in this thread, I have added the ping statement
> to the server in question to the backup script.. Here we are a few
> weeks later with the same intermittent
> problem, ping works fine.
>
> Pinging dbserver [192.168.23.154] with 32 bytes of data:
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Reply from 192.168.23.154: bytes=32 time<10ms TTL=128
>
> Ping statistics for 192.168.23.154:
>
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>
> Approximate round trip times in milli-seconds:
>
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> 8:00:19.85
> Timeout expired
> 8:00:37.23[/color]

When I was able to get "Timeout Expired" to my server at work, I was
still able to ping my machine.

As I've said before, I suspect that the issue is related to Windows
Networking, Active Directory or something else I have very little
knowledge of.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

Books Online for SQL Server 2005 at

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

Books Online for SQL Server 2000 at

http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx