Re: Udpate KB948109   

(cross-post added to  SQL Setup)
"Domski100"  wrote in message news:59AB5D0F-92C9-4CDA-8863-578497A76221@microsoft.com...
>I have been having the same issues for days now. I started a support incident
> request as suggested but got an email back suggesting I look on this
> newsgroup for a solution!
>
> I am getting Error code 64C.


That's obviously a hexidecimal value (e.g. note the C).
So the decimal equivalent of it is 1612  (according to calc.exe)


>
> I also went into and got the summary as someone suggested and the message was:
>
> Product                   : SQL Server Database Services 2005 (MSSMLBIZ)
> Product Version (Previous): 3042
> Product Version (Final)   :
> Status                    : Failure
> Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log
> SQL Express Features      :
> Error Number              : 1612
> Error Description         : Unable to install Windows Installer MSP file
>
> Any ideas on how to resolve this would be very welcome!


FWIW that looks to me to be a very generic code, suggesting that earlier
in your (verbose) log you would find a more specific symptom to try to diagnose.

Try a web search?

Well, I can't find much regarding this specific update
but following  Susan's  suggestion to treat your updates
like service packs we can find

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3196163&SiteID=1
(Live Search for
    2008  SQL update 1612  verbose  MSFT  site:microsoft.com
)

which shows an example of where my guess would have been correct.

BTW  notice that all the hits in the above search were from  MS forums.
I think that at least some also correspond to MS NNTP newsgroups.
Cross-posting to one for convenience.   I suspect you are more likely to get
more knowledgeable help from one of those than from the WU NG.


Good luck

Robert Aldwinckle
---


>
> Thanks
>
>
>
> "PA Bear [MS MVP]" wrote:
>
>> See this discussion for some insight:
>> http://msmvps.com/blogs/bradley/archive/2008/07/15/the-mess-of-the-sql-patches.aspx
>> -- 
>> ~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/
>>
>> Adrian wrote:
>> > I'm having the same problem. I just opened an support incident, and I'll
>> > report back if I hear anything useful.
>> >
>> > As far as I can tell, the path is applied correctly, but it's not being
>> > detected as applied the next time because something is configured
>> > incorrectly in SQL Server.  I've never used SQL Server, but it comes with
>> > Visual Studio. (The last time I used SQL, it was 1990, and I was running
>> > Ingres on a VAX/VMS workstation.)
>> >
>> > I tried opening the SQL Server Configuration Manager, but that fails with
>> > "Cannot connect to WMI provider.  You do not have permission or the server
>> > is unreachable.  Note that you can only [sic] manage SQL Server 2005
>> > servers
>> > with SQL Server Configuration Manager.  Initialization failure
>> > [0x80041014]". I suspect that whatever is causing this problem is also
>> > preventing the update detector logic from recognizing that the patch has
>> > already been applied.
>>
>>

date: Sat, 19 Jul 2008 19:50:20 -0400   author:   Robert Aldwinckle