RE: KB928365 Err 663, on production SQL2K5 serve CANNOT uninstall

The file name is always different but it's an MSI and the properties are:

Title: Installation Database
Subject: Microsoft .NET Framework 2.0
Revision: {BFC5E8EF-C140-454A-9B47-EEC73A4AAB3F}
Size: 2060 KB

The exact file name is recorded at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\D6461317C3DC4F04799BDCE9E42626FE\InstallProperties\LocalPackage

so if all else fails, you could find the MSI file with those properties on
another Win2003 server, copy it to your affected server
(c:\windows\installer) and rename it to whatever that registry key shows on
the affected server...

Adrian






"Pazu" wrote:

Hello,

There is a seed of truth in your idea, because I moved the files, from which
W2K3 server and SQL server, where installed form C: to D: - but these are
normal setup files copied form CDs.

Anyway I never touched directory C:\Windows\Installer, it exists and it
looks to contain a lot of GUID-named folders and some hexa named MSIs. I
compared with another server and there is much more msi and even msp files,
however their hexa names seem to be machine-specific.

Any idea how to determine which "hexa".msi are missing ?

Thanks - Jiri

"Adrian" wrote:

I had the same issue, and was totally unwilling to uninstall SQL 2005, .NET
etc. and reinstall just to get the patch to work.

But I found the cause, and a non-destructive fix.

Basically, .NET, SQL 2005, Visual Studio, MSXML and many other packages that
use Windows Installer tend to drop MSI and MSP files in C:\Windows\Installer.

Updates to such packages often seek the original files in this folder.
The .NET 2.0 patch q928365 is one such update.

But these files can be rather large and you can end up with a lot of them,
and if the C: drive gets full, some people identify this folder as using a
lot of space and figure correctly that .MSI and .MSP files are not required
for any existing software to run, so they are safe to delete...

On my server, the MSP & MSI files had been moved to another drive, and if
you hover the mouse over them or right-click and select properties, summary,
it tells you what each was for.

I just copied all the MSI and MSP files that identified themselves as
relating to .NET back to C:\Windows\Installer and reran the patch, and it
worked, no problems.


.

Relevant Pages

  • Re: New Windows 2003 Cluster - MSI īs are not applied
    ... The assignment of application Previous Versions Client from policy Software ... I have taken a brand new msi, which was not install in the past on this ... 2000 Server, where the old Enterprise MSI´s lied. ... The installation of application Software_XY of the ...
    (microsoft.public.windows.group_policy)
  • Re: Installation von "Installation Manger" @ Citrix MPS 3.0 enterprise Edition
    ... "Robert Denker" schrieb: ... der Installation dennoch den Server bzgl. späterer Updates, d.h. das MSI ... mindestens einen weiteren Server und deinstalliere dann den MPS. ...
    (microsoft.public.de.german.windows.terminaldienste)
  • RE: KB928365 Err 663, on production SQL2K5 serve CANNOT uninstall
    ... version of the patch that includes whatever content might ... another Win2003 server, copy it to your affected server ... compared with another server and there is much more msi and even msp files, ...
    (microsoft.public.windowsupdate)
  • Re: uninstall web application failed
    ... Does the uninstall works fine before you modify the MSI with Orca? ... The installation of the Kit on a Windows 2003 server works fine. ...
    (microsoft.public.dotnet.framework.setup)
  • Re: ASP.NET Deployment...
    ... By using MSI of installation of your web application, ... to/from the web server. ... > In previous jobs I've always used straight xcopy to publish to production ...
    (microsoft.public.dotnet.framework.aspnet)
Loading