Temp Msi file

hi all,
i am creating an msi package using Installshield 9. My problem is that when I run my msi package. a copy of the msi is created in the temp directory. This msi never gets deleted when the installation is finished. not even after reboot..... How can I tell the installer to clean that file... Thank you.....

I guess you're running a bootstrapper exe (setup.exe or something) that is
unpacking the MSI into the temp folder and it's being installed from there.
First, do you really need the setup.exe? Most systems have the MSI engine
already installed. The other problem is that repair operations on the
installed product or using Add/Remove Programs to change the installed
features, and maybe patching, will require access to that MSI file. It is a
*good thing* to have the MSI file available. I guarantee that if you remove
it, something will ask for it later! It's a common issue that people use a
bootstrapper that puts the MSI in the temp folder which then gets cleaned up
and then Windows needs access to the MSI file.
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

"Feras Wasef" <abutalib@sympatico.ca> wrote in message
news:wxVqc.68809$325.1406212@news20.bellglobal.com...


hi all,
i am creating an msi package using Installshield 9. My problem is that when
I run my msi package. a copy of the msi is created in the temp directory.
This msi never gets deleted when the installation is finished. not even
after reboot..... How can I tell the installer to clean that file... Thank
you.....

Hi,
Yes, I am using a bootstrapper ... But the problem do exist even if I use
the msi package alone. I looked at many other MSI packages and I notice that
all of them create this weired-named msi package in the temp folder.The only
difference is these weired named package will be deleted when we finish the
installation but mine never get deleted. not even after a reboot From that I
can guess that the windows installer is the one responsible for creating
this. Can any one tell me how to fix this ? what should I do to fix that??
Thank you
"Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
news:uXAGpynPEHA.556@tk2msftngp13.phx.gbl...
> I guess you're running a bootstrapper exe (setup.exe or something) that is
> unpacking the MSI into the temp folder and it's being installed from
there.
> First, do you really need the setup.exe? Most systems have the MSI engine
> already installed. The other problem is that repair operations on the
> installed product or using Add/Remove Programs to change the installed
> features, and maybe patching, will require access to that MSI file. It is
a
> *good thing* to have the MSI file available. I guarantee that if you
remove
> it, something will ask for it later! It's a common issue that people use a
> bootstrapper that puts the MSI in the temp folder which then gets cleaned
up
> and then Windows needs access to the MSI file.
> --
> Phil Wilson
> [MVP Windows Installer]
> Definitive Guide to Windows Installer
> http://apress.com/book/bookDisplay.html?bID=280
>
> "Feras Wasef" <abutalib@sympatico.ca> wrote in message
> news:wxVqc.68809$325.1406212@news20.bellglobal.com...
>
>
> hi all,
> i am creating an msi package using Installshield 9. My problem is that
when
> I run my msi package. a copy of the msi is created in the temp directory.
> This msi never gets deleted when the installation is finished. not even
> after reboot..... How can I tell the installer to clean that file... Thank
> you.....
>
>

I wouldn't expect that weirdly named msi file to be in the Temp folder (it
might depend on the OS) but there will be one in the Windows\Installer
folder. That's the cached version used for repair etc. If products have been
patched you'll see msp files also. What exactly is the weird file called,
and exactly which temp folder is it in?
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://www.installsite.org/pages/en/msi/books.htm

