mdavi27 wrote: Thanks for the reply! I believe the issue is with any and all builds failing on the machine that has OfficeScan installed. The difficult part of the problem is that OfficeScan isn't finding any threats in the file(s), so it's not logged which file(s) it is scanning. I believe the issue is that OfficeScan is trying to perform a real-time scan on the files when InstallShield is performing its build, and this causes InstallShield to choke. I'm going to try excluding the files in the KB you linked to, but I don't know if those files are relevant to InstallShield 2013 - there's nothing in the article stating what version of the software this info is applicable to. We'll see what happens. From an IT standpoint, supporting InstallShield is turning into a nightmare. The documentation on this stuff is super poor from an administrative standpoint. 😞 I have a customer with a similar problem to you, but is unable to disable his anti-virus due to company policy; he's also using the OfficeScan. I was wondering if the KB resolved your problem or not. Cheers DS ... View more

The main difference between the two is that with InstallShield you can create MSI installers, with InstallAnywhere you can't. Also, InstallAnywhere is multiplatform (Linux, AIX, Mac OSX, Windows etc) whereas InstallShield is Windows exclusively. ... View more

Have you made any changes to InstallAnywhere at all? Updates, newer version (2011 -> 2012), installed SP1? Anything? ... View more

Hello ofirHadad Oddly enough - I had written a KB article today about this problem; you can view it here: http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q213459 It's a problem with the Java for Mac OS X that causes blank dialog boxes -- The solution is also on there. Let me know how you get on 🙂 ... View more