Hi,
I am getting the following error for 3 files in my package.

File with key ***.db located at C:\*** could not be compressed. This may be a temporary file location. Make sure file ***.db has a source path.
I get a similar error for a .PX file.

There are other .db and .PX files in the same directory and these are compressed without any errors, these 3 files are the only ones with 0 bytes. The source paths are correct and I have tried deleting and dropping these files in file view but each time I drop it in the file size returns to 0.

I then deleted them and compiled and installed. The install went cleanly but the application fails complaining about the missing files.

Any ideas on how to integrate these files into my package<

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Sounds like you're using Wise? If so, and you've checked all source paths and they're pointing to valid files then you may be encountering a bug I come across in Wise every once in a while. I've been able to resolve this by converting the project to Wisescript (.wse) and recompiling back into .MSI

Or you could try removing the files, recompiling and then re-adding them.
Answered 08/24/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Hi Tony:

It seems that the file you are trying to package/add inside the MSI are less than a Kb in size. If you are using Wise it will ignore all those files which are less than a kb and will show them as Zero and will not be able to compress them inside the MSI. Moreover, wise ignore all those files which have a zero bytes size. you can try this your self make one txt file that should contain any thing and then try to incooperate that inside the MSI , WISE will not compress them or will automatically remove them from compression. Hope this would help.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
Seems that they have fixed this in 5.60 as I don't get this problem.. dunno if 5.5 can handle this.. maybe :)
Answered 08/24/2005 by: AngelD
Red Belt

Please log in to comment
0
I am sorry forgot to say this , as Viking said you can create a WSE file that will install these files and then you can call this wse/exe inside your MSI. Need help in Wise Script Editor for doing the same. Leave a msg on this topic.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
I agree with you Angel, since I have both 5.6 and 5.2 , 5.6 is quite stable than 5.2 , I hope Wise has fixed most of its bugs.lol

Take Care
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
0
While your at it, don't forget to install the hotfix1 for 5.60
Answered 08/24/2005 by: AngelD
Red Belt

Please log in to comment
0
Thanks all,
This must have been a wise bug, I have managed to compiled the package by going into components then browsing to the source I then noticed the file size change for the first time. However, when I first ran the app I got an file header error. I then deleted and dropped the files again in file view and this worked. I did notice somethig strange though as one of the files in the source was 2,103 kb but reported as 3MB in the destination.

Anyway thanks for your suggestions.

By the way what is wse and how do you generate one?
Answered 08/24/2005 by: TonyDeploy
Senior Yellow Belt

Please log in to comment
0
Hi tony:

Well a WSE stands for Wise Script Editor file, this can be either created via Wise Installation System or Wise Script Editor in Wise Package Studio. Try sometime its a great tool.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity