• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Creating PB Executable with Terminal Server Aware flag not set

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Creating PB Executable with Terminal Server Aware flag not set

  1. How-to
1
Votes
Undo
  1. Phil Wallingford
    Phil Wallingford
  2. PowerBuilder
  3. Thursday, 2 January 2020 16:43 PM UTC

A couple developers have asked whether the executable can be created without the TSAWARE flag not set.

When an application is not Terminal Server aware (also known as a legacy application), Terminal Server makes certain modifications to the legacy application to make it work properly in a multiuser environment.  This is true for many PowerBuilder applications built with older versions of PB.

This behavior is controlled by a setting in the PE header, TSAWARE, whose default was changed in Microsoft .Net 3.5 Framework SP1. When this flag is set, Terminal Server will not make certain changes to the application.  This means that recent PowerBuilder versions create executables with this flag set and may not function as expected (or tested).

We have introduced a build option in PowerGen to control the state of this flag.  Let us know if you want to try this.

Phil (E. Crane Computing)

Debugger cannot resolve datatype of object
Set Limit size take Photo on Appeon Mobile Apss
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 2 January 2020 19:54 PM UTC
  2. PowerBuilder
  3. # 1

You mention the default changing in .Net but what about standard PowerBuilder desktop apps?

Does this apply to apps run using RDP?

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 13 July 2020 20:29 PM UTC
Hi Roland;

FYI: RDP seems to also be affected as well. We have recently had a Support Ticket for an RDP issue that was resolved by changing the TSAWARE flag.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Phil Wallingford
Phil Wallingford Accepted Answer Pending Moderation
  1. Thursday, 2 January 2020 22:53 PM UTC
  2. PowerBuilder
  3. # 2

Maybe someone from Appeon can help us with this.  I assumed the problem might be that PowerBuilder uses some Windows services in creating the executables and the services changed when a later version of Visual Studio was used.  I know, a lot of assumptions.

Phil

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 3 January 2020 16:28 PM UTC
Hi Phil ... the TSAWARE issue was introduced by SAP in PB 12.6. Appeon is looking to fix this issue in the near future and is currently tracking this problem under ticket # 3637.

PB Developers can work around the issue by updating their PB App EXE's, as follows ...

editbin /TSAWARE:NO <filename>.exe

FYI: https://docs.microsoft.com/en-us/cpp/build/reference/editbin-reference?view=vs-2019

HTH

Regards ... Chris

  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 14 July 2020 15:22 PM UTC
  2. PowerBuilder
  3. # 3

Chris -

   Is the TSAWAARE an issue for client/server apps using PB2019R2? If so, where does the fix you mention get placed?     "editbin /TSAWARE:NO <filename>.exe"


Thanks You,

Olan

Comment
Roland Smith
  1. Roland Smith
  2. Tuesday, 14 July 2020 17:05 PM UTC
editbin is a command line tool that comes with Visual Studio. It will be somewhere under:

C:\Program Files (x86)\Microsoft Visual Studio\201#\Enterprise\VC\Tools\MSVC
  1. Helpful
Olan Knight
  1. Olan Knight
  2. Tuesday, 14 July 2020 17:11 PM UTC
Thanks, Roland!
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 14 July 2020 20:24 PM UTC
BTW: Only required when the App EXE is run under Citrix or RDP

Note: The current plan is to add this compile option in the Project Painter for PB 2019 R3
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.