When building our installer we get error 7141 on one or multiple files (different each time we try to build the installer), a description of the error and a workaround is specified here:
Unfortunately we are unable to use the workaround (disable anti-virus) due to company policies. Is there another way to prevent this error? Is this fixed in newer versions?
Extra information:
The build can fail on one or more files when building. The files it fails on are not always the same, even when using the exact same source. Occasionally the build might succeed, even though the exact same source is used that failed to build 50 times before.
Considering that the files that give an error is not always the same and that disabling the anti-virus should prevent the error, it seems like this is caused by a timing issue where the anti-virus is still checking a new file when InstallShield wants to access it.
If this is the case then it might be pretty easy to fix within InstallShield by implementing a check/wait till the file is free to use and/or just implement a retry with a short delay. On the other hand, you would expect the issue to have been fixed already if it was that simple.
Please accept our apologies for the confusion and any frustration.
I understand that permanently disabling antivirus software is not an option for you due to company policies. But were you able to temporarily disable antivirus software to try to confirm whether antivirus software is causing this issue? I'm trying to determine whether we know what the cause is (if it's antivirus software or something else) or whether that's still part of what we're trying to determine.
Please let us know if you have any questions or concerns. Thanks!
I was able to get the same issue in a local virtual machine. The issue shows up less often, but still happens pretty regularly. Disabling the anti-virus on this virtual machine does seem to prevent the issue.
Did this issue ever get resolved? If so, could you please post the information here?
We are experiencing the same exact issue, among several others. Our issues began after the July 2023 Microsoft security updates were applied, in which we started getting error -1027: Failed signing ISSetup.dll and error -6003: An error occurred streaming. These errors would fail on random files, and sometimes we would not get any errors at all. It was all very random. We were asked to disable AV, but like you, our company policy would not allow it.
We've been working with Installshield support for a few weeks without much progress. They told us the issue was a change in Windows Defender is causing it to lock certain install files during build time and not releasing them quickly enough for Installshield to sign or stream them into the setup.exe. They sent us a set of updated Installshield 2022 R2 SAB files to try to address this timing issue. The new files appear to have addressed the 6003 streaming error. However, the 1027 error still occurs (very rarely at this point), and new issues/errors have cropped up, and are happening frequently:
ISDEV : error -7132: An error occurred streaming ISSetup.dll support file
