Windows...
Started over with a new script from scratch. Able to create a package with that and had it launch with no issues. It pops up a windows that disapears very quickly that says something about being a test version.
The script simply had "get-date" in it.
Next packaged the larger script up again. It has the same output even though the actual script should draw a form on the screen prompting for input.
Any ideas?
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: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Windows? Ok. In order to diagnose this we cannot change more than one variable at a time. If you change machines, OSes and packages randomly I cannot determine what is going on.
So please provide what exact OS, service pack level, bit-ness and Powershell version you have for testing.
Then run the provided exe and tell me what the result is.
So please provide what exact OS, service pack level, bit-ness and Powershell version you have for testing.
Then run the provided exe and tell me what the result is.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
Windows XP Professional
Service Pack 3
32 bit
Output of $PSVersionTable
CLRVersion 2.0.50727.3603
BuildVersion 6.0.6002.18111
PSVersion 2.0
WSManStackVersion 2.0
PSCompatibleVersions {1.0, 2.0}
SerializationVersions 1.1.0.1
PSRemotingProtocolVersion 2.1
The exe you sent via download link seems to launch and close quickly.
Newly created exe with only "get-date" has same output.
Larger script that should eventually be packaged when created as a new package with a created form, etc., also has the exact same output.
Service Pack 3
32 bit
Output of $PSVersionTable
CLRVersion 2.0.50727.3603
BuildVersion 6.0.6002.18111
PSVersion 2.0
WSManStackVersion 2.0
PSCompatibleVersions {1.0, 2.0}
SerializationVersions 1.1.0.1
PSRemotingProtocolVersion 2.1
The exe you sent via download link seems to launch and close quickly.
Newly created exe with only "get-date" has same output.
Larger script that should eventually be packaged when created as a new package with a created form, etc., also has the exact same output.
- Alexander Riedel
- Posts: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
The exe I sent is a cmdline exe. Did you launch it from a command prompt? If you just double click it from Windows explorer it will just flash a shell window briefly like ANY Win32 command line exe.
Can you confirm that?
You cannot have a windows form and standard output in the same exe.
Windows doesn't work that way. Get-Date prints to stdout basically on a command line. If you want a Windows exe with a form you need to provide a field where you output the return from get-date.
Can you confirm that?
You cannot have a windows form and standard output in the same exe.
Windows doesn't work that way. Get-Date prints to stdout basically on a command line. If you want a Windows exe with a form you need to provide a field where you output the return from get-date.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
The one you created when launched from the command line does indeed return the date.
The one I created returns this:
"This script package was created with a
trial version of the SAPIEN Script Packager."
Nothing else happens with my get-date package.
The one with the form I mentioned is a much larger script that does indeed have a form generated when launched in a Powershell window before being packaged. After being packaged it returns the same trial version message as my get-date test script.
The one I created returns this:
"This script package was created with a
trial version of the SAPIEN Script Packager."
Nothing else happens with my get-date package.
The one with the form I mentioned is a much larger script that does indeed have a form generated when launched in a Powershell window before being packaged. After being packaged it returns the same trial version message as my get-date test script.
- Alexander Riedel
- Posts: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Ok, when you package that other script, what host do you select?
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
Package = "Package"
Output file = "c:temppackage.exe"
Engine type is set to:
SAPIEN PowerShell Host (Command Line)
Run STA is checked
Manifest = Embed a default manifest
Delete files after execute is unchecked.
Output file = "c:temppackage.exe"
Engine type is set to:
SAPIEN PowerShell Host (Command Line)
Run STA is checked
Manifest = Embed a default manifest
Delete files after execute is unchecked.
- Alexander Riedel
- Posts: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
Ok, please refer to my previous post:
"I noticed that you have a manifest added, which some XP systems don't like for command line files."
So maybe you want to not select that on your machine.
Additionally, I am not quite clear what you are trying to do. You say you want to bring up a form, yet you use the command line host.
"I noticed that you have a manifest added, which some XP systems don't like for command line files."
So maybe you want to not select that on your machine.
Additionally, I am not quite clear what you are trying to do. You say you want to bring up a form, yet you use the command line host.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalScript 2009 Packager not launching exe's
How do I not add a manifest?
The ultimate goal is to package a large script that generates a form, prompts for user information and then creates a new user account.
Unable to get that script file to package properly and produce output, nor are we able to package and produce output from a newly created test script that does nothing but return the date. Scripts that we are packaging launch and then do nothing.
Again, if it's the manifest, how could that be fixed?
The ultimate goal is to package a large script that generates a form, prompts for user information and then creates a new user account.
Unable to get that script file to package properly and produce output, nor are we able to package and produce output from a newly created test script that does nothing but return the date. Scripts that we are packaging launch and then do nothing.
Again, if it's the manifest, how could that be fixed?
- Alexander Riedel
- Posts: 8478
- Last visit: Tue Mar 26, 2024 8:52 am
- Been upvoted: 37 times
PrimalScript 2009 Packager not launching exe's
First of all, please download the latest service build, 5.0.627 to make sure we have the same thing.
Second, there is a combo box on the packager options for the manifest.
See chapter 13 in the manual.
Second, there is a combo box on the packager options for the manifest.
See chapter 13 in the manual.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.