Error in compiling files

Hi All,

I have setup captured an application.When I am compiling WSI/MSI, it gives error as "File with Key XXXX.err located at C:\Program Files\XXX\XXXX.err could not be compressed. This may be tempoparty file location.Make sure file XXXX.err has source path". Application has 3 files which gives same error. I should not delete these files. These are key files for setting and running application oriented service. I have even tried for adding these 4 files in different components and making them as key path.Still in vain. Can any one please assist me in resolving this issue.

Many thanks in advance.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 13 years ago
Red Belt
You're using a Wise product, right?

Check the file's details in the WiseSourcePath table. I'd bet a pound to a penny that the location in the file's SourcePath is no longer available. The normal cause is that when setting up your capture, you omitted to select the option to copy the files to the project folder. Thus, Wise ends up using the actual installed files as the source for the compiled MSI. If you have uninstalled the app or reset the VM or re-imaged the workstation, those files no longer exist.
Posted by: AngelD 13 years ago
Red Belt
Try stopping the service(s) before compiling as they may be locking them during running.
Posted by: beefy66 13 years ago
Orange Belt
If you have already done an initial compile, the easiest way would be to just install your capture on a vm or test box. That way, all the files will be in place for your compile.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