This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- files missing in data1.cab and data1.hdr
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 30, 2013
11:23 PM
files missing in data1.cab and data1.hdr
Hi,
When I extract my data1.hdr I found that most of the files are missing under components.
Mostly, the data1.hdr didn't include the files but include the folders only. (For example, Parent is a folder under child1 and child2 are files. In data1.hdr,only parent\ has been included but it should be like parent\child1,parent\child2.)
I believe some configuration is missing.Please suggest...
When I extract my data1.hdr I found that most of the files are missing under components.
Mostly, the data1.hdr didn't include the files but include the folders only. (For example, Parent is a folder under child1 and child2 are files. In data1.hdr,only parent\ has been included but it should be like parent\child1,parent\child2.)
I believe some configuration is missing.Please suggest...
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 31, 2013
08:39 AM
I suggest looking at the report that was created when the project was built. Verify that the files and subfolders were detected at the source at the time the package was built. I have had the situation where I am using a Dynamic Link in a Component, and due to network issues external to InstallShield the Dynamic Link does not detect any files or subfolders. So they are 'missing' from the resulting package. There is no error reported because Dynamic Link included everything it found for the Component, which was nothing. This is a risk that you take when you use Dynamic Linking rather than Static Linking. But without reviewing your build report, one can only guess that the issue might be related to a Dynamic Link.
After this Dynamic Link issue bit us a few times we scripted into our build process a procedure that compares the new build report to the last build report and produces a 'difference' report. Using this I can detect when this problem happens, fix the network problem, and rebuild the package prior to ever passing the defective package to QA.
After this Dynamic Link issue bit us a few times we scripted into our build process a procedure that compares the new build report to the last build report and produces a 'difference' report. Using this I can detect when this problem happens, fix the network problem, and rebuild the package prior to ever passing the defective package to QA.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 31, 2013
11:53 PM
phill_mn wrote:
I suggest looking at the report that was created when the project was built. Verify that the files and subfolders were detected at the source at the time the package was built. I have had the situation where I am using a Dynamic Link in a Component, and due to network issues external to InstallShield the Dynamic Link does not detect any files or subfolders. So they are 'missing' from the resulting package. There is no error reported because Dynamic Link included everything it found for the Component, which was nothing. This is a risk that you take when you use Dynamic Linking rather than Static Linking. But without reviewing your build report, one can only guess that the issue might be related to a Dynamic Link.
After this Dynamic Link issue bit us a few times we scripted into our build process a procedure that compares the new build report to the last build report and produces a 'difference' report. Using this I can detect when this problem happens, fix the network problem, and rebuild the package prior to ever passing the defective package to QA.
Yes.I looked the report too. There I am able to see like File is "". Size is some KB. Identifier is something and the Source is "I\Media\...". So the source is correct. But the file name is simply with "". And some of the files are missing here. But I am sure every file copied into the source folder of the installation.
