Recurring SQLServer errors

[This followup was posted to microsoft.public.inetserver.asp.db and a
copy was sent to the cited author.]

Hi,

I have a W2k Server with SQLServer 2000 on it. Been using it for almost
3 years now to server a number of fairly small dynamic web sites.

All my site connection strings make DSN-less connections and SQLServer
has had Service Pack 3 installed a long time ago.

Just recently, I've stared getting recurring SQLServer errors.

They begin with several, but not always all, sites showing this error:

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.

Even though they worked fine minutes earlier. At this point I go in and
restart the SQL service, but it only seems to fix a few sites, while
others then return this error:

"SQL Server does not exist or access denied"

It's fixed when I remotely reboot the server, but I'd prefer to stop
this from happening altogether.

Suspiciously, it happened at exactly the same time today as it did last
week: just before 5 p.m. on Thursday (and once in between). But the
event log doesn't show anything suspicious regarding SQL Server (I do
get a lot of netlogon errors there, however) and there are no processes
that I'm aware of scheduled to run at that time.

Since this started I've been going through and changing all my
connection strings to look for the server at 127.0.0.1 instead of the IP
address and explicitly stating the UID and password, but most sites
seemed to work fine for a few years without those in the connection
string.

Could it be there is a limit to simultaneous anonymous connections that
didn't rear its head earlier? The server is getting more traffic
recently.

Thanks.

Re: Recurring SQLServer errors

Travis Pupkin wrote:
> [This followup was posted to microsoft.public.inetserver.asp.db and a
> copy was sent to the cited author.]
>
> Hi,
>
> I have a W2k Server with SQLServer 2000 on it. Been using it for
> almost 3 years now to server a number of fairly small dynamic web
> sites.
>
> All my site connection strings make DSN-less connections and SQLServer
> has had Service Pack 3 installed a long time ago.
>
> Just recently, I've stared getting recurring SQLServer errors.
>
> They begin with several, but not always all, sites showing this error:
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'NT AUTHORITY\ANONYMOUS LOGON'.

Flag #1
Instead of ODBC, you should be using the native SQL Server OLEDB provider
(SQLOLEDB - see www.able-consulting.com/ado_conn.htm for examples)

>
> Even though they worked fine minutes earlier. At this point I go in
> and restart the SQL service, but it only seems to fix a few sites,
> while others then return this error:
>
> "SQL Server does not exist or access denied"
>
> It's fixed when I remotely reboot the server, but I'd prefer to stop
> this from happening altogether.
>
> Suspiciously, it happened at exactly the same time today as it did
> last week: just before 5 p.m. on Thursday (and once in between). But
> the event log doesn't show anything suspicious regarding SQL Server
> (I do get a lot of netlogon errors there, however) and there are no
> processes that I'm aware of scheduled to run at that time.
>
> Since this started I've been going through and changing all my
> connection strings to look for the server at 127.0.0.1 instead of the
> IP address and explicitly stating the UID and password, but most sites
> seemed to work fine for a few years without those in the connection
> string.
>
> Could it be there is a limit to simultaneous anonymous connections
> that didn't rear its head earlier? The server is getting more traffic
> recently.
>
> Thanks.

Are you explicitly closing and destroying your connections? Failure to do so
is one way to stop connection pooling from working, which is one of the
possible causes of the problems you are experiencing:

http://support.microsoft.com/default.aspx?scid=kb;en-us;3284 76


Another way to disable pooling is the failure to use explicit connection
objects:
http://support.microsoft.com/?kbid=271128

Some more info about pooling:
http://msdn.microsoft.com/library/en-us/dnmdac/html/pooling2 .asp
http://support.microsoft.com/?scid=kb;en-us;Q176056
http://support.microsoft.com/default.aspx?scid=kb;en-us;1915 72

Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Recurring SQLServer errors

In article , reb01501
@NOyahoo.SPAMcom says...
> Flag #1
> Instead of ODBC, you should be using the native SQL Server OLEDB provider
> (SQLOLEDB - see www.able-consulting.com/ado_conn.htm for examples)
>


Thanks for the tip (above) and the links on pooling. I was closing and
emptying all of my record sets, but was leaving my connections open,
probably causing a pooling problem and the subsequent authentication
errors.

Very helpful.

Thanks.