Problem with SQL Server 2000!

Really? that can be the reason! Because users make a PC Reset (From the Reset Button) instead of using Windows shutdown most of the time! So orphaned connections still exist!

How can I go around this?

Reducate your users, using power switch instead of shutdown causes all sorts of problems in Win 98.

Also you can change connection timeout values in SQL server (or so I think), not got a copy here so cannot check how.

Jay

Edit: Timeout should be set for ODBC or whatever you use as a translator, not SQL server itself (my mistake, I was thinking of query timeout). You could check how many concurrent connections your SQL server is set to allow (Enterprise->Server->Properties->Connections).

[edited by - Jason Zelos on May 5, 2004 2:06:14 PM]

If you''re using MSDE 2000 (the free version of MS SQL), then there is a five user connection limit.

I just reread your post, I''m guessing Zipster is correct as MS SQL 2000 (production edition anyway) will not install on XP only Windows server products.

Jay

No, my Client program does close the connection when it is done!

You know, Another possible reason is that the server is overloaded! Am not sure, just want to ask : Is this possible?

I store about 50 pictures as binary data, and the client programs make heavy logging of events happening. Can any of those two be the reason for the theoritical server overload?

[edited by - gtarawneh on May 5, 2004 4:13:24 PM]

If either of those was a problem your clients would be able to connect. You would just have slow access to the database (unless you have set it up differently). I''d check what authentication you use to connect, make sure the clients are logged into the domain before accessing etc.

Check that the faulty clients can ping the server and that no firewall is blocking port 1443 (or whatever port you use). Although I doubt that would affect you unless different users have different ACL''s.


''No, my Client program does close the connection when it is done! ''

Even when the program crashes after a reboot? Normally there is a delay before the server closes the connection unless the client requests it. Not sure what the delay is though.

Jay

What error does ODBC (or whatever interface you are using) return when the clients cannot connect?

If you are really overloaded you would at most get a connection timeout. Though I have yet to see a SQL server instance refuse a connection because it is overloaded. Have you set a maximum number of concurrent user connections?

Though, this sounds more like a network problem then a SQL problem.

The error message is : "SQL Server does not exist or access denied", I installed Windows 98 on that network and seems (so far) that all is working fine!

Anyway, I did that because I heard some people talk about WindowsXP inbound connections limitations!