Re: SQL server connection problem

KHATER,

Application Log and Transaction Log are not identical, I responded to your
other post. (Once for Transaction Log and (finally) once for Application
Log.)

RLF

"KHATER" <KHATER@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:393777BD-CE08-4C42-9466-788421073E98@xxxxxxxxxxxxxxxx
Please can you tell me what is the difference between the application log
and
the transaction log? if both of them are identical, can I use the commnd
"DUMP trnsaction log"?. Is it necessary to dump database after processing
DUMP transaction log?. Please can you tell me the difference between DUMP
and
DROP database?
Thank you

"Ekrem Önsoy" wrote:

Something pulls you back from changing it but I can't figure out what it
is
from this message unfortunately :(

You can clear the Application Log from Event Viewer. Go to Event Viewer
and
right click on it and clear it. If you need to keep that log, then save
it
before clearing.

I could suggest you to connect to your SQL Server in a Single-User mode
and
then try that change in that mode.

You can do that going to SQL Server Configuration Manager and go to
properties of SQL Server service. Go to Advanced tab and add "-m;"
parameter
to the Startup Parameters. Restart your SQL Server service and then try
changing Maximum concurrent connections value.

After performing this, do not forget to going back to SQL Server service
properties and erasing that "-m" parameter and restarting your SQL Server
service. Otherwise, nobody except for you could loging to SQL Server.

Also, stop SQL Server agent before trying to login to SQL Server when
it's
in Single User mode, because it may try to use that Single-User right and
then you may end up failing to login to SQL Server because of SQL Server
Agent service.

Please let me know about the result of this process if you proceed.

--
Ekrem Önsoy
MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT



"KHATER" <KHATER@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:485D24AF-35CA-4577-8A42-7B2E3403E6B7@xxxxxxxxxxxxxxxx
Thank you for your tips. I've tried to change the user connections to
0, I
found the error message was no more active for a long period before it
reactivated again at the end but with connections user 25! Through that
time
I've received the following message

"A connection could not be established to fileserver - (DB-Library) SQL
server connection Timed out".

"SQL server connection time out. Do you wish to retry?

"ERROR 10024 (DB Library) SQL server connection time out"

Msg No 10007 Severity 5 State 0. General SQL server error.



Here some more problem clarification that it could help fixing the
problem

- The working data base is marked inaccessible and cannot be edited

- The following message appears when restart the server and before
login

"The application log file is full"
If you have any further useful tips, please do not hesitate to send it
to
me.
Thank you and best regards.

KHATER


"Ekrem Önsoy" wrote:

You said you tried using sp_configure but I'll ask you to go to EM and
connect to your instance and then go to SQL Server Properties dialog
box
and
select Connections tab and check the "Maximum concurrent user
connections"
option for this situation. If it's set to 15 or something, please
change
it
to "0" which means unlimited connections are going to be accepted by
SQL
Server.

Please let me know about the result of this course.

--
Ekrem Önsoy
MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT



"KHATER" <KHATER@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EEB5A7C4-2ECA-47EC-BF23-DC2EB21989B6@xxxxxxxxxxxxxxxx

Problem description
==============
- I have 4 clients and 1 server (SQL server)
- 3 clients are Monitoring console 1 client is operation
console
- Monitoring console collects some data from the control unit
and
store them into the Sql server
- The operation console then retrieve this data from the sql
for
reporting and statistics purposes
- I am using ODBC connection
- The problem is that the operation console is not able to
connect
to
Sql server
- I receive Error message: "A connection could not be
established
to
fileserver-(SQL server). Unable to connect. The max number of 15
configured
user connections are already connected. System administrator can
configure
to
a higher value with SP_Configure"
- I receive the same error message in many conditions while I
am
using
the EM (Enterprise Manager) GUI

Environment
========
Windows NT 4.0
SQL 6.5

Troubleshooting (we have done & Analysis)
=====
- Seems that sql server has reached the max allowable number
of
connections
- It might be some opened connection those never being closed
by
some
application.
- This problem also appears when 7.5 installed while 6.5 is
also
installed, however I don't have 7.5 installed
- We tried to perform:
Exec sp_configure 'user connections', 25
Go
RECONFIGURE
Go

And then try to restart the sql server

- I was unable to execute the above steps as I was receiving
time
out
- Unable to stop/restart Sql server, I had to reboot to start
sql
server (I was being interrupted with the error message again)
- Check sql configuration parameters from EM, I checked:
1. "conn time out" : reasonable values for Min, Max and running
2. "worker threads": reasonable values for Min, Max and running
3. "user connections": reasonable values for Min, Max and
running
- Seems no problem with configuration parameters (the major
ones
related to the symptoms we have at least)
- Also we performed restar for sql server service through the
rebooting with no impact on the problem
- We tried to truncate the log file of the database as I
suspected
it
causes a problem, we performed the following procedure:
Backup LOG <your database name> with truncate_only
- Try to restart your sql server, no avail
- We checked scheduled tasks, as you mentioned that this
problem
started to appear three weeks ago and I noted that when I restart
the
sql
server or stop the clients the problem disappears but reoccurs each
Sunday,
we found one scheduled task which configured to run in the exact
same
time
(on
Sunday) however you added that restarting your server is no more
effective
to temporary solve the problem as before (and this is obvious
through
our
trials above to restart the server)
- We tried to remove that schedule task and then restart as it
might
be the cause of the problem
- I was unable to remove the scheduled task, and I received
another
error message related to Sql server!!
- While we were performing the above steps, I have been
interrupted
with the same error message while I am using the query analyzer
- The server looks to be in very unstable state, so I need some
recommendations to fix the problem as mentioned bove.


Waiting for any feedback recommended to fix the server problem.





.

Relevant Pages

  • Re: SQL server connection problem
    ... I've tried to change the user connections to 0, ... "SQL server connection time out. ... The following message appears when restart the server and before login ... I receive Error message: “A connection could not be established to ...
    (microsoft.public.sqlserver.clients)
  • Re: Classic ASP connectionstring to SQL Server 2005
    ... received an error message: ... database from an ASP to VB6 DLL to SQL Server 2K5? ... Connections option in the Database Engine node. ... Please reply to the newsgroup. ...
    (microsoft.public.inetserver.asp.db)
  • Re: SQL Server 2005
    ... procedure to increase the maximum number of concurrent connections. ... When you successfully connect to the instance of SQL Server 2005, ... I have an application that requires an database to be installed on the ...
    (microsoft.public.sqlserver.setup)
  • Re: TCPv4 Counters "Connetions Active" and "Connections Passive" on W2K3 IIS 6 S
    ... Active is the number of connections that are initiated by the system. ... For the SQL server some indications might be: ... values indicates that active queries are waiting for other queries. ... Also database size, queries and indexes can make huge differences. ...
    (microsoft.public.inetserver.iis)
  • Re: SQL server connection problem
    ... You can do that going to SQL Server Configuration Manager and go to ... changing Maximum concurrent connections value. ... found the error message was no more active for a long period before it ... The following message appears when restart the server and before login ...
    (microsoft.public.sqlserver.clients)