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

Please call 1-800-936-4900 and open a case and ask to be routed to the
SQL-Public Team. There is no charge for this case as it has to do with a
Security Bulletin.

When you call please let them know that this has to do with Security
Bulletin MS08-040.

If they try to charge you, please let them know that there is free support
for any issues with Security Updates.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


mandoXXXFoo wrote:
> I'm having the same problem.
> My Summary.txt file says :
>
> Product : Database Services (SQLEXPRESS)
> Product Version (Previous): 3068
> Product Version (Final) :
> Status : NA
> Log File :
> SQL Express Features :
> Error Description : The edition of product instance SQLEXPRESS
> does not qualify for this update.

I tried this the first time I had an issue and it keeps coming back. Really
wish someone had a layman's solution.

"theloniouscoltrane" wrote:

> SOLUTION
>
> I got a hold of someone at Windows Live One Care and approached it as I
> didn't like the fact that my One Care sign was showing I needed to do an
> update.
>
> I use XP SP2. He figured out the problem immediately. Unless you have the
> business system or Win 2000, this update doesn't apply. The SQL server is
> something the rest of us don't even have.
>
> So, you click on the warning thing in your systray and when it comes up,
> pick advanced. On the following page, you'll see the program it wants to
> install. Uncheck that. Then I can't remember if it pops up later or if
> there's another check box, but you'll get a question along the lines of Do
> you want to... or maybe its a box that says Don't remind me. Anyway something
> that gives you the option of saying don't ever tell me I have to install this
> up date again. Click out and you're done.
>
>

I could probably figure this out too if it was explained in layman's terms.
Who wants to stay on the phone for three hours to fix this - if you're lucky.
I have a version that came bundled with third-party software I use in my
business but otherwise no nothing about it. The Windows Update support team
basically gives you the runaround. Come on Microsoft - take care of us.

If you're still having this problem perhaps post in the link below
will be of help to you. Basically if your right click on the "My
Computer" icon, then select "Manage" from the menu, and go to
"services" in the resulting window. Check to make sure the the SQL
services are enabled before you run the update.

http://groups.google.com/group/micro...66ee62ca974cc2

Mark wrote:
> I could probably figure this out too if it was explained in layman's terms.
> Who wants to stay on the phone for three hours to fix this - if you're lucky.
> I have a version that came bundled with third-party software I use in my
> business but otherwise no nothing about it. The Windows Update support team
> basically gives you the runaround. Come on Microsoft - take care of us.

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/SQLSer...dbackID=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.
>

I may have solved the problem of the Security update for SQL Server 2000 (KB
948110) not installing ---at least on this one computer. I found the culprit
to be UPS’s Worldship program. I uninstalled Worldship, rebooted; then also
uninstalled MS SQL server; rebooted; installed all updates; rebooted;
re-installed Worldship; rebooted; and all was fixed. No more messages about
a security update that needs to be installed. Hope this helps someone.



"Eric H" wrote:

> Security Update for SQL Server 2000 Service Pack 4 (KB948110) will not
> install. I have tried to install it 8 times and it fails every time. I have
> rebooted multiple times and it still fails. After failing, the Microsoft
> Update Icon reappears notifying be of an update to install.
>
> Running XP Pro with all updates to date (except this one).
> --
> Eric H

I would just like to confirm and thank this post and the link below as it was
really helpful and made for an easy quick fix to this problem especially for
someone not too tech savvy as myself and reccomend this to anyone else with
this same porblem just make sure you set both SQLAgent$MICROSOFTSMLBIZ, and
MSSQL$MICROSOFTSMLBIZ to manual and start the programs, then run update
again and it should work this time, hope this helped and thanks again to the
previous posts

P.S - On a side note here, not that it really matters just curious if anyone
knows why these programs were disabled inthe first place and if we should
still leave them running but anyways thank again

"robinson.tien@gmail.com" wrote:

> If you're still having this problem perhaps post in the link below
> will be of help to you. Basically if your right click on the "My
> Computer" icon, then select "Manage" from the menu, and go to
> "services" in the resulting window. Check to make sure the the SQL
> services are enabled before you run the update.
>
> http://groups.google.com/group/micro...66ee62ca974cc2
>

[benb449]

I am having the same issue with this update.
Benb449

xp pro

[benb449]

I just followed the google post and it reports that i have corrupt files.

any other ideas?

thanks for the help

benb449 wrote:
:: I am having the same issue with this update.
:: Benb449
::
:: xp pro
::
::
:: --
:: benb449
:: Posted via http://www.vistaheads.com


see: http://support.microsoft.com/kb/948110
Lists known issues and where to get help for this SP.
--

TaurArian [MVP] 2005-2009 - Update Services
http://taurarian.mvps.org
======================================
How to ask a question: http://support.microsoft.com/kb/555375
Disclaimer: The information has been posted "as is" with no warranties
or guarantees and doesn't give any rights. Computer Maintenance:
Acronis / Diskeeper / Paragon / Raxco