This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: MSI runs on my machine but not on test machine
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2009
03:53 PM
MSI runs on my machine but not on test machine
The MSI works on my machine creating the following path
C:\MyTestMSI\MytestProject\*.dll
C:\MyTestMSI\register.vbs
My custom action runs the vbs file and registers the files.
If i run my MSI on a test machine it fails to add the files here
C:\MyTestMSI\MytestProject\*.dll
the path is created but no files and it starts to run the custom action.
With INstallShield, my MSI is located here
C:\InstallShield 2010 Projects\TestMSI\Product Configuration 1\Release 1\DiskImages\DISK1\
- *.exe
-*.ini
-*.MSI
-MyTestMSI\MyTestProject\*.dll
ON test machine I get Error 1308
C:\MyTestMSI\MytestProject\*.dll
C:\MyTestMSI\register.vbs
My custom action runs the vbs file and registers the files.
If i run my MSI on a test machine it fails to add the files here
C:\MyTestMSI\MytestProject\*.dll
the path is created but no files and it starts to run the custom action.
With INstallShield, my MSI is located here
C:\InstallShield 2010 Projects\TestMSI\Product Configuration 1\Release 1\DiskImages\DISK1\
- *.exe
-*.ini
-*.MSI
-MyTestMSI\MyTestProject\*.dll
ON test machine I get Error 1308
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2009
04:30 PM
on the test machine, are you copying jsut the .MSI file over or all the files in the DISK1 directory?
is this a basic msi or an installscript msi project?
Is the project being built compressed or uncompressed, are there more subdirectories in the DISK1 directory and are they being copied over to the test machine?
Windows installer error 1308 is "Source file not found".
is this a basic msi or an installscript msi project?
Is the project being built compressed or uncompressed, are there more subdirectories in the DISK1 directory and are they being copied over to the test machine?
Windows installer error 1308 is "Source file not found".
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2009
04:31 PM
Am just copying the MSI and not the contents of Disk1. This is basic MSI
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 04, 2009
04:34 PM
Lurean wrote:
on the test machine, are you copying jsut the .MSI file over or all the files in the DISK1 directory?
is this a basic msi or an installscript msi project?
Is the project being built compressed or uncompressed, are there more subdirectories in the DISK1 directory and are they being copied over to the test machine?
Windows installer error 1308 is "Source file not found".
on the test machine, are you copying jsut the .MSI file over or all the files in the DISK1 directory? ---- Only copying the MSI
is this a basic msi or an installscript msi project? - Basic MSI
Is the project being built compressed or uncompressed, are there more subdirectories in the DISK1 directory and are they being copied over to the test machine? - Compressed/Uncompressed??
Under Disk1 I have the following
*.MSI
*.exe
*.ini
MyTestMSI
Under MyTestMSI I have
|-MyTestProject
Under MyTestProject I have 3 sub dirs
|-Folder 1 \*.dll
|-Folder 2 \*.dll
|-Folder 3 \*.dll
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 05, 2009
03:01 PM
if you want to copy only a single file over, you will need to build the project as a compressed release. This will compress everything into a single output file. If you want it to be an msi instead of a setup.exe, then you will need to set the "Setup Launcher" option under the "setup.exe" tab of the release to No.
If you do not build it as a compressed build then you will need all of the files that are put into the output "DISK1" directory. Copy the entire contents of the DISK1 directory to the test machine and you will have no problems so long as relative paths are maintained. Meaning that the msi file and all other files/folders from DISK1 are in the same location on the test machine.
If you do not build it as a compressed build then you will need all of the files that are put into the output "DISK1" directory. Copy the entire contents of the DISK1 directory to the test machine and you will have no problems so long as relative paths are maintained. Meaning that the msi file and all other files/folders from DISK1 are in the same location on the test machine.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)