# SOLO-4083

> ComponentVersionIncompatibleSoloError — Validation

URL: https://solo.hiero.org/docs/troubleshooting/errors/validation/SOLO-4083/

| | |
|---|---|
| **Code** | `SOLO-4083` |
| **Category** | Validation |
| **Ownership** | User |
| **Retryable** | No |

## Description

Thrown when the selected component versions would run together in a combination the network does not support (for example a block node too old to verify the blocks a consensus node produces); the message lists every broken constraint and names the component to bump. Running such a combination typically fails block verification or ingestion, so choose versions that satisfy the listed minimums, or pass --force to deploy them anyway.

## Troubleshooting Steps

1. <remedies.join('
1. ')>
1. Upgrade the lagging component first when the rule allows it
1. When the consensus node and another component must move together, stage the consensus node upgrade with --skip-node-start, upgrade the other component, then run solo consensus node start
1. Or bypass this check with --force if you accept the resulting failures
