# SOLO-5089

> CachedFileInaccessibleSoloError — System

URL: https://solo.hiero.org/docs/troubleshooting/errors/system/SOLO-5089/

| | |
|---|---|
| **Code** | `SOLO-5089` |
| **Category** | System |
| **Ownership** | User |
| **Retryable** | No |

## Description

Thrown when a file solo previously cached under SOLO_HOME can no longer be opened; the message names the path and the underlying failure is in `cause`. The cache is reused across deploys, so this means the file survived but its permissions no longer allow access — on Windows an empty DACL (which denies every principal, including the owner, and blocks deletion) and on POSIX a foreign owner or a cleared mode are the usual roots.

## Troubleshooting Steps

1. This is a local cache problem, not a cluster problem; the cluster does not need to be recreated
1. On Windows, repair the permissions: icacls "<path>" /reset
1. If that reports access denied, take ownership first: takeown /f "<path>"
1. On macOS and Linux, check the owner and mode: ls -l <path>
1. Then delete the file so solo re-creates it on the next run
1. To repair the whole cache on Windows: takeown /f "%USERPROFILE%\.solo" /r /d y && icacls "%USERPROFILE%\.solo" /reset /t /c /q
