Could possibly be linked to your licence and available concurrent
database connections.
Check your transaction and locking code and also take heed of Micro$ofts
recent security bulletin for securing IIS. You might be being fired upon by
denial of service attacks.
-Original Message-
Mike,
Check your SQL Connection setting. It looks like it is using [Named Pipes].
Try changing to TCP/IP.
Jeff Craig
- Original Message -
From: Mike Connolly [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, August 16, 2001 5:06 AM
Subject: Strange ODBC Error
Fellow
Hi Mike;
We would get that error whenever the connection to our SQL database failed,
like is someone decided to reboot the database server while the site was
still running.
Melanie
-Original Message-
From: Mike Connolly [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 16, 2001 6:07 AM
this. All assuming your SQL server is set up to talk tcp/ip..
-Original Message-
From: Melanie Maddix [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 16, 2001 8:33 AM
To: CF-Talk
Subject: RE: Strange ODBC Error
Hi Mike;
We would get that error whenever the connection to our SQL database
change your default Network protocol to TCP/IP in the SQL Server Client Config
The named-pipes protocol does more than just shift data from A to B, it has
some security mechanisms too. Any breaks in the network traffic between
your web server and database can cause errors like this.
Mark
5 matches
Mail list logo
