/build/static/layout/Breadcrumb_cap_w.png

Error packaging an APP

I'm trying to package an app called perforce. When I try to compile the file I get the error.

File with key tmp.edb located at C:\WINDOWS\SoftwareDistribution\DataStore\Logs\tmp.edb could not be compressed. This may be a temporary file location. Make sure file tmp.edb has a source path.


& the MSI file is never created. Any Ideas why this happens?

Thanks

0 Comments   [ + ] Show comments

Answers (5)

Posted by: WiseUser 19 years ago
Fourth Degree Brown Belt
0
I don't think you want to package that file (in fact I'm pretty sure you don't)!

Just delete it from your project - you should be fine.
Posted by: newpackager 19 years ago
Senior Yellow Belt
0
Hi you can go ahead and delete the SoftwareDistribution Directory as you dont need the directory or any of those files in your application.
Posted by: viv_bhatt1 19 years ago
Senior Purple Belt
0
Which tool are you using for packaging ?
Posted by: jguyton 19 years ago
Senior Yellow Belt
0
I'm using Wise. The problem was that the MSI file wasn't being created. I think the problem was that there was a dot (.) in part of the filename. I removed it and now am able to package the file as a MSI
Posted by: AngelD 19 years ago
Red Belt
0
The C:\WINDOWS\SoftwareDistribution directory is part of the "Windows Update" and this is it's root directory.
Make sure you disable the WU service when repackaging.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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