|
Scenario
|
Resolution
|
|---|---|
|
To validate ThingWorx Flow connectivity
|
Run the ValidateFlowSetup service.
|
|
If the ThingWorx Flow server URL is not accessible or returns an error code 502 or 504
|
Complete the steps in Reconfigure ThingWorx Flow Setup Parameters.
|
|
If the ThingWorx Foundation host is not accessible from the ThingWorx Flow virtual machine
|
1. Navigate to the RabbitMQ log files under the <ThingWorx_Flow_Install_Location>\modules\RabbitMQ\log folder.
2. Open the log file and check if the following line is available in the log file:
user 'flowuser' authenticated and granted access to vhost 'orchestration'
3. If the line is not available, do the following:
◦ Check the firewall connection on the ThingWorx Foundation virtual machine.
◦ Ensure that the RabbitMQ port is accessible on both hosts.
Check if ThingWorx Foundation and ThingWorx Flow hosts can reach each other using the DNS name or the host name.
|
|
If flow execution in the engine stops abruptly
|
Review your software before you make any changes:
• Set the ephemeral ports for services on your operating system between 5000 and 65535.
For information about ephemeral ports and its range, see The Ephemeral Port Range.
• Reduce TIME_WAIT on sockets to 30 seconds.
For more information, see Windows: Time Wait setting or Linux: Time Wait setting.
|
|
If you have updated the password of the ThingWorx Flow database administrator
|
You must update the same password in ThingWorx Flow. To do so, complete the steps in Updating the ThingWorx Flow Database Administrator Password.
|
|
If you want to update the RabbitMQ password
|
Complete the steps in Updating the RabbitMQ encrypted password.
|
|
If the password of the user that ran the ThingWorx Flow installer changed
|
You must restart ThingWorx Flow. To do so, complete the following steps:
Windows
1. Stop the ThingWorx-Flow service.
2. Right-click the ThingWorxFlow installation folder, and provide all permissions to the NETWORK SERVICE group.
3. In Windows Services, right-click the ThingWorx-Flow service, and select Properties. Select the Log On tab, and for the Network Service account, update the password.
4. Start the ThingWorx-Flow service.
5. If the ThingWorx-Foundation service uses the same user, then repeat the same procedure.
Linux
1. Restart the ThingWorx-Flow service.
2. If the ThingWorx-Foundation service uses the same user, then restart the ThingWorx-Foundation service.
|
|
If you are unable to run ThingWorx Flow in case ThingWorx Analytics was installed before ThingWorx Flow
|
This may be caused as RabbitMQ services for both, ThingWorx Analytics and ThingWorx Flow, are listening to the same default port. If this is the case, you must reconfigure RabbitMQ port for ThingWorx Flow to listen to other port than default port.
|
|
After installation, if ThingWorx Flow is not loading and displays error code 502
|
• During the installation if HTTP_PROXY or HTTPS_PROXY is used to connect to the internet, then this setting is picked up by the dump.pm2 and is added in the environment variable.
In this case, delete the HTTP_PROXY and HTTPS_PROXY settings in the dump.pm2 file and from environment variable.
For more information, see Following successful ThingWorx Flow installation, attempts to access the login page fail with "504 Gateway timeout" or "502 Bad Gateway nginx" error and New installation of ThingWorx Flow hangs on the ThingWorx logo, F12/Developer Tools shows currentUser call returns "502: Bad Gateway" or "504: Gateway Timeout".
• Verify that ports used for communication between foundation and flow are not blocked at the server or firewall level. The ports in use are found in platform-settings.json, vhost-flow.conf, nginx.conf and deployment config files.
If the following error message is logged in the nginx logs, this means that the port similar to 443 is blocked by other application. This happens when you try to install many application on single machine. For e.g., Foundation, Flow, Windchill etc.
2021/11/30 15:42:15 [emerg] 47544#47116: bind() to 0.0.0.0:443 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
Check if the URLs and ports mentioned in vhost-flow.conf and deployment.config files are correct. (Backup the files before changing)
• If you are using commercial certificates or if you have made any changes in the certificates, follow the steps in the article Configuring SSL for ThingWorx Flow .
For more information, see ThingWorx Composer is not responding when accessed from Flow
|
|
If login to ThingWorx Flow is successful after configuring the CA signed certificate, but ThingWorx is unable to connect to ThingWorx Flow
|
The java keystore (cacerts) may be missing the CA's root and intermediate certificates. For more information, see “Notes” section in Configuring SSL for ThingWorx Flow
|
|
If ThingWorx Flow fails to create rows to MSSQL database with error Invalid column name "id".
|
ThingWorx Flow assumes MSSQL tables has id column as a primary key by default. If id column is not a primary key:
• Use id either as primary key.
OR
• Do not use id as a column name.
|
|
Error Code
|
Error Message
|
|---|---|
|
[FLOW-CONFIG-01]
|
ThingWorx Flow is not enabled. Add the OrchestrationSettings section to the platform-settings.json file to enable ThingWorx Flow.
|
|
[FLOW-RABBIT-01]
|
Failed to connect to RabbitMQ. Check whether the RabbitMQ service is running and is accessible.
|
|
[FLOW-API-01]
|
Failed to connect to ThingWorx Flow. Check ThingWorx logs for more detail.
|
|
[FLOW-API-02]
|
Failed to connect to ThingWorx Flow. Ensure that you are accessing an Nginx-hosted ThingWorx instance. ThingWorx Flow is not supported on a Tomcat-hosted ThingWorx. Ensure that all ThingWorx Flow services are running and are healthy. In case of self-signed certificate, make sure that correct CN is provided.
|
|
[FLOW-KEY-01]
|
OAuth admin key not found in the ThingWorx KeyStore.
|
|
[FLOW-KEY-02]
|
Exchange admin key not found in the ThingWorx KeyStore.
|
|
[FLOW-KEY-03]
|
Failed to get ThingWorx Flow keys from the ThingWorx KeyStore.
|
|
[FLOW-KEY-04]
|
Failed to get ThingWorx Flow keys from the ThingWorx KeyStore.
|
|
[FLOW-EXCHANGE-01]
|
Failed to connect to ThingWorx Flow exchange service. Check ThingWorx logs for more details.
|
|
[FLOW-EXCHANGE-02]
|
Failed to connect to ThingWorx Flow exchange service. Check whether ThingWorx Flow exchange service is up and running.
|
|
[FLOW-OAUTH-01]
|
Failed to connect to ThingWorx Flow OAuth service. Check ThingWorx logs for more details.
|
|
[FLOW-OAUTH-02]
|
Failed to connect to ThingWorx Flow OAuth service. Check whether ThingWorx Flow OAuth service is up and running.
|