Hi Rudolf;

The error message says InfoMaker. Are both PB and IM having this issue or just IM?

Regards ... Chris

Hi Chris,

both, Infomaker and PB

Rudi

Hi Rudolf

I had the same problem. I then switched off the remote support in the system.

After the restart, PB has taken the key. Try this.

André Rust

Hello Rudolf;

May I suggest:

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 to replace the Sysam Properties file with the one from C:\Program Files (x86)\Sybase\PowerBuilder 12.5. Its possible that your pb125_sysam.properties file (in C:\Users\xxxx\AppData\Local\Sybase\PowerBuilder 12.5) might have gotten corrupted

c) run a Sysam trace ...

Diagnosing SySAM Problems with PowerBuilder - SAP PowerBuilder - SCN Wiki

HTH

Hi Chris,

here is the log File

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

SyLAPI Version: Sybase Licensing API/2.2.0.8fc-r2-vc6/2208fc/32bit/1/P/NT (IX86)/Windows 2003/OPT/Wed Jan 16 10:25:53 2013
PB/IM Version: 12.5.2.5609
C:\Program Files (x86)\Sybase\Shared\PowerBuilder\PBSHR125.dll
Using properties file: C:\Users\Rudi Fürst\AppData\Local\Sybase\PowerBuilder 12.5\pb125_sysam.properties
Product Name: pb125GA
Instance Name: pb125GA
2016/11/16 13:23:19 Using licenses from: C:\Users\Rudi Fürst\AppData\Local\Sybase\PowerBuilder 12.5\PB125.lic
2016/11/16 13:23:19 Error (1000000): Assertion failed in c:\work\ase150\sysam2208fcx_cushion_vu\calm\dub\sysam\sylapi\src\generic\csource\prop.c at line 2030: ((mode[0] != 'r') && (mode[0] != 'w') && (mode[0] != 'a'))

sylapi_init() returned: 131244
--SySAM/SyLAPI Terminated--

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

regards

This could be triggered by special characters the server cannot parse.

See Knowledge Base Article 2147788 for more information.