---
title: "TYPO3 Exception 1317178604"
manual: "TYPO3 Exceptions"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3exceptions:typo3-exception-1317178604"
source: "Exceptions/1317178604.rst"
modified: "2026-09-16T07:39:08+00:00"
---

# TYPO3 Exception 1317178604

> [!NOTE]
> Below, the TYPO3 community may have provided additional information or
> solutions for this exception. However, these may or may not apply to your
> particular case. If you can provide more information, you should come back
> here and add your experience and solution steps to this issue once you have
> resolved it.
>
> General TYPO3 troubleshooting tips can be found in the *Troubleshooting*
> section in the menu. You can also ask questions and receive support in the
> [TYPO3 Questions category on talk.typo3.org](https://talk.typo3.org/c/typo3-questions/).
>
> To add your experience, click "Edit on GitHub" above and follow the
> ["Edit on GitHub" workflow](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/EditOnGithub.html#docs-contribute-github-method).
> Also check out
> [our tip on Coding Style and reST](https://docs.typo3.org/permalink/t3exceptions:tip-about-rest-coding-style).

## No file found for given UID.

### TYPO3 CMS 6.1.2: Error while uploading previously deleted file

Having deleted a specific file before at the `fileadmin` it's not
possible to upload the same file again without error "No file found
for given UID.".
You can't open the `fileadmin` folder containing the file once again
uploaded afterwards.
At the `sys_file` table the misbehaving file's entry shows "deleted = 1"
before and after upload.
Workaround: Deleting the `sys_file` entry of that file via phpMyadmin.
This is forcing TYPO3 `fileadmin` to create a new sys_file entry with a
different uid. Now the folder and it´s content are available again.

Related to [Bug #50508](https://forge.typo3.org/issues/50508)

### TYPO3 CMS 6.2.x - happened when a tt_news entry had an non-existing image in the bodytext

For some reason the preview did still exist and was shown in BE when
editing the news record. But in FE this lead to the exception, because
the sys_file record was not there anymore.

### EXT:solr + EXT:solrfal

The exception happened when initializing `fileadmin/` queue. File record
was missing in sys_file but existed in `sys_file_reference` and
`sys_file_processedfile`. The following SQL helped:

```sql
delete from sys_file_reference where uid_local not in (select uid from
sys_file); truncate sys_file_processedfile;
```

The exception can also happen when there are non-existing files for
indexing in `tx_solr_indexqueue_file` and the the records are not deleted with
"Clear Index Queue" for unknown reasons. This SQL helped:

```sql
truncate tx_solr_indexqueue_file;
```