"Alan Z. Scharf" <ascharf@grapevines.com> wrote in message
news:ugQV%23gLiFHA.3164@TK2MSFTNGP15.phx.gbl...
> uninstall and reinstall VS 2003.
>
> Program installer does not show up in Add/Remove programs or
> Windows\Installer cache.
>
> When I try to run setup program from disk, either repair or uninstall, I
> get
> two messages:
>
> 1. Setup is unable to find baseline data.
> 2. [07/14/05,16:55:44] Visual Studio .NET Enterprise Architect 2003 -
> English:
>
> [2] ERROR_FILE_NOT_FOUND returned in CRootComponent::Install; could not
> find
>
> file: D:\WINDOWS\Installer\8222e.msi
>
> Is it possible to get the 8222e.msi file from somewhere?
>
>
>
> Is there anything in the registry that I could clear out that would allow
> Install to proceed?
>

"Peter van der Goes" <p_vandergoes@toadstool.u> wrote in message
news:e$AGUfUiFHA.3164@TK2MSFTNGP15.phx.gbl...
>
> "Alan Z. Scharf" <ascharf@grapevines.com> wrote in message
> news:ugQV%23gLiFHA.3164@TK2MSFTNGP15.phx.gbl...
> > uninstall and reinstall VS 2003.
> >
> > Program installer does not show up in Add/Remove programs or
> > Windows\Installer cache.
> >
> > When I try to run setup program from disk, either repair or uninstall, I
> > get
> > two messages:
> >
> > 1. Setup is unable to find baseline data.
> > 2. [07/14/05,16:55:44] Visual Studio .NET Enterprise Architect 2003 -
> > English:
> >
> > [2] ERROR_FILE_NOT_FOUND returned in CRootComponent::Install; could not
> > find
> >
> > file: D:\WINDOWS\Installer\8222e.msi
> >
> > Is it possible to get the 8222e.msi file from somewhere?
> >
> >
> >
> > Is there anything in the registry that I could clear out that would
allow
> > Install to proceed?
> >
> Try following the instructions here:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;824642
>
> for manual uninstall. Complete all steps even if you get indications that
> one or more steps did not work. That *should* give you a clean slate for
an
> installation. In rare cases, I have had to also manually remove references
> to "visual studio" and ".net" from the registry (all the usual cautions
> about editing the registry apply!).
>
> --
> Peter [MVP Visual Developer]
> Jack of all trades, master of none.
>
>

"Alan Z. Scharf" <ascharf@grapevines.com> wrote in message
news:ugQV%23gLiFHA.3164@TK2MSFTNGP15.phx.gbl...
> uninstall and reinstall VS 2003.
>
> Program installer does not show up in Add/Remove programs or
> Windows\Installer cache.
>
> When I try to run setup program from disk, either repair or uninstall, I
> get
> two messages:
>
> 1. Setup is unable to find baseline data.
> 2. [07/14/05,16:55:44] Visual Studio .NET Enterprise Architect 2003 -
> English:
>
> [2] ERROR_FILE_NOT_FOUND returned in CRootComponent::Install; could not
> find
>
> file: D:\WINDOWS\Installer\8222e.msi
>
> Is it possible to get the 8222e.msi file from somewhere?
>
>
>
> Is there anything in the registry that I could clear out that would allow
> Install to proceed?
>
>
>
> Thanks.
>
>
>
> Alan
>
>
>
>

"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:ujJlyVXiFHA.2904@tk2msftngp13.phx.gbl...
> That 8222e.msi file is the cached MSI file for a product. It's required
for
> the uninstall (and any repair etc etc) and is not supposed to be removed.
> Step 1 in the manual uninstall in that previously mentioned kb article
uses
> that cached MSI file, so that won't work for your missing one.
Incidentally,
> msizap will remove the Windows Installer references to those installed
> products but it doesn't remove the files.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Alan Z. Scharf" <ascharf@grapevines.com> wrote in message
> news:ugQV%23gLiFHA.3164@TK2MSFTNGP15.phx.gbl...
> > uninstall and reinstall VS 2003.
> >
> > Program installer does not show up in Add/Remove programs or
> > Windows\Installer cache.
> >
> > When I try to run setup program from disk, either repair or uninstall, I
> > get
> > two messages:
> >
> > 1. Setup is unable to find baseline data.
> > 2. [07/14/05,16:55:44] Visual Studio .NET Enterprise Architect 2003 -
> > English:
> >
> > [2] ERROR_FILE_NOT_FOUND returned in CRootComponent::Install; could not
> > find
> >
> > file: D:\WINDOWS\Installer\8222e.msi
> >
> > Is it possible to get the 8222e.msi file from somewhere?
> >
> >
> >
> > Is there anything in the registry that I could clear out that would
allow
> > Install to proceed?
> >
> >
> >
> > Thanks.
> >
> >
> >
> > Alan
> >
> >
> >
> >
>
>

