Hi Kevin;

       Been there, done that ... feel your SYSAM pain!  

Try one of these possible remedies, as follows:

a) Try this first ...

• Locate pb125_sysam.properties in C:\Users\yourusername\AppData\Local\Sybase\PowerBuilder 12.5
• Right click on the file and select "Properties".
• Click on the "Previous Versions" tab. Wait a bit until the File Versions box is populated.
• Select a version from a restore point when you knew PB to be working OK and then click the RESTORE button.
• PB should start normally

b) Try this second  ...

• Your pb125_sysam.properties file (in C:\Users\xxxx\AppData\Local\Sybase\PowerBuilder 12.5) might be corrupted...
• Try to replace it with the one from C:\Program Files (x86)\Sybase\PowerBuilder 12.5

HTH

Regards ... Chris

Hi Kevin, PB 2017 R3 is releasing July 31, 2018 (tomorrow).  Since you are not in production yet with PB 2017, I would recommend to focus your testing on PB 2017 R3 and release based on that version instead of PB 2017 R2. 

The reason for this recommendation is two folds:

1. PB 2017 R3 will be our long-term (LTS) support version: https://www.appeon.com/products/eol-policy.html

2. It has some nice little enhancements compared to R2:  https://www.appeon.com/developers/roadmap 

Since you are a licensed customer, you will be able to download R3 from the User Center (on or after July 31, 2018): https://www.appeon.com/user/center/index#download

No luck with either option.  There were no prior versions by doing properties, but there were a bunch of saved.bak files of both the license file and the properties file.  Tried various combinations with no luck.  Is there some way to reinstall the license files on the SySam server?

Is it possible that Sybase has shut something down since they EOL'd PB?  I guess that would explain the "vendor daemon" message.  That would be very bad as I'm totally out of the water right now and unable to work in PB 12.5.  Wonder if there's still any way to generate a standalone local seat license to fix this issue?

Hi Kevin;

  This is for PB 12.0 - but, its the same Sysam architecture for v12.5 ...

FYI:  https://archive.sap.com/discussions/thread/3773215

HTH

Regards ... Chris

I've had this happen, and it's no fun.
You do need to replace your license file with a NEW license file.

Follow the directions in the attached TEXT document do do exactly that.


Good Luck,
Olan

--- Well, crudzola! Apparently a ".txt" file is not supported ---
Fine. Here's the contents of the TXT file.

// -----------------  START ------------------

How to create a PBv12 Licese File
=================================

IPv4 address = 10.23.18.25 <--- to find: CMD>ipconfig /all

Physical address = 005056AC040E <--- to find: CMD>ipconfig /all

Volume serial disk = 1C171448 <--- to find: CMD> vol C: (remove the dash)

Computer name = OTHISISMYPC <--- to find: Computer -> Properties

Full computer name = OTHISISMYPC.workcorp.com <--- to find: Computer -> Properties

LaunchPad = launchpad.support.sap.com
SAP Customer ID = S0011111111
Password = YourSybasePassword

----------------------
Creating a license key
----------------------

Go to: https://launchpad.support.sap.com/
Password: YourSybasePassword

1) From MY HOME, click on the "License Keys" tile

2) Set filters: Customer = YourCustomerNumber (should already be listed)
Product = Sybase
Installation Number = YourInstallNumber

or select the installation number directly in the bottom field:
YourInstallNumber

3) Click on SAP PowerBuilder v12.6

4) If required, check in the old license file
On the bottom right, find the blue "EDIT" button and click it.

5) The data should be correct on the EDIT SYSTEM DETAILS window.
Click Continue.

6) On "3-Details" page, click the GENERATE button ->

Primary usage
Served License
Quantity = 1
Host Name = OTHISISMYPC.workcorp.com
Host ID = DISK_SERIAL_NUM=1C171448 <--- c:> vol c:
-> click GENERATE

-> scroll down and find the license you just created
-> above the license created click DOWNLOAD, then DOWNLOAD again
-> save into the LICENSES folder under C - SYSAM

7) Exit SAP Launchpad

-----
SYSAM
-----
1) Ensure that the SYSAM server is installed.
After it's been installed, copy the IPV4 and IPV5 folders back into
C:\sybase\SYSAM\SYSAM-2_0\bin

Then replace the LMGRD.EXE file in the BIN folder with the same file from the IPV6 folder.

2) Go to: C:\sybase\SYSAM\SYSAM-2_0\bin
run LMTOOLS.EXE

Page 1 = Service License File - select "Configuration using services"
Page 4 = Stop/Reread - click Reread License File

------------
PowerBuilder
------------

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

2. Restart Powerbuilder

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

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

5. Then Finish.

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

7. If step #6 fails, then
a) Go to:
C:\Documents and Settings\\Local Settings\Application Data\Sybase\PowerBuilder 11.5
and look for the pb.ini file

b) Get into the pb.ini file, and add " LogSySAM=2" as a separate line under the [PB] section.
This will create a pb115_sysam.log file in the same directory as the pb.ini file.
This file can be used by the Sybase tech support people (1-792-2735, option 3, option 3)

-------------------------------

A. When you upgrade your version of PowerBuilder, you need to upgrade your LICENSE FILE:

B. OPTIONAL: Add a new SYSTEM environment variable called LM_LICENSE_FILE (in all caps) and add the path and complete license file name as the value. Save.

// -----------------  END  ------------------

I'm glad your issue was resolved!

Later -
Olan