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

[INO]

I am having the same problem with SQL Server 2005 service Pack. Everytime
I've tried to install it - it says "some items could not be stalled". If you
get any suggestions could you pass them on? Thanks. INO

"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

[K.@discussions.microsoft.com Matt K.]

I am having the identical problem with this update install failing on my
computer.

I have another computer in the house which also received this morning's set
of updates -- but KB948110 is not in the list of installed updates -- and so
it did NOT fail. Why are some computers in my house getting this update --
and some are not?

Matt

[Eric H]

[Jimmy]

Same problem here...add me to the list

[M@discussions.microsoft.com Bill M]

Same problem. I'm getting a 0x643 error message. Have tried the cumulative
hotfix "SQL2000-KB916287-v8.00.2187-x86x64-ENU.exe" but continue to have
problem. The Update Icon is starting to become very annoying...

[pcoats]

This update is also trying to install where an SQL 2000 database once was. I
have 2 servers that had MSDE and SQL 2000 on them at one time and has since
been removed. This update is still trying to install but is failing.

[ClausN]

Same problem.
W2K3 Server R2 E x64 E SP2.
No problems with updates until now.
Installing SQL2000-KB948110-v8.00-x86x64-ENU.exe seems to work.
Manually installed updates does not affect Windows Update History.
Perhaps there is a trick to tell Windows Update about manually installed
updates?
Querying Add/Remove Programs tells me about 2 SQL-Hotfixes:
Hotfix 1101 for SQL Server 2000 x64 ENU (KB913100)
Hotfix 2050 for SQL Server 2000 ENU (KB948110)
May be the Windows Update symbol in the task bar will leave when you
deselect the update within Microsoft or Windows Update. But in my
opinion it is not a correct solution, only for the systems which do not
need the patch (see other answer within this discussion).

Sorry about my plain english

Claus N.

[theloniouscoltrane]

Ditto

[Leo the Lionhearted]

I have the same problem. I do not see a solution posted.
Leo
--
Good Selling

[PA Bear [MS MVP]]

keep reading...

Leo the Lionhearted wrote:
> I have the same problem. I do not see a solution posted.
> Leo
>

[PsychBiller]

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

The patch installation uses the SQL SA user, which has sysadmin
privileges. If you download and attempt to install the patch manually,
you get a dialog box where you are asked to enter the SA
password.

My SQL Server 2000 installation is the MSDE version bundled into
a commercial product. The developers of the product will not tell the
purchasers what the SA password is, and for good reason. Users could
do some serious damage to the product's underlying database.

If you don't know the SA password, what can you do?

The manual installation gives you the option of logging on with
Windows Authentication instead. It will look in the SQL installation to
see if your Windows user ID has SQL sysadmin privileges. My user ID
has Windows Administrator privileges, so it is automatically included
in the SQL "BUILTIN\Administrators" group. But the developers of the
commercial product had removed sysadmin privileges from the SQL
"BUILTIN\Administrators" group as another way to protect the
database.

The Microsoft rep used the OSQL utility, available even in the
MSDE version, to logon to the server with my Windows user ID. The
command for that is:

C:\>OSQL -S COMPUTER-NAME\SQL-SERVER-NAME -U WindowsID -P
WindowsPassword

Next, we looked for SQL users that had sysadmin
privileges:

1> exec sp_helpsrvrolemember 'sysadmin'
2> go

I was very, very lucky that the list returned by this command
included another user I recognized as part of the commercial product,
AND I knew how to get the password for it. By the way, "exit" is how to
get out of the OSQL utility.

We logged back on to the server with OSQL using that SQL user I
recognized:

C:\>OSQL -S COMPUTER-NAME\SQL-SERVER-NAME -U SQLUser -P
SQLPassword

Now we could give my Windows user ID the sysadmin privilege (the
single quotes are required):

1> exec sp_addsrvrolemember
'COMPUTER-NAME\WindowsUser','sysadmin'
2> go
''COMPUTER-NAME\WindowsUser' added to role 'sysadmin'.

Finally, we ran the patch installation again and this time, just
clicked Next to accept the default authentication, which is Windows,
not SQL. It worked! The patch installed. No special command line
switches were necessary; I just typed the name of the file I
downloaded.

I didn't want to leave that security window open, so I used OSQL
to remove the sysadmin privilege from my Windows user when I was
finished (the single quotes are required):

1> exec sp_dropsrvrolemember
'COMPUTER-NAME\WindowsUser','sysadmin'
2> go

I haven't had good experiences with Microsoft support in the
past, but this representative did an excellent job. He was located in
India, but his English, troubleshooting skills, and product knowledge
were refreshingly good. And he used his real name!

--
PsychBiller
Posted via http://www.vistaheads.com

[shoneinc]

I also have the same problem. No solution is posted.

[PsychBiller]

Did you try what worked for me?

http://tinyurl.com/5merew

[shoneinc]

I didn't try as I have no idea what "patch installation you sugested let
alone a request for the SQL SA user, which has sysadmin privileges. If you

download and attempt to install the patch manually, you get a dialog box
where you are asked to enter the SA password."

[Dad@discussions.microsoft.com Benny's Dad]

My experience is same as Ric H. I don't talk technical shorthand. At this
point I just want the Update Icon to go away until MS sends a fix that works
without operator intervention.

[shoneinc]

Yes – I am in total agreement with Benny’s Dad.

[Kodiak_ABA]

Has anyone come accross a FIX for installing SQL Server 2000 Service Pack 4 (KB948110)?

--
Free News Reader
http://put.hk
http://put.hk/reader/news.microsoft.com/microsoft.public.windowsupdate.html

[theloniouscoltrane]

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.

[theloniouscoltrane]

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.

[mandoXXXFoo]

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.

--
mandoXXXFoo
Posted via http://www.vistaheads.com

[PA Bear [MS MVP]]

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/

[Cark69]

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

[Mark]

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.

[robins...@gmail.com]

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/microsoft.public.windowsupdate/browse_thread/thread/6380b0a40889e4f8/f666ee62ca974cc2?lnk=st&q=Security+Update+for+SQL+2000+Service+pack+4#f666ee62ca974cc2

[thejamie]

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

[djgeddis]

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.

[Newbie04]

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

[benb449]

I am having the same issue with this update.
Benb449

xp pro

--
benb449
Posted via http://www.vistaheads.com

[TaurArian]

benb449 wrote:
:: I am having the same issue with this update.

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

[Annoyed]

I am having the same problem with my WXP SP3 Pro system.

The product instance SQLTools has had update 2273 applied. You cannot
install GDR update 2050 overtop update 2273. An update of build equal to or
greater than 2273 should be downloaded.

I tried to log a support call but I need to call back during business hours.