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

Resolved PSLib5.dll causing a socket error

  1. Issue
0
Votes
Undo
  1. Teresa MacDonald
    Teresa MacDonald
  2. PowerBuilder
  3. Wednesday, 4 March 2020 17:11 PM UTC

We have an application that was originally developed in PowerBuilder 6. It was migrated along up to 12.5.2. We have now migrated it to PowerBuilder 2019. We are having an issue when using PSLib5.dll. This dll is dated 1996. Does anyone know if there is a newer version of it?

PB 2017R3 runtime installation ended prematurely
Code to print active sheet does not work in PB2019
Responses (5)
David Peace
David Peace Accepted Answer Pending Moderation
  1. Thursday, 5 March 2020 16:43 PM UTC
  2. PowerBuilder
  3. # 1

Hi

As I understand it this has worked fine for PB12.5.2, does that include this one user that failes now. I.e. can you run te pb12.5.2 on their machine and it works?

You say that you get a socket error, I wonder if there is a firewalling issue blocking the connection on that PC?

Comment
There are no comments made yet.
Teresa MacDonald
Teresa MacDonald Accepted Answer Pending Moderation
  1. Wednesday, 4 March 2020 19:53 PM UTC
  2. PowerBuilder
  3. # 2

Thank you for your suggestions.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 4 March 2020 20:01 PM UTC
FWIW: If the user(s) having the problem are W10 based. What happens when they run the App as ADMIN?
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 4 March 2020 18:28 PM UTC
  2. PowerBuilder
  3. # 3

Teresa;

  The "PSLib5" DLL is from a 3rd party product known as PowerSocket. The product is now long gone along with the vendor. I suspect that your App using this for some sort of TCP/IP (socket) processing. However, PowerSocket's DLL is probably based on old ANSI 32 bit code. Since PB 10.0 of course, PB is now Unicode based as well. So moving up to any higher level of PB 10.0 or higher would probably encounter this run-time issue after migration.

  My suggestion would be to replace the PowerSocket DLL with something like Chilat or SocketWrench (as a few examples) ...

Chilat: https://www.example-code.com/powerbuilder/socket.asp

SocketWrench :  https://sockettools.com/socketwrench

  You could also try Roland's free TCP/IP socket code for PB as well ...

https://www.topwizprogramming.com/freecode_winsock.html

HTH

Regards ... Chris

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 4 March 2020 18:52 PM UTC
Teresa said it worked fine on PB 12.5.2 and only one user's machine has problem.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 4 March 2020 19:40 PM UTC
Hi Armeen .. Yes sorry - I only saw Teresa's later reply after I was looking at the original post.

Hmmm ... could this be an issue of W7 vs W10 users?
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Wednesday, 4 March 2020 21:49 PM UTC
The winsock example comes with PB 10.5 and 12.6 versions. The 12.6 version is '64 bit ready'.
  1. Helpful
There are no comments made yet.
Teresa MacDonald
Teresa MacDonald Accepted Answer Pending Moderation
  1. Wednesday, 4 March 2020 17:47 PM UTC
  2. PowerBuilder
  3. # 4

Compiled in 32 bit. We have several customers using the same app. but only one having this issue. unable to determine the cause. I suspect it is their environment.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 4 March 2020 17:57 PM UTC
If only one of your users has the issue then it is not a PB 12.5.2 vs. 2019 issue, and even you track down a newer version that most likely wouldn't solve your issue either. The almost sure-fire way to resolve is to wipe out the hard drive of your user's machine and setup everything clean (from either a default disk image your IT dept. has or the original installers if no default disk image). Of course, you could try to find what about the environment is causing the problem, but that could end up taking long time and still not discover the root cause.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 4 March 2020 18:15 PM UTC
But one thing I suggest to do is start by Googling the socket error message you are getting and see what are common Windows OS config issues that could cause that. You might get lucky... good luck!
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 4 March 2020 17:41 PM UTC
  2. PowerBuilder
  3. # 5

Are you compiling 64-bit?  Doesn't make sense that this DLL would work in 12.5.2 but not 2019... the core product source code is so similar.

Comment
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.