Event ID: 17055 Source: MSSQLSERVER Type: Information Login failed

I am having a problem with one of the website we host that accesses an
SQL2000 database. Every so often I get the above mentioned event in the
App. log accompanied by a error reported by the users browser stating
that the login failed for IUSR_xxxxxx. If I log into the server having
the problem and log out the problem resolves itself. I tried using
Profiler to see if I could see any odd activity and there was no
activity what so ever while the problem persisted. Once the problem
corrected by the login/logout I saw normal activity resume in Profiler.
The only this I noticed different after the login/logout fix was that
the network protocol: Named Pipes actioned appeared to be showing up in
Profiles where it was not before. I have checked all my permissions and
everything seems to be in order(especially since the login/logout seems
to resolve it). Any ideas as to what is causing this?
Thank you in advance,
Ethan Cottrell
Structured Business SystemsBased upon your description, it sounds like you're requesting a Windows
Authenticated connection from the web server, and
it is authenticating using the IUSR account. This account doesn't exist on
the SQL Server , so it fails.
If you then login to the server using Named Pipes, you've authenticated
yourself and any new sessions will piggy-back on this.
If you then check for successfull logins at the server, does it show that
IUSR connected successfully or your domain account?
These two articles may give you a better understanding as well.
332167 IIS 6.0: HOW TO: Configure IIS to Control the Anonymous Password
http://support.microsoft.com/?id=332167
229286 FP2000: Cannot Connect to SQL Database on Windows NT Server Computer
http://support.microsoft.com/?id=229286
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
I already had added the IUSR account to SQL and gave it permissions on
the database. Any pages on the site that do not require a connection to
the database are fine, it is only those ASP pages that connect to the
database that are having this problem. When I use Profiler I can see
that the IUSR account has no problems logging in when there is no
problem, but once the problem occurs the IUSR account activity stops and
is replaced by the NT AUTHORITY/ANONYMOUS or something like that.
I think I may have resolved this issue already, but I am keeping an eye
on it. I forgot to mention earlier that the database in question is
accessing data on a linked server also, and I think that may have been
the source of my problem. We had recently installed a new server (server
B) with a different host name from the original. Server A is where the
website and it's database exist and server B is where the database with
additional data exists (it is the primary db for another site). I added
the old server b's host name to DNS to hopefully eliminate and potential
problems, but that may not have been the case. I have since removed all
linked servers and remote servers and recreated them in both instances
of SQL using the correct host name and am using the sa account to
authenticate between them. Does that sound like it could have been the
source of the problem?
Thank you for your response,
Ethan Cottrell
Structured Business Systems
Kevin McDonnell [MSFT] wrote:
> Based upon your description, it sounds like you're requesting a Windows
> Authenticated connection from the web server, and
> it is authenticating using the IUSR account. This account doesn't exist o
n
> the SQL Server , so it fails.
> If you then login to the server using Named Pipes, you've authenticated
> yourself and any new sessions will piggy-back on this.
> If you then check for successfull logins at the server, does it show that
> IUSR connected successfully or your domain account?
>
> These two articles may give you a better understanding as well.
> 332167 IIS 6.0: HOW TO: Configure IIS to Control the Anonymous Password
> http://support.microsoft.com/?id=332167
> 229286 FP2000: Cannot Connect to SQL Database on Windows NT Server Compute
r
> http://support.microsoft.com/?id=229286
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||DNS issues could certainly cause a problem from the web server to the
database.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.