Re: Security Update for SQL Server 2000 Service Pack 4 (KB948110)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I'll try to put in an "English" version. There are two different methods to
log into SQL Server. One is the one we are all familiar with - it is related
to our user name and password when we log into our machine (called Windows
Authentication) The other is SQL Authentication where, if the given database
is configured to use this authentication, there exists a superuser who can do
anything on that database server if they have the correct password (SA
Password). Apparently, the 948110 hotfix will not work on a database server
where there is either no sa password given (which is the case for the
SBSMonitoring and MSFW instances on Small Business Server).

What he suggests is to switch the authentication method of the database to
SQL authentication long enough to 1) create an sa password or if none is
available, use an account with sa privilege and 2) provide that privelege to
the BUILTIN\Administrator account and 3) switch authentication from the SQL
mode to the Windows Authentication mode and 4) run the update, and 5) undo
this.

I'm a bit confused because I think that switching to SQL Authentication and
providing JUST a password and running the update is not sufficient but that
this can also work provided the password is strong enough.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=357228

You may be able to infer the fix from the next link although I would agree
with the MVP that you may as well get help directly from Microsoft for this
issue - caveat - your server must be down and causing a work stoppage for
free support otherwise, it may be a pay event. I have also seen that it is
refundable if this issue is Windows Update related. I made a request to the
team to clean up the information on the website below to make it easier to
understand what is needed to fix the issue without making it worse first.

http://support.microsoft.com/kb/948110/

--
Regards,
Jamie


"theloniouscoltrane" wrote:

While I appreciate the work that PsychBiller did in transcribing his fix, he
could have said in Romanian and it wouldn't have been any more difficult to
understand.

Is there anyone out there who knows the solution and can explain it to
non-geeks.


"PsychBiller" wrote:


I just spent 3 hours on the phone with Microsoft tech support to
resolve this.

.



Relevant Pages

  • RE: Confusion on standard security methodologies.
    ... Application will talk to a back-end SQL ... By "back-end," I assume you mean on a different box from IIS? ... If SQL is on a separate box, you won't be able to use NT authentication ... impersonations (meaning that once passed to the IIS server, ...
    (microsoft.public.inetserver.iis.security)
  • Re: IIS6 Authentication Problem with SQL Server 2000
    ... They're not accessing SQL directly right? ... > a) if you are using a Windows 2000 Domain, ... > backend SQL Server. ... You need to use Kerberos authentication for this (not ...
    (microsoft.public.inetserver.iis.security)
  • Re: iis problems with some xp clients - kerberos issue?
    ... is the browser even attempting Kerberos Authentication? ... the webserver failing to get a service ticket for the SQL Server etc. ... Check that the site is in IE's Intranet zone (IE doesn't attempt to Kerberos ... Both access SQL ...
    (microsoft.public.inetserver.iis.security)
  • Re: Cached Logon
    ... It appears that the IIS and the SQL are installed on one machine? ... the scenes" windows authentication information? ... The folder on IIS holds all 3 .asp files. ... On the server I was logged in as domain1\administrator. ...
    (microsoft.public.windows.server.general)
  • Re: Cached Logon
    ... It appears that the IIS and the SQL are installed on one machine? ... the scenes" windows authentication information? ... The folder on IIS holds all 3 .asp files. ... On the server I was logged in as domain1\administrator. ...
    (microsoft.public.sqlserver.connect)