Re: SQL 7.0 sp4 - hotfixed and broken

From: Djana Milton [MS] (djanam@online.microsoft.com)
Date: 01/31/03 

From: "Djana Milton [MS]" <djanam@online.microsoft.com>
Date: Fri, 31 Jan 2003 06:52:19 -0800

You need to disable all server access so that nothing gets in except for
you.

>From a command line:
Pause the server: net pause server
Kill all sessions: net sessions /delete
kill all sql sessions: net stop mssqlserver
make sure agent isn't running: net stop sqlserveragent
restart sql server: net start mssqlserver

from isql or osql:
    sp_Configure 'show advanced', 1
    go
    reconfigure with override
    go
    sp_configure 'connections',0
    go
    reconfigure with override
    go
    sp_configure 'show advanced', 0
    go
    reconfigure with override
    go

from the command line:
net stop mssqlserver
net start mssqlserver
net continue server 

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Djana O.C. Milton
SQL Server PM
"cauline" <cauline.holdren@dot.state.fl.us> wrote in message
news:06eb01c2c923$e4fe3ae0$d6f82ecf@TK2MSFTNGXA13...
> Re-enabled named pipes as you suggested, to no avail.
>
> On examining the errorlog, it's pretty obvious that my
> setting did take. Here's an excerpt...
>
> 2003-01-30 13:51:27.68 kernel   initconfig: Number of user
> connections limited to 1.
> 2003-01-30 15:04:33.16 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:05:33.19 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:06:33.22 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:07:33.25 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:08:33.29 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:09:33.32 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:10:33.35 kernel   The maximum limit for
> connections has been reached.
> 2003-01-30 15:11:33.38 kernel   The maximum limit for
> connections has been reached.
>
> I guess my question now would be, is there any way to
> change this back to (0) unlimited?
>
> Thank you again.

Relevant Pages

  • Re: SQL 7.0 sp4 - hotfixed and broken
    ... Here's an excerpt... ... 2003-01-30 15:04:33.16 kernel The maximum limit for ... connections has been reached. ...
    (microsoft.public.sqlserver.security)
  • Re: Deactivating service shell due to excessive incoming connections
    ... I am running rcp commands to the server when that error ... When do I have to tune in the kernel to fix it? ... that pertain to the maximum number of connections. ...
    (comp.os.linux.misc)
  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... You really should go through the steps I posted and get the SMTP service to stop hanging in the first place. ... You'll be happier, you won't be clubbing your server every day with a kill script, and you won't have dead connections. ... You do *not* need to restart the server, ...
    (microsoft.public.windows.server.sbs)