SCORM

STF should be your first action  and then ask for help to your local Moodle Partner, if you need to respect SLAs.

BTW, debugging that issue could be a really time consuming activity because you need to activate debugging at DEVELOPER level, including display messages, and look at the error message and find the reason for that error.

From the past posts of other users for the same error, you could have issues in the filedir folder where Moodle stores its contents via internal deduplication and the most recurrent ones are:

• permissions issues: for some reasons the user under which the web server runs your Moodle instance is not able to R/W files there;
• broken uploads: for some reasons - e.g. no more disk space - the file has been partially stored but the size and/or the content of the actual file is not equal to the expected one/s and any other upload will fail until you'll fix the broken file in the filedir folder.

In order to fully understand what written above, you need to understand the way Moodle stores its contents. The documentation can be found at https://docs.moodle.org/dev/File_API_internals, the first important thing to know can be found in https://docs.moodle.org/dev/File_API_internals#File_storage_on_disk.

HTH,
Matteo

If there's an SLA involved there are probably a number of major violations simply by allowing your clients to use a Moodle 2.0.1 site.

2.0.1 contains a large number of serious security issues that are well known and well documented that could allow a malicious user to compromise your site. You should spend less time trying to get it to work on 2.0.1 and more time on upgrading your site to a recent supported release.