Natively to SQL there shouldn't be any reason to involve IIS, however not knowing your
environment
it's hard to say. Is the client connecting via an browser interface? The possibilities
are nearly
endless...
Attached is an article that may help point you in the right direction.
http://support.microsoft.com/support/kb/articles/Q193/6/46.ASP
----- Original Message -----
From: "higginspi" <[EMAIL PROTECTED]>
To: "NT System Admin Issues" <[EMAIL PROTECTED]>
Sent: Friday, September 21, 2001 3:16 PM
Subject: IIS with SQL?
I have an NT server that I inherited about four months
ago (long story). It's sole purpose is to house a
database that is updated infrequently. There are a
very few people that connect directly to it maybe once
or twice a month. They are not users on the system.
Quite frankly, I have no idea about the mechanics of
how these people connect, but I assumed that IIS must
have something to do with the process. I shut down
IIS on Tuesday when Nimda was new. I had the patches
applied to IIS, so Nimda should not have effected me
anyway.
Anyway, there is never any information in the IIS log
files when a user connects to SQL. A user has
connected during the time that I have had IIS services
shut down. However, I get a constant error in the
system log that says with event ID 10005 --
DCOM got error, "The specified service is disabled and
cannot be started" attempting to start the service
IISAdmin with arguments "" in order to run server.
What does this error mean, and is there any reason for
me to run IIS for SQL connection? I would greatly
appreciate any help that anyone can give me.
Thank you,
Higgins
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger.
http://im.yahoo.com
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
