Alright, So I built a new VM XP SP3 Box, patched and all. Installed my nifty new program Studio Admin and proceeded with a Repackager of DesktopBinder Lite. After the capture I load the project to proceed with building a Single File and I continuosly get the following error, "Error during build: Unable to copy file to". I have gone as far as modifying the Output folder and still the same result. Move forward with a CD or Web, again same error. Permissions are perfectly fine on the folder level. Does anyone have any thoughts as to why this is happening?
Here is the exact error,
Building Project: rds
Output Folder: C:\\Release\\Single\Deployment Type: Compressed Single Self Installing EXE
Code Signing: Disabled
Compression: None
###
Cleared output folder C:\\Release\\Single\Built plug-in action (Un)Install MSI Setup
Error during build: Unable to copy file to C:\\Release\\Single\\data\\OFFLINE\\5C72EFED\\3E37E898\\{9A1C0136-8464-4EB6-BBB8-1A562DB41F02}
Error during build: Unable to copy file to ....
-
satirical1
- Posts: 2
- Joined: Fri Apr 10, 2009 5:11 pm
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
The file in question might have been picked up by the repackager but no longer available on the system, you may want to clean up the captured files a little based on such build errors and a little bit of intuition and trial and error...
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
-
satirical1
- Posts: 2
- Joined: Fri Apr 10, 2009 5:11 pm
No Go
Sadly, after several attempts and rebuilds. Clean install and all of both applications, same results in the error. I moved forward with using AppDeploys Repackager application and it captured everything perfectly without error.
I decided to test this with another application of ours that was giving us issues and the error was similar to the other. It keeps looking to this OFFLINE folder and errorring our. I can only assume I am using the application incorrectly... but then, I am doing nothing more then what the prompts ask me to do. Not sure where I might be going wrong here.
Any thoughts?
I decided to test this with another application of ours that was giving us issues and the error was similar to the other. It keeps looking to this OFFLINE folder and errorring our. I can only assume I am using the application incorrectly... but then, I am doing nothing more then what the prompts ask me to do. Not sure where I might be going wrong here.
Any thoughts?
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:

