Installation Troubleshooting
ThingWorx platform needs to be restarted to update certain extensions
Explanation
One or more extensions were either dependant on an updated extension or contain JAR files (which is the case in all Java extensions).
Solution
Restart the Apache Tomcat platform.
Service call failed with status code 502 - Could not connect to environment: connect ECONNREFUSED server:port
Explanation
Your environment is not running.
Solution
Start your ThingWorx environment.
ENOENT: no such file or directory, scandir 'path'
Explanation
Entered path does not exist in the directory.
Solution
Enter a valid file path (or folder).
Could not find extensions in specified folder path 'path'
Explanation
Distribution (application) packages could not be found in the specified folder.
Solution
Ensure the distribution packages in the specified folder (check the file path) are accurate and run the installation process again.
Service call failed with status code 401 -
Explanation
Default message coming from ThingWorx. If empty, it may be a connection issue.
Solution
Check your credentials, make sure you are connected with the right username/password
Login failed for user 'username'.
Explanation
Connection to database failed for supplied user.
Solution
Check your credentials and try again. Make sure to also check if the database name is correct.
Failed to connect to server:port - Could not connect (sequence)
Explanation
Connection to database failed due to a mis-configured server and/or port. It may not be running.
Solution
Check your server configuration (name, port) and make sure you have access to it. Check if it is running as well.
ThingWorx: Receiving an HTML page content with 400 Bad Request
Explanation
Service call failed with status code 400 - HTTP/1.1 400 Bad Request Content-Type: text/html; charset=utf-8 Connection: close

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html>
<head>
<title>400 Bad Request</title>
</head>
<script type="text/javascript">
var regex = new RegExp(/http:\/\/(<^:>+):(<^/>+)/),
match = regex.exec(window.location.href);

if (match !== null) {
window.location = 'https://' + match<1> + ':' + match<2>;
}
</script>
<body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
</body>
</html>
This is caused by a mis-configured URL. ThingWorx server does not exist on that suppled URL or is not accessible.
Solution
Check accessibility for ThingWorx server and if the ThingWorx server exists on that URL.
Service call failed with status code 502 - Could not connect to environment: write EPROTO 45216:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:C:\Users\runneradmin\AppData\Local\Temp\pkg.c9bd35679b120888f042ed2c\node\deps\openssl\openssl\ssl\record\ssl3_record.c:332:
Explanation
An SSL connection attempt was made to a server that was not configured for SSL.
Solution
Either attempt your connection on an SSL-configured server, or turn use TlS off in your configuration. In the case of the interactive, respond N to the”Does ThingWorx use TLS”question.
The following dependencies are not compliant to version constraint for <application>: <list of dependencies>
Explanation
Staged (or if not staged, installed) dependencies do not match version constraint for an extension. Some extensions require a certain version of a dependency in order to work correctly.
Solution
Make sure the right version of an extension is installed. If needed, re-download the required app (like CORE) in order to get its dependencies with the right version.
The following dependencies are missing for <application>: <list of dependencies>
Explanation
Required dependencies are not staged or installed for an extension.
Solution
Ensure all required extensions are either staged for installation or already installed in ThingWorx. If needed, re-download the required app (like CORE) in order to get its dependencies with the right version.
The following apps do not meet minimum version required to run the automated installer
Explanation
To run the automated installer, there is a minimum version requirement to do so as some services will be needed to install. See System Requirements for the minimum version requirements.
Solution
Update all applications to the required minimal version, whether staged or installed.
Current ThingWorx 9 version is unsupported. Supported versions are 9.3.1 and above
Explanation
Minimal version accepted for TW9 environments are 9.3.1.
Solution
Upgrade to minimal 9.3.1 version. If using versions greater than 9.3.1, make sure it is fully supported for ThingWorx Applications.
Cannot import extension - ThingWorx version needs to be (minimum version)
Explanation
Current ThingWorx Platform version is lower than the minimal version required for the extension
Solution
Upgrade ThingWorx environment to match the minimal version required to install the extension
The following extensions require a platform restart to update in the ThingWorx environment. Restart your ThingWorx platform and press Enter once it is fully restarted.
Explanation
Some JAR-based extensions (such as Document Converter) require a ThingWorx Platform restart to be fully updated. If not updated properly, it will cause issues when installing dependencies such as CORE or CORE-UI.
Solution
Follow the instructions: - Restart ThingWorx Platform (using Tomcat or Docker) - Wait until Composer prompts you for login - Press Enter in the Window in which the message was shown to continue the installation script
Cannot update extensions package
Explanation
Unable to update existing Extension Package [MnfgCommon_Extension]
Solution
Following the instructions laid out in the following topics: Refer to RTPPM, CWC or AMU, pending which install is being completed.
Was this helpful?