Re: MSDE KB829358 Update Repeats Indefinitely

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks Russ.

I was having a senior moment back there. While it is true that hacking the
registry makes it go away, I was a bit concerned about trashing a legitmate
key, and what the future ramifications of this might be.

Cheers,
Bill

"Russ Grover" <russ@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23P%23A12CAGHA.2148@xxxxxxxxxxxxxxxxxxxxxxx
> It's ok bill it's just one of those "Features"
>
> You actually don't have to delete the key, just manually install it and it
> works...
> (The automated part is the broken feature)
>
> Russ
>
> --
> Russ Grover
> Small Business IT Support
> SBS Rocks!
> Portland/Beaverton OR
> Email: Sales at SmallBusinessITSupport.com
> Website: http://www.SmallBusinessITSupport.com
>
>
> "Bill" <billyg1943@xxxxxxxxxxx> wrote in message
> news:u9CSHB7$FHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
>> OK. I confess. I already asked this question in this very newsgroup
>> and got an answer:
>>
>> As answered on another NG before by Wesley:
>>
>> Do you actually mean KB 829358 "Overview of the Critical Update for SQL
>> Server
>> 2000 Desktop Engine" [url]http://support.microsoft.com/?id=829358[/url] ?
>>
>> If so, try the following steps:
>>
>> Please either delete or modify the content of the ProductCode key in the
>> registry
>> for sharepoint, which can be found at:
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
>> Server\SHAREPOINT\Setup
>>
>> For example:
>>
>> 1. Delete the ProductCode key from
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
>> SQL Server\SHAREPOINT\Setup
>>
>> 2. OR a milder approach (probably less intrusive approach) is to change
>> the
>> content
>> of Product code from {65657C59-23A8-4974-B8E0-BA04EBD04E4F} to anything
>> else, for
>> my testing purposes, I changed it to
>> {65657C59-23A8-4974-B8E0-BA04EBD04E4F}INVALID
>>
>>
>>
>> Gruß,
>> Oliver Sommer
>> TrinityComputer.de
>>
>> Thanks again to Oliver!
>> Cheers,
>> Bill
>> "Bill" <billyg1943@xxxxxxxxxxx> wrote in message
>> news:OPXSTk5$FHA.1288@xxxxxxxxxxxxxxxxxxxxxxx
>>>I know I have seen something on this before but I can't find it anywhere!
>>>I apply the update and it appears to be successful but the nag pops up
>>>again in less than a minute.
>>> New installation of Window SBS 2003 Premium Edition with SQL 2000 and
>>> ISA 2000. SBS 2003 is patched to the max (but not SP1). I have not
>>> patched Exchange, SQL or ISA yet. Can someone please give me a clue?
>>> Cheers, Bill
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: VB ADO.NET Concurrency, Access, date fields and parameters
    ... Hi Bill, thank you very much for your help, it is much apreciated. ... >> I then edit a date in the grid. ... > Not sure what your update command looks like but that's the likely source. ... > There's no profiler that I konw of for Access, but if you ever use SQL ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MSDE KB829358 Update Repeats Indefinitely
    ... It's ok bill it's just one of those "Features" ... You actually don't have to delete the key, just manually install it and it ... > Do you actually mean KB 829358 "Overview of the Critical Update for SQL ...
    (microsoft.public.windows.server.sbs)
  • Re: Access vs. SQL
    ... William (Bill) Vaughn ... > book to help me in the SQL db design and VB integration? ... >> I think that JET databases are fine for home systems, ... >> Microsoft MVP ...
    (microsoft.public.vb.database)
  • Re: Passing IDs in SQL
    ... William (Bill) Vaughn ... This posting is provided "AS IS" with no warranties, and confers no rights. ... >> Let's see how you're setting up the SQL in code. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Passing IDs in SQL
    ... William (Bill) Vaughn ... This posting is provided "AS IS" with no warranties, and confers no rights. ... >> Let's see how you're setting up the SQL in code. ...
    (microsoft.public.dotnet.framework.aspnet)