This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 4 years and 2 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Building MSI file...
heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\speedtest.exe. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load file: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\speedtest.exe, error: 193
heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\Test-Services.exe. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load file: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\Test-Services.exe, error: 193
heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\InstallerFiles\bin\x64\CopyShortcut.exe. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load file: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\InstallerFiles\bin\x64\CopyShortcut.exe, error: 193
heatout.wix
C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\heatout.wix(70) : error LGHT0094 : Unresolved reference to symbol 'Directory:ProgramFilesFolder' in section 'Product:{SANITIZEDGUID}'.
Error: Could not create MSI file
6 error(s), 3 warning(s)
I am unable to build an MSI and don't understand what I need to do in order to fix this issue.
Generally this type of error indicates that the file specified does not exist or is not accessible. Possible not in the location expected.
Check that your folder has write permissions.
There is an error : Unable to load file: C:\Users\SANITIZED\Documents\Code\PowerShell\ScriptProjects\Test-Services\Test-Services\bin\x64\InstallerFiles\bin\x64\MSI_BuildFolder\Test-Services.exe, error: 193
Could you attach .psbuild file?
And screenshot of Installer/Files and Folders settings in Script Packager
What's odd about this area, is that the shortcut normally would say "packaged executable" but if I hit the drop down, it just adds the places in Documents.
The folder structure seems to contain duplicates (I don't know if that is intentional) and usually those kind of errors from the WiX toolset indicate it cannot resolve or cope with the path names.
It is quite possible that these here simply get too long for the toolset.
I would suggest to restructure the folders so that there are no unnecessary replications of folders.
Additionally, the output folders should be in the root of your project to avoid confusion where files are copied.
...\Code\ProwerShell\ScriptProjects\TestServices\output would be a good choice I guess.
This topic is 4 years and 2 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
