Created a new Powershell script with only one line to test the packager out.
The line is:
get-user jsmith
Created a script package. The created script.exe does not launch.
Powershell.exe does launch from the Start-Run area on the same machine.
Are there files other than the test.ps1 that have to be added to the script in order to get it to launch?
What should the engine type be?
What is the difference between using STA and not?
Thanks.
PrimalScript 2009 Packager not launching exe's
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Which engine did you actually specify?
When you say "does not launch", do you get an error message?
STA refers to the threading model, vs. MTA. Not important unless you do Windows Forms with it.
When you say "does not launch", do you get an error message?
STA refers to the threading model, vs. MTA. Not important unless you do Windows Forms with it.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
So MTA used when a form is involved?
The error is:
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
I've tried basically all the engine types for PowerShell. Unsure which would be which and what the difference is between the choices.
The error is:
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
I've tried basically all the engine types for PowerShell. Unsure which would be which and what the difference is between the choices.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
What OS is this? 64/32 bit?
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Wait a second. Where is "get-user" from?
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
Running on Windows XP 32bit.
Get-User is just a powershell command. Ultimately though we'd want to be using Exchange and Quest addons for PowerShell and have them all packaged in as well.
Get-User is just a powershell command. Ultimately though we'd want to be using Exchange and Quest addons for PowerShell and have them all packaged in as well.
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Get-user is not a standard PowerShell cmdlet, neither from V1 or V2.
If you use snapins you need to load them in your script since packages do not process any profiles to avoid dependencies on specific machines.
If you package with one of the command line package types, please understand that you need to launch the exe from a console window. Otherwise you see a brief console flashing at best.
If you use the Windows package type, you need to create a form or a window of some kind, otherwise it won't do much.
If you use snapins you need to load them in your script since packages do not process any profiles to avoid dependencies on specific machines.
If you package with one of the command line package types, please understand that you need to launch the exe from a console window. Otherwise you see a brief console flashing at best.
If you use the Windows package type, you need to create a form or a window of some kind, otherwise it won't do much.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
Changed the script to now be:
Add-PSSnapin quest.activeroles.admanagement
Add-PSSnapin *exchange*
get-user benw
Packaged it again. Still no good. Same error.
Do I need to add those files somehow? Where would I maybe find them and how would they added to the package?
Add-PSSnapin quest.activeroles.admanagement
Add-PSSnapin *exchange*
get-user benw
Packaged it again. Still no good. Same error.
Do I need to add those files somehow? Where would I maybe find them and how would they added to the package?
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Please zip the exe you produced and email it to support@sapien.com
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.