Showing results for 
Search instead for 
Did you mean: 

ASE/SYSAM thinks hostid is null [KBAs 2993255 / 2422577 ?]

0 Kudos

I'm in the process of replacing a VM (old=SUSE 11 / new=Ubuntu 20.04).

I've been able to get all but one of my SAP/Sybase software installations migrated successfully:

ASE 15.7 SP140                       # failure (more below)
ASE 16.0 SP03 PL07                   # success
RS 15.7.1 SP306                      # success
RS 16.0 SP03 PL07                    # success
Data Assurance 16.0 SP03 PL06        # success
SYSAM_2_4                            # success

The ASE 15.7 software installation completes successfully and I can successfully create a new ASE instance. There's just one issue, ASE's SYSAM component thinks the hostid is null (see last line from this errorlog snippet):

00:0000:00000:00000:2021/12/31 15:44:03.03 kernel  SySAM:  The hostid of this system does not match the hostid
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel  SySAM:  specified in the license file.
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel  SySAM: License feature name:  ASE_CORE
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel  SySAM: License hostid:        000011223344
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel  SySAM: License search path:   /opt/sybase/ASE_157_SP140/SYSAM-2_0/licenses/ASE.EV.lic:
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel  SySAM: FLEXnet Licensing error:-9,57.  System Error: 19 "(null)" 


  • all ASE/SRS/DA instances (other than the ASE 15.7 instance) are able to successfully check out the associated EV licenses (mix of served and unserved)
  • the ASE 15.7 and ASE 16.0 instances are using the same EV license
  • for the ASE 15.7 instance I get hostid=null for both served and unserved license
  • for the ASE 15.7 instance there are no problems if using the XE or DE license file, but this is expected since those license files are coded for ANYHOST (and hostid=null qualifies as 'ANYHOST')
  • I've successfully installed the i386 architecture and associated libs (into Ubuntu 20.04) and verified 32-bit apps do work in this 64-bit VM

I've also verified this behavior (hostid=null) with the associated SYSAM/cpuinfo:

$ ./cpuinfo
License hostid:                                          <<<=== no hostid is displayed 
Detected 4 logical processor(s), 4 core(s), in 2 chip(s)

The RS 15.7.1 version of SYSAM/cpuinfo, running on the same VM, does show the hostid:

$ ./cpuinfo
License hostid:        000011223344                     <<<=== correct hostid displayed
Detected 4 logical processor(s), 4 core(s), in 2 chip(s)

KBA 2993255 looks like a possible match (ASE 15.0, invalid host, hostid = ' null').

KBA 2422577 looks like a match for the `cpuinfo` program generating hostid=null.

Question: Could someone with access to KBAs 2993255 and 2422577 respond with the resolutions to these issues?



View Entire Topic

Hi Mark,

We had a similar situation some years ago when we started using NIC binding - using multiple ethernet network adapters in the same server. The solution was to rename the connection to eth0, SySam 2.0 wouldn't work otherwise with what our network admin had named the connection.


0 Kudos


I've only got the one ethernet/network adapter on this VM but it was named ens33 so after making sure I had a good VM snapshot it was off to chat with Mr Google about how to change the name to eth0 ...

After a bit of OS wrangling (and a few restores back to that VM snapshot) I was able to rename the ethernet/network adaptor to eth0.

I've finally got my ASE 15.7 instance up and running under a (served) EV license!

General notes:

  • ASE 15.7 is a bit long in the tooth and doesn't seem to know how to handle the EValuation license type so getting the ASE 15.7 instance up and running with an EV license in an unserved license scenario is not doable (I can always revert back to the Developer (DT) license in this case)
  • ASE 15.7 can work with an EV license in a served license scenario as long as the license server is running a newer version of SYSAM (my standalone license server is running SYSAM 2_4 so no problems dealing with ens33 or eth0)
  • the ASE 15.7 version of SYSAM/cpuinfo now displays the (correct) hostid

Thanks for the tip!