| Re: Security Update for SQL Server 2005 Service Pack 2 (KB948109) |
|
 |
|
 |
|
 |
|
 |
Group: microsoft.public.sqlserver.setup · Group Profile
Author: Robert AldwinckleRobert Aldwinckle Date: Aug 5, 2008 11:32
(cross-post added to SQL Server Setup)
"Chris Foster" discussions.microsoft.com> wrote in message
news:8ABC8CB3-4046-4FC0-8043-C5E11F4A1ACF@microsoft.com...> This patch has been a source of frustration for several weeks since my system
> always wants to install it and never can. My SQL directory is not compressed
> so that suggestion isn't going to help.
Are you seeing hex code 0x6D9E as well?
Try searching for additional diagnostics
using the decimal equivalent (28062)?
> How about a patch that we can install
> ourselves so we are not treated like a bunch of mushrooms?
The solution for many of these codes seems to depend on how
the product was initially installed and whether access to the original
install files is still available by the same user.
> Or just correct
> thiss self installing update because it is obvious a lot of users are having
> issues here.
I've been wondering how many of these users actually need SQL at all.
If they don't use it perhaps it would be best if they simply uninstalled
the product completely?
Good luck
Robert Aldwinckle
---
>
> -Chris
>
> "I.R." wrote:
>
>> Since a week ago .
>> Every time I tried to install Security Update for SQL Server 2005 Service
>> Pack 2 (KB948109) an error message is appear " Some updates were not install"
>> and Error found : Code 6D9E and the Get help link is not helpful.
>>
>>
| 
