Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Support for all customers who have purchased a SAPIEN PowerShell Studio product license. This forum does not offer a response time guarantee.
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.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
mark106
Posts: 19
Joined: Mon Jan 09, 2017 8:15 am

Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Post by mark106 » Tue Apr 16, 2019 3:33 am

Hi,

I have the same issue as posted here:

viewtopic.php?t=13822 - "Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore"

i.e. complied exe doesn't run since the .161 update, no errors, just disappears.

I reverted to an older version of PowerShell Studio and the compiled .EXEs are ok again.

The EXE runs elevated and the build options have the embedded default manifest for elevation. When the exe is run the prompt for these credentials appears - but nothing thereafter.

OS - Windows 7 Pro 64 bit
Currently running Studio v5.6.157 (reverted to)

Target: Windows 64 bit
V3 Host (Windows Forms)
STA mode
generates .config file

project containing a .psf file



p.s. should I be able to post to an existing topic, rather than creating a new one? I don't seem to be able to.

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Post by davidc » Tue Apr 16, 2019 8:05 am

Thank you for contact us. We are working on a fix and we will release a new service build as soon as possible.

To ensure it is the same issue, please answer the following questions:

1. Are you using UTF-8 encoding?
2. Do you have any Unicode characters in your script?

P.S. Creating a new topic is the preferred method. This way we don't have cross-talk confusion.
David
SAPIEN Technologies, Inc.

User avatar
mark106
Posts: 19
Joined: Mon Jan 09, 2017 8:15 am

Re: Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Post by mark106 » Tue Apr 16, 2019 8:26 am

Thanks David,

Yes, the scripts are shown as UTF-8

It is also using the embedded webBrowser which is loading a UTF-8 encoded page. This page is loaded into variables and "parsed" within the script.

Best regards,

Mark

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Post by davidc » Tue Apr 16, 2019 8:45 am

I recommend temporarily selecting a Command line engine in the Packager Settings so that you can see if there are any errors. The forms engine suppresses all output.
David
SAPIEN Technologies, Inc.

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Post by davidc » Fri Apr 19, 2019 6:47 am

The v5.6.162 service build is now available and should resolve this issue.
David
SAPIEN Technologies, Inc.

User avatar
mark106
Posts: 19
Joined: Mon Jan 09, 2017 8:15 am

Re: Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore.

Post by mark106 » Tue Apr 23, 2019 5:34 am

Yes, all working with .162.

Many thanks.