Re: Strange SQL Server Timeout Problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joseph Geretz (jgeretz_at_nospam.com)
Date: 06/24/04 

Date: Thu, 24 Jun 2004 13:53:17 -0400

Hi Kelly,

Can you elaborate please? I'm not familiar with the auto close option.

Thanks,

Joe Geretz

"Kelly" <Kelly@discussions.microsoft.com> wrote in message
news:2241D937-89C3-40EC-9768-387F3D316C64@microsoft.com...
> It sounds like the auto close option is turned on.
>
> "Joseph Geretz" wrote:
>
> > We're seeing a very strange SQL Server access problem. At intermittent
> > times, all users are unable to log into our software. We've traced the
> > problem to the following query:
> >
> > INSERT INTO WORKSTATIONS SELECT MAX(WORKSTATIONID)+1, 'VMSRSSERVER1',
> > GETDATE(), 0 FROM WORKSTATIONS
> >
> > Here's the error information returned:
> >
> > PROVIDER ERROR
> > Error: -2147217871
> > Description: Timeout expired
> > Source: Microsoft OLE DB Provider for SQL Server
> >
> > What's strange about this is that, in order to reach this point, the
> > software must have already successfully issued a SELECT statement from
the
> > USERS table in order to to validate credentials. It seems, that in this
> > scenario, SELECT statements are successfully processed, but the first
INSERT
> > statement will hang. When this happens to one user, it happens to all
users
> > and no one can log into our software.
> >
> > Evan stranger, the situation can be corrected by simply accessing the
> > database in Enterprise Manager. In this scenario, I notice that
accessing
> > the database takes much longer than usual, approximately 30 seconds. But
> > once Enterprise Manager accesses the database, suddenly all users are
able
> > to log in again. Also, this seems to happen only in the morning. Once we
use
> > the Enterprise Manager trick, all users can once again log in and we're
good
> > until tomorrow...
> >
> > Has anyone seen this problem? Or if you can suggest an approach for me
to
> > investigate this, that would be extremely helpful as well.
> >
> > Thanks very much for your help!
> >
> > - Joe Geretz -
> >
> >
> >

Relevant Pages

  • Strange SQL Server Timeout Problem
    ... We're seeing a very strange SQL Server access problem. ... the database takes much longer than usual, ... once Enterprise Manager accesses the database, ...
    (microsoft.public.sqlserver.server)
  • RE: strange behavior of default document
    ... This is strange because http://>/ is ... If form1.asp is loaded without any query strings, will it be auto ... Get Secure! ...
    (microsoft.public.inetserver.iis)
  • Re: How to set default date format in Access 07
    ... the date that it auto inserts has the time after it, ... timestamp off? ... I have tried filters on the date field but they do not work, ... that you can get strange results if you have a Field or form control named ...
    (microsoft.public.access.gettingstarted)
  • RE: Problem with Autocreated Client Printers
    ... > Its strange because the auto created printers create fine ... > when a user logs in. ... > they can see all other users autocreated local printers. ...
    (microsoft.public.windows.terminal_services)