I know this is really awkward but for the last three days now at around 5:30
PM our two (NLB clustered) webservers have been unable to connect to our SQL
2005 SP2 server. The SQL server installation is configured in a failover
cluster. The webservers are running Windows 2003 Standard Edition SP2 with
MDAC 2.8 SP2 (each has 4 quad core Xeons and 3 Gb RAM). The servers are
running classic ASP websites and both servers exhibit the common error
messages to the visitors:
DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied
DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error
Rebooting both webservers resolves the problem. Another webserver running a
copy of the clustered websites, which is not used by the public, is still
able to access all the websites/databases that link to the SQL Server. We
don't think the problem is with the SQL Server set-up. When we failed over
from one to the other the problem persisted.
No changes or tasks have been made/added for months. Things have been
running smoothly for a while.
Nothing is logged in the event log on the webservers or the logs within SQL
Server. I don't know where to go next.
Does anyone have any advice?
Many thanks
Mike
I don't know where to go. Nothing is logged anywhere.
"Mike Wazowski" <bookham_meas...@yahoo.com> wrote in message
news:%231bzQ9v...@TK2MSFTNGP03.phx.gbl...
"Mike Wazowski" <bookham_meas...@yahoo.com> wrote in message
news:%23v2tFv8...@TK2MSFTNGP05.phx.gbl...
It will be interesting to hear if this works for you. I've not run into
the problem myself, but I'm sure it could crop up someday.
--
HTH,
Bob Barrows
"Bob Barrows" <reb0...@NOyahoo.SPAMcom> wrote in message
news:eDRT%23SF5J...@TK2MSFTNGP06.phx.gbl...