InstallAware

I recently upgraded from InstallAware 17 to X3 and I am configuring a new build server. I am frequently seeing failures with the message, "Error during build: Unable to set MSI summary stream code page." Although the same error message is mentioned a couple of times in this forum, I do not see a definitive reason or solution. Can anyone enlighten me as to the possible causes of this error? Thank you.

EDIT: After following the advice from one of the other posts and disabling anti-virus real time scanning, it does appear to succeed more consistently. My sample size so far is slightly fewer than 30 successful MSBuild driven builds in a row, but that is pretty good compared to what I saw before. I would like to have virus scanning exceptions as narrow as possible, so it would be helpful to know what file(s) being accessed can lead to the "Unable to set MSI summary stream code page" error.

Dear Hajnie,

as I have already said with other replies, unfortunately often it is not enough to just disable the AV and it may be necessary to un-install it.

Regards

Hi Francesco,

Thank you for your input. I saw your 2010 message stating as much in the "A bit frustrated" thread. I was thinking since that one goes back to 2007, I'd start a new question about it in hope there was more recent information available. I see now that thread had a recent post with essentially the same question I'm asking.

My IT people are going to want this server to have antivirus. In my tests yesterday and today, the builds are working consistently if I exclude the entire build folder from real time scanning. I'd like to narrow the exclusion further, perhaps by file type. I'm not an expert in the MSI summary streams and InstallAware allows me to be blissfully unaware of some details. What I see from the logging is the execution of miabuild.exe, a few messages about the settings, an attempt to clear the output folder, and then the error referenced above. What I can't tell is whether InstallAware is using the MSI API to manipulate the summary stream or if it's using msiinfo.exe or orca.exe to manipulate those, and I can't tell for certain what files are being written at the time. If you can give me more detail about the process or specifically which files are involved (just .msi files, or others too), perhaps I can narrow down the anti-virus exclusions in a way that satisfies our IT people.

Thank you.

Dear Hajnie,

I had the same identical problem but with Visual Studio. I switched to Microsoft Essentials which is very good AV, not intrusive and it's also free.

Regards