December 19, 2005 at 12:37 pm
I have a client with a SQL Server implementation that started giving us fits a couple of weeks ago.
When trying to connect through anything, the users are unable to connect. Whether through an ASP page, Query Manager, Enterprise Manager or SQL Profiler, nothing is able to connect.
The ASP application reports the following error. The SQL Server tools report the following error:
[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error
The database is running, I can go into Task Manager on the server and see the process running. It is using about 2Gig of memory. The only way I can resolve the error is to stop and restart SQL Server using the icon in the system tray, stopping and starting the service. There is nothing in the logs indicating an issue, and if I run the profiles, nothing is there either.
Anyone have an idea what could be causing this?
December 20, 2005 at 7:51 am
December 20, 2005 at 8:30 am
Is the certificate installed for SQL Server now expired? How about the certificate for the CA that issued that certificate?
K. Brian Kelley
@kbriankelley
December 22, 2005 at 5:55 am
Something I did omit, there isn't a secure certificate installed on the server. This isn't a secure site, it's an internal intranet site.
The lockup doesn't occur with everyone, it only occurs at some point after the server had been running for a while. Sometimes for weeks, sometimes a few days. The latest was a day and a half before it locked up again. But when it occurs, it locks up the DB and no one can access the database server.
January 20, 2006 at 10:27 am
I have a similar problem on a client server - after a couple of days the connections to SQL Server 2000 become very slow and start to fail. When this happens the @@Connection count is about 30k but sp_who only shows about 70 active connections. A stop and restart of SQL Server clears the problem. The server OS is Windows 2000 Server.
We have temporarily got round the problem by scheduling a stop/start for 3am each day but we would like to know why we get the slow down.
The SQL databse is being accessed by about 20 workstations with Access XP and VB6 code using ADO to run parameter driven SP's to perform data updates. A few of the Access users have SQL tables open behind Access forms but most are disconnected or using temporary local tables of relevant data.
I have noticed that Connection "pooling" is off on this server - could this be a factor? Is the problem with connections down to the OS and not SQL Server?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply