1. John Raghanti
  2. PowerBuilder
  3. Wednesday, 15 April 2020 13:03 PM UTC

Hi all!

So we have been quarantined for a little over a month, no employee is allowed to access the physical work building for any reason. We have been given VPN access and RDP to our machines so that we can work from home.

In the last couple days, several developers are no longer able to open PB 12.5 with a message that the SySAM license was not validated. I think it's because we are not logging in locally to the machine.

Is there any way around this? We're not allowed in the building.

Thanks!

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 April 2020 16:34 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi John;

      If I recall correclty, this would only work with PB 12.x releases if you did not install the PB Licenses locally but instead, installed then on a SYSAM Server (free from Sybase in the day) that you would host internally. Then the SYSAM  server holds the PB licenses and, they are then served up dynamically from wherever you launch PB 12.x IDE (ie: RDP, VM, etc). Using the SYSAM server approach bypasses the MAC and/or HD serial number checking that a local PB license would do.

Regards .. Chris

Comment
There are no comments made yet.
David Sowray Accepted Answer Pending Moderation
  1. Wednesday, 15 April 2020 17:59 PM UTC
  2. PowerBuilder
  3. # 1

It's been a long, long time since I had a similar problem, but if I'm remembering correctly the problem was that if Powerbuilder sensed you were logged on via RDP *when the application started*, the license isn't revalidated.  The workaround I think I used to get around it was:

1) Log on to the machine via RDP and set up a task in Task Scheduler to start Powerbuilder in a few minutes.
2) Disconnect the RDP connection and go and make a cup of tea.
3) After the startup time has passed, reconnect using RDP. Powerbuilder should have started and the license revalidated.

I may be mis-remembering, but it's worth a try for a simple fix.

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 15 April 2020 14:36 PM UTC
  2. PowerBuilder
  3. # 2

Just FYI for other people reading this.  If you upgrade to Appeon versions of PowerBuilder you won’t have this issue.  We threw SySAM in the trash and built a new license mechanism from the ground up.

Comment
  1. mike S
  2. Wednesday, 15 April 2020 15:20 PM UTC
sysam was a nightmare. SAP's website for doing the licensing is even worse.
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 15 April 2020 13:19 PM UTC
  2. PowerBuilder
  3. # 3

The person who knows the login to subscribenet could generate local license files for all the developers home computers.

Comment
  1. mike S
  2. Wednesday, 15 April 2020 15:17 PM UTC
Roland is correct.



I believe it has to do with sysam using mac address of network card by default. since you are at home you are probably using wireless, while at the office you probably are using physical connection. A workaround might be to connect to your router directly via network cable...



Even if you don't use any of the new features of appeon's powerbuilder, it is stuff like this that should have made your company migrate to the newest version. smh

  1. Helpful
  1. Miguel Leeuwe
  2. Wednesday, 15 April 2020 15:42 PM UTC
Oh yeah, I remember being able to 'hack' by simply renaming my computer name and mac address! Ahhh ... the good old days!

:)
  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.