"Feras Wasef" <abutalib@sympatico.ca> wrote in message
news:y%Arc.53681$qJ5.1246521@news20.bellglobal.com...
> Hi,
> Yes, I am using a bootstrapper ... But the problem do exist even if I use
> the msi package alone. I looked at many other MSI packages and I notice
that
> all of them create this weired-named msi package in the temp folder.The
only
> difference is these weired named package will be deleted when we finish
the
> installation but mine never get deleted. not even after a reboot From that
I
> can guess that the windows installer is the one responsible for creating
> this. Can any one tell me how to fix this ? what should I do to fix that??
> Thank you
> "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
> news:uXAGpynPEHA.556@tk2msftngp13.phx.gbl...
> > I guess you're running a bootstrapper exe (setup.exe or something) that
is
> > unpacking the MSI into the temp folder and it's being installed from
> there.
> > First, do you really need the setup.exe? Most systems have the MSI
engine
> > already installed. The other problem is that repair operations on the
> > installed product or using Add/Remove Programs to change the installed
> > features, and maybe patching, will require access to that MSI file. It
is
> a
> > *good thing* to have the MSI file available. I guarantee that if you
> remove
> > it, something will ask for it later! It's a common issue that people use
a
> > bootstrapper that puts the MSI in the temp folder which then gets
cleaned
> up
> > and then Windows needs access to the MSI file.
> > --
> > Phil Wilson
> > [MVP Windows Installer]
> > Definitive Guide to Windows Installer
> > http://apress.com/book/bookDisplay.html?bID=280
> >
> > "Feras Wasef" <abutalib@sympatico.ca> wrote in message
> > news:wxVqc.68809$325.1406212@news20.bellglobal.com...
> >
> >
> > hi all,
> > i am creating an msi package using Installshield 9. My problem is that
> when
> > I run my msi package. a copy of the msi is created in the temp
directory.
> > This msi never gets deleted when the installation is finished. not even
> > after reboot..... How can I tell the installer to clean that file...
Thank
> > you.....
> >
> >
>
>

Hi,
The weired name temp file is always changing ... one of them was like
294360c.msi. I checked it with the one get cached in the windows installer.
it has a different name but same size...... so I am not sure what I am doing
wrong to prevent it from being deleted......
Thank you very much ........

"Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
news:eD%23YU%23AQEHA.808@tk2msftngp13.phx.gbl...
> I wouldn't expect that weirdly named msi file to be in the Temp folder (it
> might depend on the OS) but there will be one in the Windows\Installer
> folder. That's the cached version used for repair etc. If products have
been
> patched you'll see msp files also. What exactly is the weird file called,
> and exactly which temp folder is it in?
> --
> Phil Wilson
> [MVP Windows Installer]
> Definitive Guide to Windows Installer
> http://www.installsite.org/pages/en/msi/books.htm
>
> "Feras Wasef" <abutalib@sympatico.ca> wrote in message
> news:y%Arc.53681$qJ5.1246521@news20.bellglobal.com...
> > Hi,
> > Yes, I am using a bootstrapper ... But the problem do exist even if I
use
> > the msi package alone. I looked at many other MSI packages and I notice
> that
> > all of them create this weired-named msi package in the temp folder.The
> only
> > difference is these weired named package will be deleted when we finish
> the
> > installation but mine never get deleted. not even after a reboot From
that
> I
> > can guess that the windows installer is the one responsible for creating
> > this. Can any one tell me how to fix this ? what should I do to fix
that??
> > Thank you
> > "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
> > news:uXAGpynPEHA.556@tk2msftngp13.phx.gbl...
> > > I guess you're running a bootstrapper exe (setup.exe or something)
that
> is
> > > unpacking the MSI into the temp folder and it's being installed from
> > there.
> > > First, do you really need the setup.exe? Most systems have the MSI
> engine
> > > already installed. The other problem is that repair operations on the
> > > installed product or using Add/Remove Programs to change the installed
> > > features, and maybe patching, will require access to that MSI file. It
> is
> > a
> > > *good thing* to have the MSI file available. I guarantee that if you
> > remove
> > > it, something will ask for it later! It's a common issue that people
use
> a
> > > bootstrapper that puts the MSI in the temp folder which then gets
> cleaned
> > up
> > > and then Windows needs access to the MSI file.
> > > --
> > > Phil Wilson
> > > [MVP Windows Installer]
> > > Definitive Guide to Windows Installer
> > > http://apress.com/book/bookDisplay.html?bID=280
> > >
> > > "Feras Wasef" <abutalib@sympatico.ca> wrote in message
> > > news:wxVqc.68809$325.1406212@news20.bellglobal.com...
> > >
> > >
> > > hi all,
> > > i am creating an msi package using Installshield 9. My problem is that
> > when
> > > I run my msi package. a copy of the msi is created in the temp
> directory.
> > > This msi never gets deleted when the installation is finished. not
even
> > > after reboot..... How can I tell the installer to clean that file...
> Thank
> > > you.....
> > >
> > >
> >
> >
>
>