I'll help point you guys in the right direction: The actual error is buried. It won't show in your logfile--error -1001 is just what the Microsoft InstallUtilLib.dll passes back when there's an error inside the installer class. Your best bet is to debug it yourself by inserting a Debugger.Launch() statement inside your Installer Class and then stepping through with Visual Studio. Good luck! ... View more

jweiss wrote: I'm trying to use Installshield and run a Powershell command with parameters. I didn't find anything online or in the manual. Anyone have any ideas? Do you mean, as a custom action? http://helpnet.installshield.com/installshield19helplib/helplibrary/CAPowerShell.htm Or as a *.prq? (Just run it with params like you would from the command line) Or are you trying to use the InstallShield Automation layer? https://blogs.flexera.com/installtalk/2011/01/getting-started-with-installshield-automation-and-powershell/ ... View more

My best guess is that it's stored in a PE stub somewhere. So, I'd start by thumbing through the InstallShield program files with a resource editor until you find a dialog that has the branding on it. Good luck. Needle in a haystack kind of thing. ... View more

So full disclosure: I haven't done this type of shortcut pinning before. I've only made this work with the taskbar shortcuts, but the process overall should be the same. First of all, you can't natively do this in InstallShield. Microsoft specifically didn't want to provide an API or other easy way to do this, because if they did, every software vendor would do it and the pinned area would fill up with junk just like your desktop does with desktop shortcuts. Baking this into an installer is hostile to the user. That said *I would seriously reconsider the decision to take this path in your installer*. So, assuming you have a very good reason for doing so, what you are going to need to do is reverse engineer what happens when a user clicks on a shortcut to pin it. This is going to be a Shell Verb, basically. Then you need to invoke that shell verb from whatever language, passing the path of the *.lnk file in order to pin it. I found some C# code which does this here: https://stackoverflow.com/questions/42819959/shell-application-verbs-net-3-5 These shell verbs are in the registry, and it's possible that organizations can disable them--make sure on your test machines that it works manually first. Good luck! ... View more

This sounds really, really strange. As far as the file in Config.msi, I'm at a loss to explain why this is happening. I would post the logs of the first scenario: 1. Base Install log 2. Patch 1 install log 3. Patch 2 install log Error 1706 has two components: The first being, something is happening which requires source. Mostly likely in this case the removal of a binary patch of file(s), since it needs to rewrite the original version of the file. The second component is the original *.msi is not accessible in the place where you installed it from. If it's a network location, that location is inaccessible. If it's the local machine, the file probably has moved. Again, a log file will help diagnose this. ... View more

Environment variables are tricky. Sometimes, the only way to truly get them reflected across the system is a system restart (microsoft says this in so many words). If it's not updating successfully, you could broadcast a WM_SETTINGCHANGE message in script like some Microsoft KB's mention, but last I looked into this it could cause a hang in the script on UAC enabled machines. But of course, it depends on exactly what's going on with your install. I'd probably start with the sanity check to make sure the MSI log mentions it's installing the variable during the WriteEnvironmentStrings action. It's possible the vendor MSI doesn't have this action sequenced! Or possible that something else is going on (maybe the variable is associated with a component that's not being installed). Once you establish in the log that it's getting installed OK, then worry about whether you need to reboot the machine or similar. ... View more

Use a powershell script to run it as a prerequisite. Nuget.org gives this as a one-liner to install it: Install-Package Microsoft.SqlServer.SqlManagementObjects -Version 140.17218.0 ... View more

Sure, I've made this work. Sounds like something is not set up quite right is all. My recommendations: 1. Add a Debugger.Launch() call at the start of the method. If it's not hit, it's likely an assembly load error. 2. Before taking further action, check to see if maybe you've got references that the *.dll needs as local reference (they aren't included automatically by InstallShield). 3. If you don't have a dependency issue, debug the assembly load log. 4. Sanity check: Make sure your method is declared as Public Static. ... View more

rguggisberg wrote: nResult only tells you if the 'Launch' was successful. You will need to use something else to detect pass/fail of the PS script. One way to accomplish is to write a temporary value to the registry in PS and interrogate that in IS. One could do it that way, if you're in control of the scripts. (You may not always have that option, and be forced to consume them verbatim for whatever reason) The problem with Powershell is that you are going to want to parse the stderr stream from the process, which AFAIK you can't do from Installscript. I'd personally switch to a C# based custom action for launching the Powershell, because there's .Net classes for hosting Powershell scripts in managed code. I haven't worked with it, but there may be some way of doing this as well with the native Powershell Custom Action support. ... View more

It's been a while since I messed with this, but I've written web.config encrypt/decrypt routines using the .Net API. IIRC, you can use the same API's to decrypt a web.config that was encrypted via aspnet_regiis.exe. ... View more

Yes, if you set a public property in the UI sequence and need to use it in the Execute sequence, it always has to go in the list of SecureCustomProperties ... View more

You are going to have to be more specific. Plug in for what? Different plugins install in different ways. Some just copy a *.dll to the right folder (like Notepad++), but some require file registration, registry entries, XML file entries, or who knows whatever else? ... View more

You have a bigger problem: Someone at some point in the past started embedding Windows OS executables into your setup. You need to audit what was using IISReset.exe, and make it work without that file in the Binary table. The fix will be removing that record from the Binary table and figuring out what was using it (and fix it to just run the command from a batch file or something). ... View more

Windows Installer itself registers the file path via the keypath of a component name provided in the ServiceInstall table: https://msdn.microsoft.com/en-us/library/windows/desktop/aa371637(v=vs.85).aspx So, there's not much you can do here to just add quotes.using the native InstallShield functionality. If I had to take a wild guess on how to trick Windows Installer to add quotes, it'd be to install the service executable to a path which contains a space in a folder name. Failing that, as you mention, a custom action. Don't go down the .Net Installer class route though, if you can avoid it. ... View more

bgoldca wrote: I know this is an old topic, but I can't find any sufficient answers so I'm posting it again. I've found several pages that say that files cannot be overwritten unless the version of the file is higher than the existing file, but most say that using Always Overwrite should overwrite the files upon upgrade. Yet when I do a new install over an existing install or an upgrade about half of my files are overwritten and half are not and they're all marked as Always Overwrite. Please let me know your thoughts or if you have any questions. Thanks! Ben p.s. This is for InstallShield 2013 but that forum doesn't get many views so I'm posting it here. I think they should behave the same way. Post a log. That will tell us why. things to look out for: Features with an "Advertised" state during InstallValidate. (this means a component was removed across upgrades) Components that won't overwrite, denoted by "Disallowing Installation of component {xx} because xx" If nothing there, look for the FileCopy() operation during InstallFinalize which mentions that file. It'll tell you if it decides not to copy the file during InstallFinalize, and the reason. Being that these are clearly *.dll files, does restarting the machine upgrade the files? (there's a myriad of options for restart behavior, so it's easier to ask this question than: are the files locked? It may not be evident) I can't access it, but I guess you can request community access to some KB articles. This one is useful: https://flexeracommunity.force.com/customer/articles/en_US/HOWTO/Q200372 ... View more