TimeOut with ms sql 2000

[arnaud_brunet]

Hello,

I have a program called Gestimum which question a MS SQL 2000 DataBase.

I have 6 clients who connect to the database througth Gestimum.

It works good for 5 of them.

But one of them I have TimeOut Error when he wants to print.

Gestimum use ADO to connect with Database, it use also TCP/IP to
connect with the server.

I already change the timeout delay to 0 (infinite)

So i don't understand why only one client doesn't work.

If anybody I have an idea ?

Thanks wery much.

PS: I'm sorry for my poor English (i'm French)

[Simon Hayes]

Are you sure that the timeout is coming from SQL Server? Normally,
printing has nothing to do with the database, so could it be a timeout
from the print server, perhaps?

If you believe it is an issue with SQL Server, you could use Profiler
to trace what's happening on the server, but I suspect that the best
option is to ask Gestimum directly about the problem.

Simon

[arnaud_brunet]

Yes, I am sure.
When you print a document in Gestimum, Gestimum asks data to the data
server (ms sql). And gestimum said that is an sql error.

I will try to ask it at Gestimum directely.

But it works which all of clients expect one so it's not a Gestimum
Error or MS SQL Error => it's an user system error :)

thanks.

[Erland Sommarskog]

(ar***********@hotmail.com) writes:

Yes, I am sure.
When you print a document in Gestimum, Gestimum asks data to the data
server (ms sql). And gestimum said that is an sql error.

I will try to ask it at Gestimum directely.

But it works which all of clients expect one so it's not a Gestimum
Error or MS SQL Error => it's an user system error :)

The only timeout error SQL Server can produce is a lock-timeout error.

Most client libraries have two pre-defined timeouts: one for connections
and one for queries. Partulcarly the query timeout is often taken for
an SQL error, but SQL is in fact innocent.

Since this happens to a single user, my guess would be for a connect
timeout.

But it would really help if you posted the exact error message. (Et
en cas le message est en française, postez le message en françsais,
s'îl vous plaît.)

Contacting the vendor as you intend to do, is probably the best option.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp