Installation and access troubleshooting
| Symptom | Customer check | Next action |
|---|---|---|
| Installation precheck fails | Read the named prerequisite | Resolve with the installation owner |
| Installation file verification fails | Confirm package identity and reported file | Obtain the complete matching package |
| Platform already exists | Determine whether it contains customer records | Preserve records and agree recovery with support |
| Broker unavailable | Confirm the supplied URL and installation result | Contact the platform owner |
| Login rejected | Confirm Broker account, active state and password | Ask the administrator to review User Management |
| Required action absent | Check role, assigned organization, project state and licence | Review with the administrator |
| Licence rejected | Check complete key and intended installation | Follow activation troubleshooting |
For a new installation, change the initial Broker administrator password before handover and create named accounts. Repository installation passwords are separate from Broker login. Use the customer Broker URL and its accounts for platform administration.
Provide the version, time, supplied URL without secrets, visible error and sanitized screenshot. See licence troubleshooting and case preparation.