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
- :
- 1334 Error - Anyone Know Any Obscure Cures?
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
‎Mar 01, 2019
09:42 PM
1334 Error - Anyone Know Any Obscure Cures?
Hi all,
All of a sudden our web app installation is erroring with a 1334 - file cannot be found in .cab file. We are currently using InstallShield 2018 SP1. I've tried everything I can think of or found online, but I just can't get past this error.
I've removed the problematic component to see if it was some type of file problem, but the error just moved on to another file in the installation. Removed that, error just moved on to different file.
I even compiled a previous, released version which hasn't been touched in weeks and it errored on the same exact file. The source files for that release are in a completely different location, of course, than the originally failing release. My thought was maybe the source files were on a bad area of disk or something like that. That led me to believe that it might be something with InstallShield itself that went awry, .dll, a configuration setting or something like that. I repaired our InstallShield instance, no luck.
Ran chkdsk, no luck.
I've tried different compression settings in the Release settings, no luck.
I tried adding a different Release configuration, no luck.
I tried moving the .ism project directory, no luck.
I sent the build log and .ism to InstallShield support and they didn't see anything out of the ordinary there. They said they've seen this error with weird or missing file dates, but that is no the case here.
Does anyone know what else I could try? Any obscure cures?
Info MUCH Appreciated!!
All of a sudden our web app installation is erroring with a 1334 - file cannot be found in .cab file. We are currently using InstallShield 2018 SP1. I've tried everything I can think of or found online, but I just can't get past this error.
I've removed the problematic component to see if it was some type of file problem, but the error just moved on to another file in the installation. Removed that, error just moved on to different file.
I even compiled a previous, released version which hasn't been touched in weeks and it errored on the same exact file. The source files for that release are in a completely different location, of course, than the originally failing release. My thought was maybe the source files were on a bad area of disk or something like that. That led me to believe that it might be something with InstallShield itself that went awry, .dll, a configuration setting or something like that. I repaired our InstallShield instance, no luck.
Ran chkdsk, no luck.
I've tried different compression settings in the Release settings, no luck.
I tried adding a different Release configuration, no luck.
I tried moving the .ism project directory, no luck.
I sent the build log and .ism to InstallShield support and they didn't see anything out of the ordinary there. They said they've seen this error with weird or missing file dates, but that is no the case here.
Does anyone know what else I could try? Any obscure cures?
Info MUCH Appreciated!!
(10) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 03, 2019
02:38 AM
Superfreak3 wrote:
Hi all,
All of a sudden our web app installation is erroring with a 1334 - file cannot be found in .cab file. We are currently using InstallShield 2018 SP1. I've tried everything I can think of or found online, but I just can't get past this error.
I've removed the problematic component to see if it was some type of file problem, but the error just moved on to another file in the installation. Removed that, error just moved on to different file.
I even compiled a previous, released version which hasn't been touched in weeks and it errored on the same exact file. The source files for that release are in a completely different location, of course, than the originally failing release. My thought was maybe the source files were on a bad area of disk or something like that. That led me to believe that it might be something with InstallShield itself that went awry, .dll, a configuration setting or something like that. I repaired our InstallShield instance, no luck.
Ran chkdsk, no luck.
I've tried different compression settings in the Release settings, no luck.
I tried adding a different Release configuration, no luck.
I tried moving the .ism project directory, no luck.
I sent the build log and .ism to InstallShield support and they didn't see anything out of the ordinary there. They said they've seen this error with weird or missing file dates, but that is no the case here.
Does anyone know what else I could try? Any obscure cures?
Info MUCH Appreciated!!
Hi,
When you say web app installation is it via Suite project or something else?
Can you please attach complete log file here to check for more updates?
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 03, 2019
09:27 AM
Jenifer wrote:
Hi,
When you say web app installation is it via Suite project or something else?
Can you please attach complete log file here to check for more updates?
Thanks,
Jenifer
It is a Basic .msi package wrapped in a Setup.exe, which also delivers prerequisites. The install log is attached in two parts.
I've sent the log to InstallShield and they indicated they saw no problems other than the 1334 error.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
08:15 AM
Maybe try revoking your InstallShield License and install InstallShield on another machine?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
08:25 AM
rguggisberg wrote:
Maybe try revoking your InstallShield License and install InstallShield on another machine?
Yep, that's what I'm working on now. I was wondering if the trial version of IS is fully functional or has limitations. I don't want to revoke the license and install on another machine because other things are building fine on that production server.
I wonder if a complete uninstall/reinstall would do the trick. If so, do I have to revoke the license if working on the same machine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
10:19 AM
Let us know how that all works out for you.
Also, be careful how many times you revoke and re-use the license. After a few times you may have to contact Flexera.
Also, be careful how many times you revoke and re-use the license. After a few times you may have to contact Flexera.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
10:22 AM
rguggisberg wrote:
Let us know how that all works out for you.
Also, be careful how many times you revoke and re-use the license. After a few times you may have to contact Flexera.
Will do. Before I go the revoke route, I'm hoping I can use the trial to see if things work out on another machine. The only problem is, when I download the installer and install on different machine, when I launch IS, I can't select the option to continue with evaluation. I can only select activate or get license from server. I guess it sees a paid, running instance on the network.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
02:14 PM
I was able to get an instance of the trial version of InstallShield up and running on a new machine. The problem persists even if compiled on a different machine. So, the problem must be project specific.
The strange thing is that are released version is bad if recompiled and that hasn't been touched since release. Also, if a pull an install template from a few days prior and compile that too is problematic. This is perplexing and probably going to kill me! :confused:
The strange thing is that are released version is bad if recompiled and that hasn't been touched since release. Also, if a pull an install template from a few days prior and compile that too is problematic. This is perplexing and probably going to kill me! :confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
02:16 PM
Maybe try installing InstallShield on an older OS???
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
02:18 PM
rguggisberg wrote:
Maybe try installing InstallShield on an older OS???
What do you think that will do? It's been working fine. But I get it, who the heck knows what it might be.
Come to think of it, the trial version was run on an older OS.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2019
05:08 PM
I found the problem (with the help of Support). The support tech, and maybe some others mentioned modified date on a file. I was looking at the files indicated in the error. It turned out to be the file directly before that in sequence. It had no modified date!
I remember checking sequence being bounced around as well.
At least its fixed!!
Thanks for all the input!
I remember checking sequence being bounced around as well.
At least its fixed!!
Thanks for all the input!
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)