Skip to Content
0

SAP ASE 16 via ODBC on Windows Server 2016

Nov 07, 2017 at 07:09 PM

131

avatar image
Former Member

Hello,

We have an Powerbuilder (version 12.5.1 Build 4595 classic) application that runs on a Windows Server. The users connect to this machine using Remote Desktop and run the app, which is client-server and it connects to SAP ASE 16 via ODBC. Everything works great on Windows Server 2008 R2 Standard.

Now, we are installing Windows Server 2016. If the user has admin rights, everything works fine, but if the user does not have admin rights, the application gets critically slow and the memory consuption of the user session increases significantly. This was the only difference between users that we found. Does anyone knows something about this? Or maybe some report that could lead us to errors, etc. Thanks in advance,

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Shenn Sellers Nov 08, 2017 at 05:42 PM
1

One problem could be that PB 12.5.1 does not support Windows Server 2016.

Sybase PowerBuilder version 12.5.1 supports these operating systems:

  • Microsoft Windows XP with Service Pack 3
  • Microsoft Windows Vista Business Edition 32-bit and 64-bit with Service Pack 2
  • Microsoft Windows 7 Professional 32-bit and 64-bit with Service Pack 1
  • Microsoft Windows Server 2008 32-bit and 64-bit with Service Pack 2 (runtime only)

Your best bet is to upgrade to PB 2017 which supports Windows Server 2016 and see how it performs.

Appeon PowerBuilder 2017 supports these operating systems:

Windows 7 32- or 64-bit with SP1, Windows 8.1, Windows 10 32- or 64-bit, Windows Server 2008 32- or 64-bit with SP2, Windows Server 2012 R2, or Windows Server 2016. (Supports Windows Server 2008/2012/2016 runtime only, not development.)

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Thanks for the info Sheen.

0
avatar image
Former Member Nov 14, 2017 at 01:46 PM
1

Hi Shenn;

Have you tried using the ASE 16 native client instead of ODBC?

Regards ... Chris

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

I would go down this road, the native client should work better anyway.

0