Troubleshooting
This page points you to the right section when something does not work. Find the symptom, read the linked section, and check the logs if the section does not solve it.
Start-up and sign-in
| Symptom | Where to look |
|---|---|
| A module does not start, a port is already in use, the first-launch wizard misbehaves, or the install folder path causes errors | Troubleshooting in Installation, services and updates |
| Another application uses a default port | Changing the ports |
| You cannot sign in to the web UI | The UI credentials are the ones that you entered in the first-launch wizard. See the rows about the UI login in Troubleshooting. The Hub must run, and hub must be true in modules.conf |
| A new password has no effect after the first start | Changing the default user ID and password |
| You are not sure that a module runs | Health check |
IBM i connections
| Symptom | Where to look |
|---|---|
| The Hub cannot reach the IBM i | The Hub must reach the IBM i ports and the host servers must run, see Prerequisites: IBM i. For TLS, see IBM i TLS connection configuration |
A connection has the status WARNING or FAILED, or a license error appears |
License and connection status. To get or renew a license, contact the Infoview sales team |
Data Flows
| Symptom | Where to look |
|---|---|
| A Data Flow does not start | Requirements for starting |
A Data Flow is FAILED or INVALID |
Recovering a FAILED or INVALID Data Flow and Failure behavior |
| A create or update request returns an error | Validation errors on create and update |
| The target database rejects the data | Errors and retries |
| The Data Flow reads very slowly | Check Batch size in Data Flows. A value of 0 reads one message per cycle |
| You want to see what a running Data Flow does | Monitoring a Data Flow |
| The Hub rejects a password or key | Encrypting secrets. Values encrypted with another key do not work |
APIs
| Symptom | Where to look |
|---|---|
A call returns 400, 401, 403 or 404 |
Errors in Calling your APIs |
A call returns 404 for an API that exists |
The API may be inactive, see Managing Hub APIs |
| A request is rejected with a list of problems | Request validation |
| A value does not arrive in the program or the SQL statement | API parameters configuration |
| An RPA Call fails | Troubleshooting and Errors in the RPA Hub user guide |
MCP server
| Symptom | Where to look |
|---|---|
The AI agent gets 401 |
MCP authentication |
| The AI agent sees no tools, or only mock tools | Tool initialization and reload configuration. Select Reload Tools on the MCP Tools page |
Logs
Each module writes log files to the log folder. See Log files and Log levels. Raise the log level only while you look for a problem.
Still stuck?
Contact Infoview Systems and attach the log files of the affected module, the version of the Hub and a description of the steps that lead to the problem.