Bug 3167

Windows Server 2012 R2 terminal server comptability 15 January, 2021

Walter Ruaro
08 August, 2019
Product: PowerBuilder Category: Other
Version: 2019 Build:
Classification: Publishing: Public
Priority: P3
Status: Verifying Reason:
Communication Status: Waiting for Appeon
Walter Ruaro 15 January, 2021
#45
Good afternoon

We haven't been able to fix the problem yet.

As you can see in the attached video, you can see that when doing a retrieve works, the second retrieve generates a crash in the application

This does not happen on PC operating systems. Only on Window Server.

Video:
https://youtu.be/_MlUCWz5zWM
armando herrera @Appeon 13 January, 2021
#44
Hi Walter,

I would like to check with you if the response provided has been helpful enough to resolve your case. If so, can we proceed to close the ticket?.
Otherwise, please let us know if we can provide you with any further assistance, remember you can always open another ticket any time you need it.  

Regards!
armando herrera @Appeon 23 December, 2020
#43
Hi Walter,

Thank you very much for your response!.

Resuming :
- Through Terminal Server the 64 bits application crashes in an uncontrolled way.
- The same application compiled in 32 bits, ie the same binaries in Windows 10 work correctly.
- It is compatible with Windows Server 2012 R2.
- Have used "PowerBuilder Runtime Packager" and generated a complete runtime installer. 

Were you able to test 2019R2 version? 
https://account.appeon.com/download

Please notice that we have no videos attached to this ticket from you to correctly follow-up the error, we have no way to see the code.

Were you able to identify the line where it crashes? 



Regards!
Walter Ruaro 16 December, 2020
#42
Screenshot_126.jpg (227KB)

Hi Armando.

We have previously included videos and images.

The problem continues to be in clients that access Windows 2012 operating systems by RDP.

I attach a screen

gracias
armando herrera @Appeon 11 December, 2020
#41
Hi Walter,  

We have been trying to keep in touch with you to find out about the resolution of this issue, we would like to continue with our support but without more information, we are in the need to close it in the next 3 working days, according to our internal help support policy but please remember you can always open a new ticket.
    
Regards
armando herrera @Appeon 23 November, 2020
#40
Hi Walter,

I would like to check with you if the response provided has been helpful enough to resolve your case. If so, can we proceed to close the ticket?. 
Otherwise, please let us know if we can provide you with any further assistance. 

Regards!
armando herrera @Appeon 05 June, 2020
#39
Hi Walter,

This issue has stopped due to a required test case, we wish to continue helping you but we need to collect more information about it. 

You can also send:
- Set of screenshots 
- A video 

Showing the necessary path to find the case so we can try to collect the info we need, unfortunately, we can't proceed with our analysis with the info we have so far. 

Thank you for your understanding!

Regards!
#38
Hi Walter,

Can you record a video debugging your application? 

Regards!
armando herrera @Appeon 09 March, 2020
#37
Hi Walter,
There are some functions that we do not support Terminal Services, but we would like to re-take this issue and find out what is wrong.

We know that time is very slippery but feel free to contact us at any time.


Regards!
armando herrera @Appeon 04 March, 2020
#36
Hi Walter,  

As I see following the thread of this conversation we offered you a remote session because we were not able to reproduce this issue with the info provided. 

Do you think we can re-take that option?

Regards!
Walter Ruaro 02 March, 2020
#35
We still have the same problem reported in the videos we have sent.
armando herrera @Appeon 18 February, 2020
#34
Hi Walter,

Since you are testing until May. Do you think we can close this ticket?. 
Otherwise, let us know if we can provide you with further assistance.

Remembering that you are always welcome to open another ticket when you start your new testing if necessary. 


Best Regards
Walter Ruaro 17 February, 2020
#33
138/5000
Hi.

The problem remains.

We will test 2019 R2 towards May of this year. We are currently working with 2019 Fix 2170

thank you very much
armando herrera @Appeon 07 February, 2020
#32
Hello Walter

Were you able to correct this issue? 
Please let us know if we can continue on close this ticket? otherways let us know if there is something else we can do for you. 

I also want to invite you to try our 2019 R2 Version with a lot of excellent new features.

Go to: https://docs.appeon.com/appeon_online_help/snapdevelop2019r2


Best Regards!
armando herrera @Appeon 10 December, 2019
#31
Hello Walter! 

I'm checking on tickets that are not concluded. 

Please let me know if you were able to solve the issue, otherwise, we can reschedule the pendant meeting any time this week. 

Regards!
cedric.pernet 03 October, 2019
#30
Hello Walter,

We consider this to be a specific issue with your working environment and we will be much more likely to solve it if we can personally address it as we mentioned earlier.

Please tell us the ideal day and time for your team to schedule a remote desktop session to address the issue.
Walter Ruaro 30 September, 2019
#29
good afternoon

You have advanced on this subject.

Would you have any answers to give us?
Walter Ruaro 30 August, 2019
#28
Hello
When do you have it?

Monday?
cedric.pernet 30 August, 2019
#27
Hello Walter, 
We are still considering both of your issues, but we will need more information on them and possible a remote session. 

Would you be available to schedule a remote session with us?

-Cedric
Walter Ruaro 23 August, 2019
#26
good
We must cancel.

Unfortunately we do not have availability at this time.

Please replan.
cedric.pernet 23 August, 2019
#25
Please check your email to following the invitation, the meeting will start shortly.

-Cedric
Walter Ruaro 23 August, 2019
#24
Hello
We're waiting

thank you
Walter Ruaro 22 August, 2019
#23
okay.

We look forward to the invitation.

regards
cedric.pernet 22 August, 2019
#22
Sorry Walter, 
I correct the time to appoint it to 12pm CST.
cedric.pernet 22 August, 2019
#21
Hello Walter,

We will send you an invitation for tomorrow's remote session at 10:00am CST.

-Cedric
Walter Ruaro 22 August, 2019
#20
Hi.

Excellent. David will be in the session. I will join if I can arrive.

What time could it be?

Thank you
cedric.pernet 21 August, 2019
#19
Hello Walter,
Me and my supervisor are fluent Spanish speakers so naturally we accept to address the session in Spanish.

-Cedric
Walter Ruaro 21 August, 2019
#18
Hi.

Is there a possibility that it is in Spanish?

Our developer and who is on these issues handles English in a limited way.
 
If it is not possible, I will try to be myself or someone from the team that can act as a translator.

thank you
cedric.pernet 20 August, 2019
#17
Hello Walter,

Sorry for the delay, 
We would like to appoint a remote session and a call with you to try and solve both of your issues (regarding ticket "Soap FAULT using httpclient" ), we estimate that the best time to do this would be on Friday morning on CST.

Please let us know if you are available for this appointment.

-Cedric
Walter Ruaro 16 August, 2019
#16
Screenshot_106.png (41KB)

Screen with crash
Walter Ruaro 16 August, 2019
#15
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
#14
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
#13
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
#12
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
#11
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
#10
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
#9
bug3167_event.zip (238KB)

Good morning.

I attached required information.

Best regards
cedric.pernet 09 August, 2019
#8
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
#7
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
#6
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
#5
(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
#4
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
#3
Sorry. I correct myself.
It's about virtualization
Walter Ruaro 08 August, 2019
#2
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
#1
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