"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:ujJlyVXiFHA.2904@tk2msftngp13.phx.gbl...
> That 8222e.msi file is the cached MSI file for a product. It's required
for
> the uninstall (and any repair etc etc) and is not supposed to be removed.
> Step 1 in the manual uninstall in that previously mentioned kb article
uses
> that cached MSI file, so that won't work for your missing one.
Incidentally,
> msizap will remove the Windows Installer references to those installed
> products but it doesn't remove the files.
> --
> Phil Wilson [MVP Windows Installer]
> ----

"Alan Z. Scharf" <ascharf@grapevines.com> wrote in message
news:%23AcU4Y1iFHA.1148@TK2MSFTNGP12.phx.gbl...
>
>
> Phil,
>
> Thanks for your reply.
>
> Where can I get the 8222e.msi file?
>
> I searched for it on:
>
> VS 2003 CD
> Win 2003 CD
> Installer Cache (Start, Run, Installer)
>
> Any other way around this without that file?
>
> Thanks again.
>
> Alan
>
>
>
> "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
> news:ujJlyVXiFHA.2904@tk2msftngp13.phx.gbl...
>> That 8222e.msi file is the cached MSI file for a product. It's required
> for
>> the uninstall (and any repair etc etc) and is not supposed to be removed.
>> Step 1 in the manual uninstall in that previously mentioned kb article
> uses
>> that cached MSI file, so that won't work for your missing one.
> Incidentally,
>> msizap will remove the Windows Installer references to those installed
>> products but it doesn't remove the files.
>> --
>> Phil Wilson [MVP Windows Installer]
>> ----
>
>

"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:uojT8X9iFHA.2644@TK2MSFTNGP09.phx.gbl...
> You can't get it - I'm unsure of the algorithm used to create it.
>
> Try this at your own risk:
>
> Copy the MSI file for the product as 8222e.msi into the winows\Installer
> folder. Make sure you get the right MSI file - it sounds like it's your VS
> .NET MSI file. Then see what happens when you try to uninstall. That
cached
> MSI file is the "same" as the original except that it doesn't contain cab
> files. I just tried this on a simple MSI file - I installed it, deleted
the
> cached MSI file in Windows\Installer, renamed the original MSI file so it
> couldn't find it. I got the error dialog at uninstall time. Then I copied
> the original MSI file to the Installer folder and renamed it to the cached
> name, and it uninstalled ok.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Alan Z. Scharf" <ascharf@grapevines.com> wrote in message
> news:%23AcU4Y1iFHA.1148@TK2MSFTNGP12.phx.gbl...
> >
> >
> > Phil,
> >
> > Thanks for your reply.
> >
> > Where can I get the 8222e.msi file?
> >
> > I searched for it on:
> >
> > VS 2003 CD
> > Win 2003 CD
> > Installer Cache (Start, Run, Installer)
> >
> > Any other way around this without that file?
> >
> > Thanks again.
> >
> > Alan
> >
> >
> >
> > "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
> > news:ujJlyVXiFHA.2904@tk2msftngp13.phx.gbl...
> >> That 8222e.msi file is the cached MSI file for a product. It's required
> > for
> >> the uninstall (and any repair etc etc) and is not supposed to be
removed.
> >> Step 1 in the manual uninstall in that previously mentioned kb article
> > uses
> >> that cached MSI file, so that won't work for your missing one.
> > Incidentally,
> >> msizap will remove the Windows Installer references to those installed
> >> products but it doesn't remove the files.
> >> --
> >> Phil Wilson [MVP Windows Installer]
> >> ----
> >
> >
>
>