Use Read Registry / Is MSI Setup Installed / other similar commands...

Add it to your project using the Project Manager, Dialogs node.

There is no logging for Run Program - since the function already has its own return parameter. The casing of the message box and your project title is still different - which doesn't help identify the issue. I am as curious as you are to find the cause of this problem! Unfortunately there's nothing ...

Run the setup in the debugger to find out why its acting up, I'd say?

You may call Delete Registry on the orphaned entry when changing your product name. Place the call right after (Un)Install MSI Setup - provided the call has succeeded. We have temporarily deprecated the support site, it will be coming back up soon with many fresh articles and publications. Sorry for...

Works for me just fine here. Did you actually un-check the "for all users" check-box?

What is the WinAPI CSIDL of the folder you want to obtain?

This is the TXT file, its not helpful. We need the actual script file - MIA - and not the full file, because we won't be able to build it due to missing files. Just trim the script down to the minimum size possible to illustrate the issue and provide the MIA script.

If you are based off of a single file installer, you should not invoke $EXEFILE$ but $SFXFILE$ because the $EXEFILE$ resources will vanish as you have found out. Please note that you really should be calling Reboot and Resume instead of what you are doing now. Microsoft guidelines require that any s...

Even if the issue is not always happening, if you are to send us a minimum script that launches your program over and over for instance, we should be able to see the problem. Run Program is a straightforward operation and there is nothing in it that could cause the message you are seeing to be displ...

If its saying it cannot find a dialog, and referencing an old folder, then something in your MPR file has gotten corrupted. Like I said, open it up, search for the path in question, and eliminate it. A dialog reference could never actually be folder specific. Maybe you are getting the error as part ...

Can you attach the project that reproduces this - just the minimum fragment necessary?

It looks like the alternate plug-in did work for you, then? What you have is not a connection error. Did you un-check the create database if absent option? I am glad that you are able to connect, but please let us know if there's any issues with database checking/creation on the alternate plug-in so...

Can you reproduce this with any program, or is it specific to the program you are using?

Does it occur only with Run Program, or also with Run Program As?

In a script that does nothing other than call your program, is the issue still present?

What version of InstallAware are you using?

Which setup command is this file a part of?

Can you reproduce this issue by removing all setup commands except the command that installs this file?