1. Libby Engelbret
  2. PowerBuilder
  3. Tuesday, 15 May 2018 15:12 PM UTC

After applying some Windows Updates, I tried to start PB 12.6 and got an error message "Failed to initialize SySam licensing.  The mandatory property file pb126_sysam.properties is missing".  I Googled and found posts that said I should copy the file from my program files directory and replace it.  I did that, but I still get the error.  Another person said they needed to run PB as an administrator.  This does work, but I don't want to do this and it's now giving me messages about my source control software because I'm not logged in as the same person.  Any help would be greatly appreciated.

Libby Engelbret Accepted Answer Pending Moderation
  1. Tuesday, 22 May 2018 12:14 PM UTC
  2. PowerBuilder
  3. # 1

Thanks for all of the responses.  I didn't try all of the suggestions, but we ended up upgrading to PB 2017 and this solved the problem.  

Comment
There are no comments made yet.
Alfredo Aldama Accepted Answer Pending Moderation
  1. Wednesday, 16 May 2018 02:59 AM UTC
  2. PowerBuilder
  3. # 2
Hi, In the past I had this error, --------------------------- License Initialization --------------------------- Failed to initialize SySAM licensing. PowerBuilder is shutting down. A mandatory property is missing. To help diagnose the problem, you can enable logging by adding the following to the PB.INI file: [pb] LogSySAM=1 The log file is 'pb115_sysam.log'. --------------------------- Aceptar --------------------------- Solution Your pb115_sysam.properties file (in C:\Users\xxxx\AppData\Local\Sybase\PowerBuilder 11.5) seems corrupted... Try to replace it with the one from C:\Program Files (x86)\Sybase\PowerBuilder 11.5 I hope this can help you Regards
Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 15 May 2018 23:43 PM UTC
  2. PowerBuilder
  3. # 3

PBv12.1 b7055
Windows 7, SP1, 64 bit platform

My account is an administrator on my VM.

My entire VM was recently moved from one server to another in a different city.

I had to do the following:

1) Uninstall SYSAM
2) Re-install SYSAM v2.2 from the PBv12.6 install disks
3) Go to the SAP Launchpad website and generate a new License Key
4) Open LMTOOLS.exe and set the LMGRD.EXE selection to the lmgrd,exe file within the IPV6 folder
5) Download the new license to the SysM Licenses folder
6) Reboot.

That got SYSAM working.
Now you open PB, wait for it to say NOT VALIDATED, close PB, and open PB again.
That got PB working.


Good Luck,

Olan

 

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 15 May 2018 23:43 PM UTC
  2. PowerBuilder
  3. # 4

PBv12.1 b7055
Windows 7, SP1, 64 bit platform

My account is an administrator on my VM.

My entire VM was recently moved from one server to another in a different city.

I ahd to do the following:

1) Uninstall SYSAM
2) Re-install SYSAM v2.2 from the PBv12.6 install disks
3) Go to the SAP Launchpad website and generate a new License Key
4) Open LMTOOLS.exe and set the LMGRD.EXE selection to the lmgrd,exe file within the IPV6 folder
5) Download the new license to the SysM Licenses folder
6) Reboot.

That got SYSAM working.
Now you open PB, wait for it to say NOT VALIDATED, close PB, and open PB again.
That got PB working.


Good Luck,

Olan

 

Comment
There are no comments made yet.
Brad Wery Accepted Answer Pending Moderation
  1. Tuesday, 15 May 2018 15:34 PM UTC
  2. PowerBuilder
  3. # 5

I ran into the same issue recently:

https://powertothebuilder.com/blogs/2/12/power-builder-sy-sam-issue

​None of the solutions I found helped as is. I had to run as admin to get around it. I hope you have better luck.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 15 May 2018 15:31 PM UTC
  2. PowerBuilder
  3. # 6

Hi Libby;

   Have you tried this approach ...  click here?

Regards ... Chris

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.