Note: You are currently viewing documentation for Moodle 3.1. Up-to-date documentation for the latest stable version of Moodle is probably available here: error/moodle/storedfilecannotread.

error/moodle/storedfilecannotread: Difference between revisions

From MoodleDocs
m (Added link to spanish translation of page)
(forum discussion links)
 
Line 1: Line 1:
This error occurred when I was swapping a moodle 2 installation from one server to another and the actual file in the moodledata directory was not copied over correctly.
This error can occur when moving a Moodle site from one server to another and the actual file in the moodledata directory was not copied over correctly.


The entry in the Moodle 2 database referenced a legacy resource file but the actual file did not exist on the server.
The entry in the database referenced a legacy resource file but the actual file did not exist on the server.


The screen reported Permissions error which is kind of correct but "file not found" would be more appropriate.
The screen reported Permissions error which is kind of correct but "file not found" would be more appropriate.
Line 7: Line 7:
==See also==
==See also==


* Using Moodle [https://moodle.org/mod/forum/discuss.php?d=236403 file problem after upgrade] forum discussion about how the error could have occurred
Forum discussions:


* [https://moodle.org/mod/forum/discuss.php?d=236403 file problem after upgrade] forum discussion about how the error could have occurred
* [https://moodle.org/mod/forum/discuss.php?d=218075 Cannot read files after moving to new server]
* [https://moodle.org/mod/forum/discuss.php?d=254152 accidentally deleted a repository file]


[[es:error/moodle/storedfilecannotread]]
[[es:error/moodle/storedfilecannotread]]

Latest revision as of 05:47, 22 September 2016

This error can occur when moving a Moodle site from one server to another and the actual file in the moodledata directory was not copied over correctly.

The entry in the database referenced a legacy resource file but the actual file did not exist on the server.

The screen reported Permissions error which is kind of correct but "file not found" would be more appropriate.

See also

Forum discussions: