Hi,
We have a released product shipping for a while now and suddenly get a reproducible "Feature transfer error". The file in question is part of a larger set and other files in the feature are copied fine. (Verified with Sysinternals ProcessMonitor)
As far as I can tell neither the file in question nor the code for the installer (which is a InstallShield Install Script project) has changed (as in "at all") in recent weeks. (Last change to the installer was about a month ago.)
The problem affects both server builds, as well as local builds on the InstallShield development machines. We currently use InstallShield 2012 Spring for this product.
Internet searches for the issue did not lead to even a pointer into the right direction so far and I was hoping maybe somebody else on here has seen such a behavior in the past.
Path length appears not to be the issue (from inspection and judging by the fact that other files in the component with longer paths copy fine) and the file itself had no change since last year.
What can lead to this suddenly showing up?
Could you provide any additional pointers as to how best find out what causes the problem? (InstallShield debugger appears not to be triggered by the problem - but I might miss a configuration option.)
Thank you for the time to read this and any advise on the issue!
-T
System info: IS2012 Spring; Windows 7 x64 PRO target machines (multiple); Windows 7 x64 IS development systems;
![Name: IS2012SpringError.PNG
Views: 2
Size: 17.7 KB]()
Update with additional information (07/21/2014 04:00PM):
It looks like the file in question exists twice in the source tree and gets pulled in twice - both times via components that use 'Dynamic File Links'. Can it be that InstallShield has trouble generating unique files when packaging the components?
File system layout:
InstallShield layout:
Am I running into a weird corner case with the InstallShield compiler / engine?
Thanks,
-T
We have a released product shipping for a while now and suddenly get a reproducible "Feature transfer error". The file in question is part of a larger set and other files in the feature are copied fine. (Verified with Sysinternals ProcessMonitor)
As far as I can tell neither the file in question nor the code for the installer (which is a InstallShield Install Script project) has changed (as in "at all") in recent weeks. (Last change to the installer was about a month ago.)
The problem affects both server builds, as well as local builds on the InstallShield development machines. We currently use InstallShield 2012 Spring for this product.
Internet searches for the issue did not lead to even a pointer into the right direction so far and I was hoping maybe somebody else on here has seen such a behavior in the past.
Path length appears not to be the issue (from inspection and judging by the fact that other files in the component with longer paths copy fine) and the file itself had no change since last year.
What can lead to this suddenly showing up?
Could you provide any additional pointers as to how best find out what causes the problem? (InstallShield debugger appears not to be triggered by the problem - but I might miss a configuration option.)
Thank you for the time to read this and any advise on the issue!
-T
System info: IS2012 Spring; Windows 7 x64 PRO target machines (multiple); Windows 7 x64 IS development systems;
Update with additional information (07/21/2014 04:00PM):
It looks like the file in question exists twice in the source tree and gets pulled in twice - both times via components that use 'Dynamic File Links'. Can it be that InstallShield has trouble generating unique files when packaging the components?
File system layout:
Code:
[...]
+ Folder A
+ Folder AA
+ Folder AAA
+ Folder AAAA
- [...]
- BadFile.txt
[...]
+ Folder B
+ Folder BB
+ Folder BBB
+ Folder BBBB
- [...]
- BadFile.txt
Code:
+ Feature X
+ [...]
+ Component XX
+ Dynamic File Links for items under 'Folder AA' including sub-folders and BadFile.txt with it
+ [...]
+ Feature Z
+ [...]
+ Component ZZ
+ Dynamic File Links for items under 'Folder B' including sub-folders and BadFile.txt with it
Am I running into a weird corner case with the InstallShield compiler / engine?
Thanks,
-T