Hi Chris,
Your error message says that it can be caused by two reasons, either the
SQL Server was not found, or access was denied. The first thing we need to
find out is which one of these it is.
SQL Server has something called SQL Profiler. This is a monitoring tool
that you can use to troubleshoot. This tool should be able to tell you if
there was a request that was denied access.
You say that this is somewhat time related. That is, you need to restart
IIS, and then it will work for some time again. This makes me belive that
you have forgotten to close your connections. But you also say that you
have checked for this already.
--
Regards,
Kristofer Gafvert
<a style='text-decoration: underline;' href="http://www.gafvert.info" target="_blank">www.gafvert.info</a> - My articles and help
<a style='text-decoration: underline;' href="http://www.ilopia.com" target="_blank">www.ilopia.com</a>
Chris Keller wrote:
> Hello All,
>
> I'm looking for additional troubleshooting ideas on a persistant problem
> that is cropping up 'randomly' when a web service is communicating with
the
> SQL server.
>
> Both machines are running win2k Server with the most recent service
packs +
> .NET 1.1. The Web Service provides data to client software by connecting
to
> the SQL server and executing stored procedures. A fairly common scenario
I'd
> think.
>
> Anyway, at random points - or so far as we can determine, IIS reports
that
> access to SQL server was not found or access denied. This condition will
> persist until you restart IIS after which everything resumes working as
> expected.
>
> I've verified that the machines have the same mdac version, .net version,
> and we've even looked for stuck open connections. I've recently setup an
> entirely new domain with clean installs and the same behavior occured.
There
> are no error messages logged in SQL or IIS - or the event logs for either
> machine.
>
> Where else can I go with this? This feels like a fairly generic error and
> the apparent random nature hints that there is a specific set of
conditions
> that have to be met to repro the issue - but I can't identify them as
yet.
>
> Thanks for reading and a special thank you for your valuable time.
>
> Chris<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Frequent IIS restart required with web service / ado.net