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

Resolved Licensing for PB 12.6

  1. How-to
0
Votes
Undo
  1. Phil Wallingford
    Phil Wallingford
  2. PowerBuilder
  3. Monday, 10 May 2021 18:20 PM UTC 
I have just getting a license failure trying to start PB 12.6.

Not sure when this would have started happening, but have been using 12.6 routinely to support customers for many years.

I know this is not supported by Appeon, but I'm curious if any of you have founds a solution/workaround.

Phil
PowerBuilder 2021 beta?
Calling, from one window, a function in another op...
Responses (4)
Phil Wallingford
Phil Wallingford Accepted Answer Pending Moderation
  1. Tuesday, 18 May 2021 18:51 PM UTC
  2. PowerBuilder
  3. # 1

Thanks for all of the suggestions; I really appreciate it.

I have (had) a stand-alone license and it seems that most of the suggestions are made for served licenses.

We released support for V12.6 in 2014.  Not aware of any particular issues with it, but just wanted to be able to run if needed.

Thanks again. Phil

Comment
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Monday, 10 May 2021 22:11 PM UTC
  2. PowerBuilder
  3. # 2

FYI -

My comments:
Finally, FINALLY got the environment fixed so that both PBv12.1 and PBv12.6 are running at the same time!!! The trick was to use the Volume serial number as the host id; i.e "DISK_SERIAL_NUM=1C2E8F6C" rather
than the Physical Address like "005056908029".

Use "vol C: " to get the volume serial number of the C drive.



From SAP:
During license generation process, please follow these steps

1.    On a VM that is accessed remotely, give "DISK_SERIAL_NUM=Disk Serial Id (without dash)" in the host id section.  (Disk serial id should be the system where license server is installed on)
For a real PC when you are using an ALTERNATE license, use the Physical Address of the PC as the Host ID.

2.    Give host name of the server

3.    Download the license file and save to C:\Sybase\SYSAM-2_0\licenses directory.
       Remove previous .lic  files if any.

4.    On a remotely accessed VM, restart the SYSAM service.
Alternate licenses are always stand-alone and do not use SySAM.

5.    Restart Powerbuilder

6.    Tools > Update License > Standalone Seat - Served or Continue with the pop-up wizard

7.    Give the IP Address of the license server where it is installed in the "Computer Name of the License Server"

8. Then Finish.

9. Restart Powerbuilder > Help > About Powerbuilder > Status should be valid


The whole intention of these steps is to establish a proper connection with the license server, where it contains the license.
If the proper connection is established, the license server automatically validates the license and will set the status to valid  mode.


Comment
There are no comments made yet.
Andrew Barnes
Andrew Barnes Accepted Answer Pending Moderation
  1. Monday, 10 May 2021 21:20 PM UTC
  2. PowerBuilder
  3. # 3

You're not accessing it via Remote Desktop are you?  The license will fail on that and give you a thirty day grace period, after which it will not work until you log in locally.  We have a dedicated build machine with ORCA scripts for all of out builds, and it was easier to remote to it rather than walk into the server room, but with the licensing, we would need an in-person login once a month.  Appeon licensing is more convenient in that respect.

Comment
Olan Knight
  1. Olan Knight
  2. Monday, 10 May 2021 22:14 PM UTC
FYI -

If you are using SYSAM, you can run PBv12.x when connected to a VM or a PC via RDP as long as the licence TYPE is a standalone SERVED license.
  1. Helpful
Andrew Barnes
  1. Andrew Barnes
  2. Monday, 10 May 2021 22:28 PM UTC
We were not using served licenses. I think there was a reason, but it has been a while since I administered PB12 licenses having upgraded to Appeon PB17 shortly after it came out. For us, it really became an issue, only after our network guys virtualized our build machine. Prior to that time we always logged in physically. With the machine virtualized, even in the server room, it was an RDP. Fortunately, our Service Desk software had a remote help feature that would not trigger SYSAM's remote protocol, so even though it was a remote connection, SYSAM treated the login as local and reset our 30 day grace period. And of course, now with Appeon, that is all behind us.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Monday, 10 May 2021 18:27 PM UTC
  2. PowerBuilder
  3. # 4

what license type do you use?  the 'default' one uses a NIC address - so if you use wired and wireless it will fail on the one.  disk is better, but is a PITA to setup.  

If you have to reregister, i suggest you do disk registration and do it in a VM so you can keep a copy of the VM in case something weird happens and you lose your license setup.

 

 

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.