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
- :
- Re: Architecture Validation Error
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
‎Jun 15, 2015
04:21 PM
Architecture Validation Error
I have a WiX merge module (Intel;1033) being consumed by an InstallShield Basic MSI. We just updated to InstallShield 2015 and we get the below error:
C:\Program Files (x86)\MSBuild\InstallShield\2015\InstallShield.targets (77): -7325: An unexpected error occurred validating the architecture for file H:\B\749\bin\Setup\Release\REDACTED\Interm\MergeModules\REDACTED\13DB569E_FE5C_4577_9C35_35037C98A716\owfBB2979387EC89E5CF6C7207B333B65A6.13DB569E_FE5C_4577_9C35_35037C98A716.
The file in question is Microsoft.Practices.EnterpriseLibrary.Common.dll which is a .NET DLL. I have validation set to Lenient and yet I still get this error. Does anyone have any suggestions on how to troubleshoot and/or completely disable architecture validation? This was previously built by InstallShield 2012 Spring and has been in production for several years without issues.
C:\Program Files (x86)\MSBuild\InstallShield\2015\InstallShield.targets (77): -7325: An unexpected error occurred validating the architecture for file H:\B\749\bin\Setup\Release\REDACTED\Interm\MergeModules\REDACTED\13DB569E_FE5C_4577_9C35_35037C98A716\owfBB2979387EC89E5CF6C7207B333B65A6.13DB569E_FE5C_4577_9C35_35037C98A716.
The file in question is Microsoft.Practices.EnterpriseLibrary.Common.dll which is a .NET DLL. I have validation set to Lenient and yet I still get this error. Does anyone have any suggestions on how to troubleshoot and/or completely disable architecture validation? This was previously built by InstallShield 2012 Spring and has been in production for several years without issues.
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 16, 2015
11:09 AM
It was suggested to me to investigate path length issues. FWIW, it doesn't seem to be a path length issue.
I also reproduced the issue without the use of a merge module.
I'm able to build locally using the IDE. On my build server using TFS/MSbuild/SAB I get the error when this DLL
is consumed directly or via merge module. As an aside, the attached DLL also generates an internal build error 6212 when .NET dependency scanning is set to Dependencies and Properties. I get past this error by changing it to Properties only (my normal best practice) but then get the platform arch validation error message.
I also reproduced the issue without the use of a merge module.
I'm able to build locally using the IDE. On my build server using TFS/MSbuild/SAB I get the error when this DLL
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 17, 2015
09:52 AM
ISCmdBld.exe works also. The problem only manfiests itself when using MSBuild / InstallShield.targets via Full Blown IS 2015 and SAB Only installations.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 18, 2015
04:48 PM
An InstallShield 2015 hotfix for this issue is attached. To apply the fix, follow the steps below:
[LIST=1]
Make a backup copy of \Program Files (x86)\InstallShield\2015 SAB\System\ISWIScanners.dll.
Extract ISWIScanners.dll from the attached zip file to the path \Program Files (x86)\InstallShield\2015 SAB\System\.
Rebuild your project from MSBuild again.
This hotfix should resolve the build error -6212 and -7325. This issue has been tracked under IOJ-1733016 so that the fix will be incorporated into the next release of InstallShield.
[LIST=1]
This hotfix should resolve the build error -6212 and -7325. This issue has been tracked under IOJ-1733016 so that the fix will be incorporated into the next release of InstallShield.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 18, 2015
05:03 PM
Excellent! The hot fix worked!
I almost reported it didn't work but then I realized I had selected the wrong TFS build controller. Yes, it's been one of those days.... 🙂
Thanks,
Chris
I almost reported it didn't work but then I realized I had selected the wrong TFS build controller. Yes, it's been one of those days.... 🙂
Thanks,
Chris
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 25, 2015
04:36 PM
hidenori wrote:
An InstallShield 2015 hotfix for this issue is attached. To apply the fix, follow the steps below:
[LIST=1]Make a backup copy of \Program Files (x86)\InstallShield\2015 SAB\System\ISWIScanners.dll. Extract ISWIScanners.dll from the attached zip file to the path \Program Files (x86)\InstallShield\2015 SAB\System\. Rebuild your project from MSBuild again.
This hotfix should resolve the build error -6212 and -7325. This issue has been tracked under IOJ-1733016 so that the fix will be incorporated into the next release of InstallShield.
Any idea when the next release will be? I had to revert to 2014 from 2015 due these errors.
Thanks!
Jon
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 25, 2015
06:30 PM
jgilpin wrote:
Any idea when the next release will be? I had to revert to 2014 from 2015 due these errors.
Thanks!
Jon
...so you're saying the hotfix didn't fix the issue for you in InstallShield 2015?
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)