Start with the console
Almost every problem names itself in the server console at start. Find the first line mentioningelement_sdk or the product (the lines below it are usually consequences) and look it up in
Console messages.
If the console says nothing about the product at all, the server never found the resource. Go
straight to A product does not start.
By symptom
The product fails at start, or never appears
A product does not start.
A setting you edited changes nothing
Configuration changes have no effect.
Wrong language, untranslated strings, or a key name on screen
Text is wrong or missing.
A console message you do not recognise
Console messages.
Something works differently after an update
Update a product or the SDK.
A problem specific to one product
That product’s own troubleshooting pages.
Before you report a problem
Check these three first. They resolve most reports without a ticket.- Restart, and read the start-up output. Configuration, language files and the choice of which of your resources a product uses are all decided at start.
- Confirm the versions match. The product states which SDK versions it accepts, and refuses to start outside them. See SDK version requirements.
- Undo your last edit. Restore the file the release shipped and confirm the problem goes away. That separates a product fault from a configuration fault, which is the first thing support will ask.