Article - CS259533
"Failed to load FlxCore library" error is seen in Application log when attempting to start ThingWorx Platform
Modified: 17-May-2024
Applies To
- ThingWorx Platform 8.5 to 9.5
- Apache Tomcat
- Microsoft Windows Server
- Red Hat Enterprise Linux
Description
- ThingWorx fails to start with errors in \ThingworxStorage\logs\ApplicationLog.log (depending on the ThingWorx version)
[L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Failed to load FlxCore library. Ensure it's in PATH (Windows) or LD_LIBRARY_PATH(other platforms) or set with the VM arg, -Djava.library.path. Error message : com.flexnet.licensing.DllEntryPoint.entry([B)I [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] ==================================================================== [L: WARN] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Shutting down the Platform.
[L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [P: ] [T: main] Failed to load FlxCore library. Ensure it's in PATH (Windows) or LD_LIBRARY_PATH(other platforms) or set with the VM arg, -Djava.library.path. Error message : 'int com.flexnet.licensing.DllEntryPoint.entry(byte[])'
[L: ERROR] [O: ] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] C:\WINDOWS\Sun\Java\bin is listed as a java.library.path but it does not exist. Flex licensing file found: C:\ptc\Thingworx\webapps\Thingworx\WEB-INF\extensions\FlxCore64.dll. Flex licensing file found: C:\ptc\Thingworx\webapps\Thingworx\WEB-INF\extensions\libFlxCore.2016.08.dylib. Flex licensing file found: C:\ptc\Thingworx\webapps\Thingworx\WEB-INF\extensions\libFlxCore.so.2016.08. Flex licensing file found: C:\ptc\Thingworx\webapps\Thingworx\WEB-INF\extensions\libFlxCore64.so.2016.08
- Licensing issues prevent logging in to ThingWorx
- When moving the .war file into the Tomcat webapps folder, Tomcat crashes and the \ThingworxStorage\logs\ApplicationLog.log outputs errors
- ThingWorx fails to start after upgrading to a new release
- ThingWorx fails to start after upgrading Windchill (on the same server) to a new release
- ThingWorx fails to start with the below output when checking the status of Tomcat:
tomcat.service - SYSV: Tomcat Start Stop Restart Loaded: loaded (/etc/rc.d/init.d/tomcat; generated) Active: failed (Result: exit-code) since Wed 2024-04-17 15:00:46 CST; 40min ago Docs: man:systemd-sysv-generator(8) Process: 17988 ExecStart=/etc/rc.d/init.d/tomcat start (code=exited, status=1/FAILURE) Apr 17 15:00:42 ####.####.com systemd[1]: Starting SYSV: Tomcat Start Stop Restart... Apr 17 15:00:43 ####.####.com su[17995]: pam_sss(su-l:auth): authentication failure; logname= uid=0 euid=0 tty= ruser=root rhost= user=#### Apr 17 15:00:43 ####.####.com su[17995]: pam_sss(su-l:auth): received for user ####: 7 (Authentication failure) Apr 17 15:00:45 ####.####.com su[17995]: FAILED SU (to ####) root on none Apr 17 15:00:46 ####.####.com tomcat[17995]: Password: su: Authentication failure Apr 17 15:00:46 ####.####.com systemd[1]: tomcat.service: Control process exited, code=exited status=1 Apr 17 15:00:46 ####.####.com systemd[1]: tomcat.service: Failed with result 'exit-code'. Apr 17 15:00:46 ####.####.com systemd[1]: Failed to start SYSV: Tomcat Start Stop Restart.
- Tomcat does not start (crashes / terminates) with error in <tomcat_home>\logs\catalina.out:
WebApp stopping: Thingworx Server Application...OFF Thingworx Server Application...Cleaned up WebApp OFF [server = Apache Tomcat/8.0.44] Driver org.postgresql.Driver@45f5f6db deregistered
This is a printer-friendly version of Article 259533 and may be out of date. For the latest version click CS259533