Installation Troubleshooting
Issue
Possible Resolution(s)
How do I enable Cross Origin Resource Sharing (CORS) in ThingWorx?
Enabling CORS allows requests to be made from a domain/website to an instance of ThingWorx that is deployed on a different server. This can be done by updating the Apache Tomcat web.xml file. Detailed process steps are available at https://www.ptc.com/en/support/article?n=CS229450.
After installing Tomcat and deploying the Thingworx.war file, Composer does not start and issues a "404 error: Application not found".
Verify the proper port on Tomcat is being used when accessing Composer.
Check for proxy server redirection.
Verify that the Thingworx.war file and corresponding folder in <Tomcat directory>/webapps have the correct case (Thingworx, not thingworx or ThingWorx).
* 
If the folder or WAR file were deployed with the wrong case, shut down the Tomcat server, remove the "thingworx" folder from webapps, and rename the thingworx.war file to the correct case and restart Tomcat.
Verify that the URL accessed is correct http://<server>:<port>/Thingworx (not http://<server>:<port>/ThingWorx)
If a "404 page not found error" is encountered in a RHEL environment after ThingWorx installation, verify the following steps as well:
Verify that the JDK is present in the /usr/lib/jvm/ folder. If the JDK is not present, then follow the steps to install Java in Install Java, Apache Tomcat, and ThingWorx.
Verify that the JAVA_HOME environment variable has the JDK path. For example,
JAVA_HOME = /usr/lib/jvm/jdk1.8.144
Problem deploying thingworx.war.
Verify that the ThingworxStorage/extensions/web-inf folder contains the licensing libraries (DLL files).
The following error appears when deploying ThingWorx:

org.apache.catalina.core.ApplicationContext.log HTMLManager:
FAIL - Deploy Upload Failed, Exception:
org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException:
the request was rejected because its size (90883556)
exceeds the configured maximum (52437800)
java.lang.IllegalStateException:
org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException:
the request was rejected because its size (90883556)
exceeds the configured maximum (52437800)
at org.apache.catalina.connector.Request.parseParts(Request.java:2871
The maximum file size in the Tomcat web.xml file must be increased (default is 50MB). This file is located at :
<path to Tomcat>\Apache Software Foundation\Tomcat
8.5\webapps\manager\WEB-INF
1. Open the web.xml.
2. Change the max-file-size and max-request-size to 104857600.
3. Save and close the file.
4. Restart Tomcat.
The following error message appears when importing a PTC licensed extension:
is licensed but cannot find feature in license.bin file
Visit the Manage Licenses section on the PTC Support site to confirm the correct license file that matches your entitlement. For further assistance with your licenses, contact the License Management team.
The following error message appears when attempting to undeploy ThingWorx:
FAIL - Unable to delete [<path to Tomcat>\webapps\Thingworx].
The continued presence of this file may cause problems.
Due to FlxCore64.dll
(<path to Tomcat>\webapps\Thingworx\WEB-INF\extensions\FlxCore64.dll)
Remove -Djava.library.path from Tomcat’s Java configuration before undeployment. Refer to this technical support article for more information on this error and solution.
An error message, similar to the following, appears in the ConfigurationLog.log:
2017-03-10 05:56:07.097-0500 [L: ERROR] [O: ] [I: ] [U: SuperUser] [S: ]
[T: localhost-startStop-1]
**********LICENSING ERROR ANALYSIS
2017-03-10 05:56:07.097-0500 [L: ERROR] [O: ] [I: ] [U: SuperUser] [S: ]
[T: localhost-startStop-1]
/Library/flexs is listed as a java.library.path but it does not exist.
/Library/blah is listed as a java.library.path but it does not exist.
/Library/zzz is listed as a java.library.path but it does not exist.
No flx dll files found.
Is the java.library.path set?
2017-03-10 05:56:07.097-0500 [L: ERROR] [O: ] [I: ] [U: SuperUser] [S: ]
[T: localhost-startStop-1]
**********END LICENSING ERROR ANALYIS
The log message verifies if there is an issue with the license file.
An error message, similar to the following, is thrown while the platform is starting:

2017-06-12 11:33:59.204+0530 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem]
[I: ] [U: SuperUser]
[S: ] [T: localhost-startStop-1] [message: The size of provided data is incorrect.]
2017-06-12 11:33:59.205+0530 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ]
[U: SuperUser] [S: ] [T: localhost-startStop-1] ======================================
2017-06-12 11:33:59.205+0530 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ]
[U: SuperUser] [S: ] [T: localhost-startStop-1]
Invalid License file: /ThingworxPlatform\license.bin
2017-06-12 11:33:59.205+0530 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ]
[U: SuperUser] [S: ] [T: localhost-startStop-1] ======================================
2017-06-12 11:33:59.205+0530 [L: WARN] [O: c.t.s.ThingWorxServer] [I: ]
[U: SuperUser] [S: ] [T: localhost-startStop-1] Shutting down the Platform.
The license file may have been opened/edited/saved in a browser. Download the license file again, rename it to license_capability_response.bin, and place it in ThingworxPlatform folder without editing or saving it.
If a license is not generated and the following error message is generated:
Caused by: java.lang.RuntimeException: Failed to create SecurityManager, Failed to load SecretProvider
at at com.thingworx.security.SecurityManagerBootstrapper.init(SecurityManagerBootstrapper.java:108)
at at com.thingworx.security.SecurityManagerBootstrapper.init(SecurityManagerBootstrapper.java:74)
at at com.thingworx.system.configuration.PlatformSettings.<init>(PlatformSettings.java:1704)
at at com.thingworx.system.configuration.PlatformSettings.getInstance(PlatformSettings.java:2597)
at ... 62 common frames omitted
Verify that the Tomcat user has Read and Write permissions to the ThingworxStorage and ThingworxPlatform folders.
Was this helpful?