Quick Action Run Program Failure

[mikenac]

AMS 6.0.2.0

I have run into an issue that is trully frustrating me.

I have a simple InstallShield installer in the CD_ROOT\AutoPlay\Docs\server\ folder. If I use the "Quick Action" "Run Program" action, it will fail with an error '1013: File Execution Failed'.

I have tried to use scripting directly with:

File.Run(_SourceFolder.."\\AutoPlay\\Docs\\server\\setup.exe", "", "", SW_SHOWNORMAL, true);



I have tried several variations of the working folder, etc.

This does not work and returns a simple '0'.

If I use File.Open() or choose the Quick Action "Open Document", my setup will be launched.

Does anyone have any clues on this one?

[Boaz]

AMS 6.0.2.0

I have run into an issue that is trully frustrating me.

I have a simple InstallShield installer in the CD_ROOT\AutoPlay\Docs\server\ folder. If I use the "Quick Action" "Run Program" action, it will fail with an error '1013: File Execution Failed'.

I have tried to use scripting directly with:

File.Run(_SourceFolder.."\\AutoPlay\\Docs\\server\\setup.exe", "", "", SW_SHOWNORMAL, true);



I have tried several variations of the working folder, etc.

This does not work and returns a simple '0'.

If I use File.Open() or choose the Quick Action "Open Document", my setup will be launched.

Does anyone have any clues on this one?

I am getting the same error also. The only thing that I changed recently, I upgraded to IE 7.0. Is there any solution for this? I am currently running the trial version, which I downloaded from the link sent by email. I hope this can get resolved before the trial runs out.

Any clues?

[RizlaUK]

ok, i might be wrong but i think installshield msi installers use starndard windows components for its runtime engine, so file.open would be right (because you want to open the msi with its default app, ie: windows installshield)

[Boaz]

This problem stinks. It does work, I have to manually set a scripts each time, but I have to do this for many programs that I want a button to "Run". I tried uninstalling & reinstalling, but to no avail. I'm throwing in the towel on this one! Well, Good thing it was only a trial.:wow

[RizlaUK]

This problem stinks. It does work, I have to manually set a scripts each time, but I have to do this for many programs that I want a button to "Run". I tried uninstalling & reinstalling, but to no avail. I'm throwing in the towel on this one! Well, Good thing it was only a trial.

i fail to see what the problem is, i explained why File.Run dosent work, and a script for each file "one line of code" is all it takes

if you are throwing in the towel already with ams, im sure you will NOT find anything else that will do the job as easy as "one line of code"

have you tryed the quick action for open document ?? as windows would see a msi package as a document of sorts and open it with the default viewer ie: installshield,

just apply a little brain power b4 you "throw in the towel" with a software development tool that is as easy to use as spreading butter on toast, its not ams at fault, its the msi installer package that relys on windows componants to make it work,

[AudioSam]

I had the same problem with Quick Action , Run Program.
I am not sure what happens but I know for sure thru testing
that it has to do with the new update.
If you can set up your version of AMS 6.0 on another computer,
don't allow update and carry your app to that computer you can then work on your app again , it will work as it did before.
Once you Build your program it will work.

This may not be the exact problem you were having , I did have a problem with all of my
run program from button properties not working after the update.These were to open
Note Pad , Calculator , Users, Control Panel, and several other Common windows Programs.
Some using .bat files and others using the path to the .exe files.

[AudioSam]

http://www.sendspace.com/file/shxtym

[bule]

.msi file is not a program, it's a database.

[Lorne]

What is the name and location of the file you're trying to run? Are you sure it's named "setup.exe" and that it is an executable file, and not just an .msi file that has been renamed?

If it's a .msi file (a.k.a. "Windows Installer"), it isn't an executable, renaming it to "setup.exe" won't change how it works. To run an MSI file you need the Windows Installer engine installed. Then you would either use a File.Open action, or run the Windows Installer engine "msiexec" and pass the .msi file to it as a command line argument.

Does the file run on its own if you run it from a command line? If you're getting an error trying to execute it, it could just be that the file is corrupted. Or, as I explained above, it might not be an actual "executable" file.

[Julia@ININ]

Coming from DemoShield to AMS6, I have to laugh at how quickly he was ready to throw in the towel. :lol AMS6 is like a breath of fresh air. I was also having problems with .msi's because I was trying to use the quick action 'run program'. I changed it to File.Open and have no problems. And, it's not like you have type a fresh one for every install - just duplicate and update your script to the appropriate msi. It's not so bad. Hope this helps someone else.

[Intrigued]

Side note, I recommend the original poster update AMS to the latest version. (press the F9 key inside of AMS).