Knowledge baseOperate
Troubleshooting
The problems people meet most — signing in, missing data, silent alarms, reports, files that will not import — what usually causes them, and what to send when you need help.
Start with the symptom. Most problems have a short list of causes, and the platform usually says which one in the screen involved.
Signing in and reaching the platform
| Symptom | Likely cause | What to do |
|---|---|---|
| Cannot sign in | Wrong password, or the account is inactive | Ask an administrator to check the account or reset the password |
| Asked for a code after the password | Two-factor authentication is on for the account | Enter the 6-digit code from the authenticator app, or one of the recovery codes |
| Asked to change the password first | The account still has a default password | Change it; passwords such as admin, password or 123456 are refused |
| The address does not open from other computers | Firewall, or the server changed IP | Check the server’s IP and that the Windows firewall rule SyncTide Proxy (HTTP) is there; reserve the IP in the router |
| Works on PCs but not on phones | The phone uses its own DNS, or cached the old answer | Reconnect the phone to the Wi-Fi; switch off Private DNS on Android |
| SyncTide is on port 8080, not 80 | Another program held port 80 at install time | Use http://<server>:8080, or free port 80 and reinstall |
| The top bar shows OFFLINE · since … | The server stopped answering (network or service down) | The values on screen are the last ones received; the page reconnects by itself. If it does not, check the services |
Data
| Symptom | Likely cause | What to do |
|---|---|---|
| A device is grey | No data within its communication timeout | Check its connection, then the timeout in Equipment → Monitoring & Alarms |
| Nothing on the Dashboard or in the Explorer | Filters: no device, tag or period with data | Check the group, devices, tags and the time range |
| Test connection works but no values arrive | No active tags on the device, or polling not running | Check Tag Mapping has active tags with addresses; check the protocol’s service is running |
| A column of a file shows a value but has no history | The tag is not mapped, or the mapping is switched off | Map it; history starts from that moment |
| Values land on the wrong days | A date read day first that was month first | Check the first import of a new file layout; see Connecting data sources |
| The whole history moved by an hour or more | A time zone was changed or is wrong | See the time-zone cases in Connecting data sources; changing it never rewrites data |
| A file was not imported | It could not be read | It is set aside with the reason and listed in the platform; fix the file or the settings, then retry it |
Modbus: could not connect now and then |
The PLC closes idle sessions and refuses new ones for a while | Turn on the keep-alive option of the device’s connection |
OPC UA: BadIdentityTokenInvalid |
The server wants a user name and password | Set them on the device’s connection |
| IEC 104: connected but no values | The common address does not match the RTU’s | Set the RTU’s common address on the device |
| A line is broken on the chart | Real gaps, or the expected data period is too short | Check the device’s expected data period |
Alarms and Messaging
| Symptom | Likely cause | What to do |
|---|---|---|
| An alarm fired but nobody was told | No messaging rule for that device or category, or the gateway is off | Check Messaging Center → Alarm Rules and the gateway; send a test |
| A message failed | The gateway refused it | Messaging Center → History shows the gateway’s own error |
Telegram: bot can't initiate conversation |
The recipient never started the bot | They open the bot and tap Start |
Telegram: chat not found |
Wrong chat ID (group IDs are negative) | Check the ID with the recipient |
| A reply did not acknowledge | It came from another chat, or the code is wrong | Reply in the chat the alert came to; for the SMS gateway, include the ACK-… code |
| A rule did not fire for an old value | Rules apply to values received after the rule was created or changed | Expected; the next crossing fires it |
| The delay field is missing | The equipment is read from files | Delays are offered only for live sources; use a threshold with hysteresis |
| A forecast card says Waiting for the next delivery | The device sends its data in batches | Nothing to do; it turns into a warning only when a delivery is really late |
Reports
| Symptom | Likely cause | What to do |
|---|---|---|
| Excel refused: This template has no Excel file | The template is PDF only | Choose PDF, or upload an Excel layout for the template |
| The PDF header looks wrong New in 1.14.8 — coming soon | The header the template uses | Check Reports → Header and which header the template uses; the preview shows the result |
| A scheduled report was not emailed | No SMTP gateway, or a wrong recipient address | Add or test the SMTP gateway in the Messaging Center; check the recipients |
Backups and updates
| Symptom | Likely cause | What to do |
|---|---|---|
| No new backup in the morning | The scheduled task is missing or failed | Check the Backups card and the health card; look for the SyncTide Backup task. A run that does not end with Created archive: made no backup |
| The backup refuses to start | Not enough free disk for another archive | Free space or move old archives off the server |
| The licence is refused after an update | The installed version is newer than the licence’s update period | No data is lost: upload a renewed licence, or reinstall a version from within the period |
| No update notice appears | No internet access, or no newer release within your update period | The health card says when it could not check; you can always run the newer installer by hand |
Getting help
Before you contact support, gather:
- your user name and the page where it happens;
- the exact error message, if any, and the steps to reproduce it;
- a support bundle: from an elevated PowerShell in the installation folder,
.\backup_platform.ps1 -SupportBundleOnlypacks the logs and settings — no measurement data.
The logs are in the logs\ folder of the installation (one file per service: backend.log, ingestion.log, messaging.log, the protocol readers, predictor.log…). SyncTide runs as Windows services named SyncTide… (services.msc); a crashed service is restarted automatically. The nightly backup is a scheduled task, not a service.
Then contact us.