ISSetupFilesCleanup deleting files
Hi all,
We're experiencing a nasty little problem at the moment that hopefully you can help us with.
We're currently deploying the latest JAVA client to all our PCs. We've created a transform from the original vendor MSI that removes previous versions of JAVA if they're found on the end-user PC.
During the rollout we noticed that non-hidden files were being deleted from the c:\ root on all machines.
We've found the culprit to be ISSetupFilesCleanup custom action, but we don't know why!
Any ideas?
Here's the relevant section of the MSI log file -
Action start 17:29:03: ISSetupFilesCleanup.
1: Deleting Support File: \boot.ini
1: Deleting Support File: \buildmif.mif
1: Deleting Support File: \HPJIPP.dat
1: Deleting Support File: \IO.SYS
1: Deleting Support File: \MSDOS.SYS
1: Deleting Support File: \NTDETECT.COM
1: Deleting Support File: \ntldr
1: Deleting Support File: \pagefile.sys
1: Deleting Support File: \WFCNAME.INI
Action ended 17:29:04: ISSetupFilesCleanup. Return value 1.
Any help would be appreciated!!
Thanks,
Nookz
We're experiencing a nasty little problem at the moment that hopefully you can help us with.
We're currently deploying the latest JAVA client to all our PCs. We've created a transform from the original vendor MSI that removes previous versions of JAVA if they're found on the end-user PC.
During the rollout we noticed that non-hidden files were being deleted from the c:\ root on all machines.
We've found the culprit to be ISSetupFilesCleanup custom action, but we don't know why!
Any ideas?
Here's the relevant section of the MSI log file -
Action start 17:29:03: ISSetupFilesCleanup.
1: Deleting Support File: \boot.ini
1: Deleting Support File: \buildmif.mif
1: Deleting Support File: \HPJIPP.dat
1: Deleting Support File: \IO.SYS
1: Deleting Support File: \MSDOS.SYS
1: Deleting Support File: \NTDETECT.COM
1: Deleting Support File: \ntldr
1: Deleting Support File: \pagefile.sys
1: Deleting Support File: \WFCNAME.INI
Action ended 17:29:04: ISSetupFilesCleanup. Return value 1.
Any help would be appreciated!!
Thanks,
Nookz
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
NookZ
18 years ago
Can anybody help?
I cannot find anything about this on InstallShield, JAVA, or google websites!!
I cannot find anything about this on InstallShield, JAVA, or google websites!!
Posted by:
aogilmor
18 years ago
that's very odd. it seems like the msi is misreading the directory where it's suposed to delete the files and going for the root. can you just take out the ISSetupFilesCleanup action?
Posted by:
NookZ
18 years ago
Hi,
You're right that it's odd - especially from a vendor MSI.
Yep, we've removed the CA for the time being, but we'd really like to know what causes it and to find out if anybody else had suffered from it.
Regards,
Nookz
You're right that it's odd - especially from a vendor MSI.
Yep, we've removed the CA for the time being, but we'd really like to know what causes it and to find out if anybody else had suffered from it.
Regards,
Nookz
Posted by:
tsmiller
18 years ago
Hi,
I ran into this same problem with ISSetupFilesCleanup deleting files in C:\. In my case the problem arose with Intel Fortran Compiler 9.1. The problem occurs when I install the MSI without using setup.exe. If setup.exe is usws, the working directory for the ISSetupFilesCleanup action is %temp%. That seems to be where the install extracts some files that will be used by the install processes. However, if the MSI is invoked directly instead of using setup.exe, then the working directory for the ISSetupFilesCleanup action is C:\ and non-system, non-readonly files are deleted.
In my case, I'm deploying the MSI along with an MST that I created as a response transform using InstallShield Editor. A little digging on the Macrovision site found this technote that seems to be a close match to the problem.
http://esupportus.macrovision.com/view.asp?articleid=Q111491
--Terry
I ran into this same problem with ISSetupFilesCleanup deleting files in C:\. In my case the problem arose with Intel Fortran Compiler 9.1. The problem occurs when I install the MSI without using setup.exe. If setup.exe is usws, the working directory for the ISSetupFilesCleanup action is %temp%. That seems to be where the install extracts some files that will be used by the install processes. However, if the MSI is invoked directly instead of using setup.exe, then the working directory for the ISSetupFilesCleanup action is C:\ and non-system, non-readonly files are deleted.
In my case, I'm deploying the MSI along with an MST that I created as a response transform using InstallShield Editor. A little digging on the Macrovision site found this technote that seems to be a close match to the problem.
http://esupportus.macrovision.com/view.asp?articleid=Q111491
--Terry
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.