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
- :
- Antivirus real time scanning from McAfee
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Jun 03, 2014
10:05 AM
Error 6003, Install Shield Express 2012
I tried re-building a release today and am getting a 6003 error message.
I can build a 'CD-rom' successfully but get the same error when trying to build a 'single executable' and a 'web deployment'.
Any suggestions on what may be causing the problem would be welcome.
extract of error message:
Building .cab files...
Data1.cab built
Files built
Media table successfully built
ISEXP : error -6003: An error occurred streaming 'C:\Users\dger\Documents\I_Shield_Pj\foreCASH_v2_xx\v2_60B\Express\SingleImage\DiskImages\DISK1\foreCASH.msi' into setup.exe
Setup.exe created
Automatic update notification enabled
Express\SingleImage - 1 error(s), 0 warning(s)
I can build a 'CD-rom' successfully but get the same error when trying to build a 'single executable' and a 'web deployment'.
Any suggestions on what may be causing the problem would be welcome.
extract of error message:
Building .cab files...
Data1.cab built
Files built
Media table successfully built
ISEXP : error -6003: An error occurred streaming 'C:\Users\dger\Documents\I_Shield_Pj\foreCASH_v2_xx\v2_60B\Express\SingleImage\DiskImages\DISK1\foreCASH.msi' into setup.exe
Setup.exe created
Automatic update notification enabled
Express\SingleImage - 1 error(s), 0 warning(s)
(1) Reply
Jun 05, 2014
09:04 AM
In case it helps anyone else, I traced the cause of this problem to McAffee Antivirus / AntiSpyware (v16.18) running at the same time as building web deployment file.
Had not previously been a problem so perhaps related to an update on McAfee side.
Had not previously been a problem so perhaps related to an update on McAfee side.