Dear Customers,

The PolySync Support Center is now just for submitting tickets to our support team. All articles and tutorials have been moved to the new PolySync Help Center and the content below will be removed shortly.

Thank you,
The PolySync Team

DTC 115

Description from the terminal: 

License is not valid, psync_init() failed with return DTC Code 115

What this really means: 

All PolySync nodes must call the function psync_init() to become a participant on the PolySync bus. A requirement to becoming a participant is having a valid license. Without a valid license PolySync nodes cannot execute and they will throw DTC Code 115.

Resolving:

If you know that you have a license but are receiving DTC 115, or the license tool reports that no license is detected, you can remove the local cache files and re-download the license capabilities from the server.


$ rm -f /usr/local/polysync/db/am* 
$ polysync-license-tool 

*****************************
*** PolySync License Tool ***
API Build Version: 2.0.0-1454247166
System Design File: "/usr/local/polysync/db/psync.sdf"
host_id: "(Ethernet) XX7B9XXB0DXX"
ip_address: "AUTO"
license_file: "(null)"

checking for available capabilities
*****************************

The PolySync license model uses cache files on the local machine to represent the license. The license itself is stored in the back-office license server and is broken up into capabilities. With an internet connection you can update your local cache files to match the license server.

 


$ polysync-license-tool 

*****************************
*** PolySync License Tool ***
API Build Version: 2.0.0-1454247166
System Design File: "/usr/local/polysync/db/psync.sdf"
host_id: "(Ethernet) XX7B9XXB0DXX"
ip_address: "AUTO"
license_file: "(null)"

checking for available capabilities
*****************************

Troubleshooting:

You can verify your current license with the license tool and verify that it exists, is valid or expired:

$ polysync-license-tool -q

*****************************
*** PolySync License Tool ***
API Build Version: 2.0.0-1454247166
System Design File: "/usr/local/polysync/db/psync.sdf"
querying system license
host_id: "(Ethernet) XX7B9XXB0DXX"
ip_address: "AUTO"
license_file: "(null)"

number of features in file "no-file": 0

number of features in trusted storage: 0

number of features in trials storage: 5
1: analytics 99.99 11-mar-2016 uncounted    HOSTID=ANY      START=11-feb-2016
     Valid for acquisition
     Not valid for serving
2: c_api 99.99 11-mar-2016 uncounted    HOSTID=ANY      START=11-feb-2016
     Valid for acquisition
     Not valid for serving
3: fault_monitoring 99.99 11-mar-2016 uncounted    HOSTID=ANY      START=11-feb-2016
     Valid for acquisition
     Not valid for serving
4: pro 99.99 11-mar-2016 uncounted    HOSTID=ANY      START=11-feb-2016
     Valid for acquisition
     Not valid for serving
5: rnr 99.99 11-mar-2016 uncounted    HOSTID=ANY      START=11-feb-2016
     Valid for acquisition
     Not valid for serving

*****************************

Shown above is the printout from the license tool query showing a valid trial. Shown below is the printout expected when no license or trial exists on the host.

$ polysync-license-tool -q

*****************************
*** PolySync License Tool ***
API Build Version: 2.0.0-1454247166
System Design File: "/usr/local/polysync/db/psync.sdf"
querying system license
host_id: "(Ethernet) XX7B9XXB0DXX"
ip_address: "AUTO"
license_file: "(null)"

number of features in file "no-file": 0

number of features in trusted storage: 0

number of features in trials storage: 0

*****************************

If the license is invalid meaning that the capabilities have expired you can expect output matching this:


*****************************
*** PolySync License Tool ***
API Build Version: 2.0.0-1454247166
System Design File: "/usr/local/polysync/db/psync.sdf"
querying system license
host_id: "(Ethernet) XX7B9XXB0DXX"
ip_address: "AUTO"
license_file: "(null)"

number of features in file "no-file": 0

number of features in trusted storage: 0

number of features in trials storage: 5
1: analytics 99.99 8-dec-2015 uncounted    HOSTID=ANY      START=9-nov-2015
     Not valid for acquisition: Requested feature has expired
     Not valid for serving
2: c_api 99.99 8-dec-2015 uncounted    HOSTID=ANY      START=9-nov-2015
     Not valid for acquisition: Requested feature has expired
     Not valid for serving
3: fault_monitoring 99.99 8-dec-2015 uncounted    HOSTID=ANY      START=9-nov-2015
     Not valid for acquisition: Requested feature has expired
     Not valid for serving
4: pro 99.99 8-dec-2015 uncounted    HOSTID=ANY      START=9-nov-2015
     Not valid for acquisition: Requested feature has expired
     Not valid for serving
5: rnr 99.99 8-dec-2015 uncounted    HOSTID=ANY      START=9-nov-2015
     Not valid for acquisition: Requested feature has expired
     Not valid for serving

*****************************
 

If you still receive the DTC 115 error you will need to contact the Support Engineers on the Help Desk.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.