|
Home > Archive > MS SQL Server > November 2006 > SQL2005 using 100% CPU time and Droping Connections
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL2005 using 100% CPU time and Droping Connections
|
|
| Aris Basic 2006-11-10, 7:14 pm |
| From time to time (we couldnt fine the reason why)
SQLServer 2005 is using 100% of CPU time and all trying to conenct to it
come back with an error like this
A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL
Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error: 0 - An existing connection was forcibly
closed by the remote host.)
Also in SQL Server log we see this error:
LazyWriter: warning, no free buffers found.
now if we restart sqlserver (service) everything starts to work fine
until it decides to do the same thing again. (It may take days or weeks
for that to reappear again)
What could be a cause of this ?
| |
| John Bell 2006-11-10, 7:14 pm |
| Hi
Did you check out
http://forums.microsoft.com/MSDN/Sh...746299&SiteID=1
Are you on SP1?
You may also want to use SQL Profiler to try and determine if you have any
poorly performing queries.
John
"Aris Basic" wrote:
> From time to time (we couldnt fine the reason why)
> SQLServer 2005 is using 100% of CPU time and all trying to conenct to it
> come back with an error like this
>
> A connection was successfully established with the server, but then an
> error occurred during the pre-login handshake. When connecting to SQL
> Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections.
> (provider: TCP Provider, error: 0 - An existing connection was forcibly
> closed by the remote host.)
>
> Also in SQL Server log we see this error:
>
> LazyWriter: warning, no free buffers found.
>
> now if we restart sqlserver (service) everything starts to work fine
> until it decides to do the same thing again. (It may take days or weeks
> for that to reappear again)
>
> What could be a cause of this ?
>
|
|
|
|
|