Questions? Feedback?powered byOlark live chat software
Bug 3167

Windows Server 2012 R2 terminal server comptability 16 August, 2019

Walter Ruaro
08 August, 2019
Product: PowerBuilder Category: Other
Version: 2019 Publishing: Public
Status: Verifying Priority: P3
Classification: Resolution:
Walter Ruaro 16 August, 2019
Screenshot_106.png (41KB)

Screen with crash
Walter Ruaro 16 August, 2019
Screenshot_105.png (28KB)

Hi.

Keep in mind that the fault we have in different facilities on the same type of operating system.

We have used "PowerBuilder Runtime Packager" and generated a complete runtime installer.

We install it on the computers that have the problem, and it persists.

See attached images.
Cedric Pernet 14 August, 2019
Hello Walter,

Even if you use no RichTextEdit controls, the purpose of sending you that article, was checking if it was the printer's drivers that were crashing and causing the application to not respond.

Are you using or incorporating any printer's drivers?
We are still working on your case, any additional info you can provide us can help us solve it.

-Cedric
Walter Ruaro 12 August, 2019
Good.

Fail in all listings. And none of the reported cases have RichTextEdit controls

We consider that the link sent to us does not apply with the error we are reporting
Cedric Pernet 12 August, 2019
Hello Walter,

One possible solution might be that a printer's drivers are crashing and causing the application to close as indicated on the log you uploaded on logs #1001, this is a common error specially with terminal servers.

Please try to follow this article and adapt it to your needs, we think it's related to your issue and may prove useful if you adapt it to your code:
https://www.appeon.com/developers/get-help/knowledgebase/opening-richtextedit-control-over-terminal-services-slow.html

Let us know if this works for you, I'll be waiting for your response.

-Cedric
Cedric Pernet 12 August, 2019
Thank you for the information Walter, 
We will be working to find the cause of the problem , if we require any additional info we will let you know.

-Cedric
Walter Ruaro 12 August, 2019
Within our tests that we have been carrying out, we have seen that if the retrieve does not bring records, it is no problem to do several times to retrieve.

Once it brings records, the second time the system crashes

watch video:

https://youtu.be/dguDFyp78Rc
Walter Ruaro 12 August, 2019
bug3167_event.zip (238KB)

Good morning.

I attached required information.

Best regards
Cedric Pernet 09 August, 2019
Hello again Walter, 

We are currently working on your case, but we need more information to address the issue.

Please provide the error that is shown on the crash window, click "View problem details".

If possible, enter to the the event log of the server (Visor de eventos), and filter to show all errors logged, please find the one you think is being logged on the moment of the crash and show it to us.
Thank you in advance.

-Cedric
Walter Ruaro 09 August, 2019
Hi Cedric

I attached the videos that I commented.

You have three scenarios:

- Virtualized Terminal Server on Windows 2012 R2 - Local Database Access
https://youtu.be/AkncTi_ffzE

- Windows 10 Client - Remote database access via VPN
  https://youtu.be/_gt9SRK3cFU

- Native Terminal Server on Windows 2012 R2
https://youtu.be/ntxuDpyVYNY

We stay tuned for anything else you need.
Walter Ruaro 09 August, 2019
Hi Cedric

The PowerBuilder Runtime is correctly installed.

Our application has an installer that includes the entire set of dll for the application to work properly.

It considers that we have an installation of approximately 800 positions in different sanatoriums and hospitals of the Argentine Republic.

I am preparing a video for you to see the behavior on different platforms.

Soon I am attaching it to you.

From already thank you very much
Cedric Pernet 08 August, 2019
(In reply to Walter Ruaro from comment #3)
Sorry. I correct myself.
It's about virtualization
It should work if the application is already correctly compiled and the runtime already installed on the virtual machine. -Cedric
Cedric Pernet 08 August, 2019
Hi again Walter,

Your application needs Powerbuilder Runtime Packager installed on the system to run properly, you can check this on the documentation on the following link: https://www.appeon.com/support/documents/appeon_online_help/pb2019/application_techniques/ch34s03.html#d0e23929

You can also check how to do this on the documentation on the following link: 
https://www.appeon.com/support/documents/appeon_online_help/pb2019/application_techniques/ch35s02.html

Should you require any additional info, let me know.

-Cedric
Walter Ruaro 08 August, 2019
Sorry. I correct myself.
It's about virtualization
Walter Ruaro 08 August, 2019
Hello

I answer each point:

1- No. 
Only Localized runtime files / Language pack for # 2082

2- Yes.

3- No. The application opens normally. But in a non-deterministic way it usually closes without showing any errors

4- native machine 

Version de Power Builder 2019 Build 2082
Cedric Pernet 08 August, 2019
Good morning Walter,

Yes, that kind of environment is supported,
Please make sure that your environment complies with the following list to be run correctly:
1.-Is PowerBuilder Runtime installed on the server?
2.-Do you have admin rights to both the application and the subfolders that it uses?
3.-Are there any antivirus, firewall or active directory that may block the application?
4.-Is the server a native machine (ie. not virtualized)? 

If after verifying these points the application still won't run, please provide the build number of your PowerBuilder and if possible, provide us with an example code to be run on that version of Windows Server.

-Cedric
Walter Ruaro 08 August, 2019
Good morning.

We are having problems with Windows Server 2012 R2 through Terminal Server. The application closes in an uncontrolled way.

The same application compiled in 32 bits, ie the same binaries in Windows 10 work correctly.

Could you confirm if it is compatible with Windows Server 2012 R2.

thank you
OS:
Windows Server 2012 R2 
Platform:
32-bit 
Database Type:
Microsoft SQL Server 
Database Version:
2014