RE: Server2000 Std Edition Timeouts

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


Also, thinkiing a little more, the apps are establishing a direct connection
to the Server2000 DB. They aren't using the local MDSE DB.

"HMSSkeptical" wrote:

Hi,

First, asuume a large level of ignorance on this end. Didn't know we could
leave it at "0". A big question is how to reset ? As I mentioned, I tried a
re-install (over existing, not uninstall/reinstall - didn't want to clobber
existing DB files) and was not asked for number of users.

My guess is that no hotfixes have ever been applied on the MDSE side; that
may be a contributor but unknown. On the user side (the MSDE side) they have
no explicit control over number of connections. Driven by app requirements.

We also see the timeouts when trying to do the initial connection to the Std
Edition DB on the file server, so I'm pretty sure the problem is on that
side.

Is there a way to increase the timeout limit ? I've been trying to find
something in the Enterprise Manager that lets me do local client
configuration tasks and can't find anything.

Regards

"HMSSkeptical" wrote:

Hi All,

Have apps on user XP PCs running Server2000 MSDE - sharing into db on MS
Server 2003 x64 file server with SQL Server 2000 Std Edition Single CPU
Unlimited users (with all latest hotfixes Build 8.00.2249, using the 32 bit
version x86 ).

Server 2000 Std Edition was configured to 32 users at setup. We have about
14 active users running multithreaded apps that could have as many as 15
request to the SQL server at a time. We (possibly stupidly) assumed that 32
users meant support for lots of connections per user.

We are seeing lots of timeout messages:

getConnection{} failed

SqlConnectionFactoryImpl.getConnection: Timeout expired The timeout period
expired prior to completion of the operation or the server is not responding

When logged into the device that Server 2000 0is running on, the Event
Viewer rarely shows any hint of a problem, other than an occasional SQL
Server stopped.

When trying to stop, and then restart, using the SQL ServerManager from the
tray, the "stopping" part never completes. We have to kill tasks using Task
Manager.

Comments ? Ideas ? Solutions ? If we need to revise the number of users
upward, how do we do this ? Reinstall (on top of existing) did not allow
respecification of number of users.
.

Relevant Pages

  • Re: web serivce: client side timeout?
    ... client side but only from the server side. ... System.Net.Sockets.SocketException: A connection attempt failed ... asyncResult, Int32 timeout, Exception& exception) ... John Saunders | MVP - Windows Server System - Connected System ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Timeout expired. The timeout period elapsed prior to completion of the operation or the server i
    ... This does not look like a Connection Pool issue--the message returned by the ... errors are traditionally caused when SQL Server is loaded beyond capacity. ... Message: Timeout expired. ... it appears that this error is more of a TCP/IP type ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Outlook and Outlook Express die....after a while.
    ... >> Your server has unexpectedly terminated the connection. ... with as little as 4% packet loss. ... tolerant so it doesn't look to be a server-side timeout problem during ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: detecting the (brute) disconnection of a client
    ... crashed, and if an exception occurs, then the client is deconnected. ... You can either use the timeout itself as an indication of connection failure, or you can attempt to send data after the timeout. ... The server has no way to know if the connection has failed due to a client-side crash, or simply due to a temporary problem with the network. ... IMHO, it would be better to simply let the server continue to assume that the connection is valid unless there is some explicit, non-arbitrary verification that it's not. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Sendmail + DoS???
    ... carefully examining the behaviour of the server for those mails, ... which enforces a timeout at this stage: ... Throtle and connection rate limit are solutions for that. ... I use milter-error to stop the kind of dictionary attacks that include ...
    (comp.mail.sendmail)