Troubleshooting the 'file can't be uploaded' error when checking in documents
Who is this article for?Users checking in edited documents.
Document module access is required.
When checking a document back in after editing, you may encounter an error message stating 'Oops… The file {0} can't be uploaded' with no further detail about the cause.
Understanding the error message
The {0} in this message is a placeholder that should normally be replaced with the file name, but it displays literally when the system cannot populate it — which is why the message gives no specific information about the cause. This article explains how to work through the most common causes of this error.
Confirming whether the issue is specific to one document
Before investigating further, check whether the error occurs only with the document you are trying to check in, or with every document you attempt to upload.
To test with a different document:
- Check out a different, unrelated document.
- Make a small change and attempt to check it back in.
Note: If the error appears on multiple unrelated documents, this points to a setup or environment issue — such as the Automatic File Transfer (AFT) tool, your browser, or your network — rather than a problem with one specific file. If the error only occurs with one particular document, the file itself is the most likely cause, even if a second affected document seems to make the issue look more widespread at first.
Addressing the most common cause: file corruption
In most cases, this error is caused by some form of corruption within the document file itself, rather than a configuration issue. This can happen after extensive editing — particularly when a large number of images, tables, or other embedded content has been added or changed.
The most reliable fix is to recreate the document from scratch in a new file, rather than continuing to edit the corrupted one.
To recreate the document:
- Create a new Word document.
- Recreate the content from your edited version, including any images and tables.
- Save the new file.
- Check the document back in using this new file.
Example: A document has been heavily edited over time, with a large number of images and tables added throughout. The file checks in correctly with the platform but errors during processing. Recreating the document in a brand new file, then re-adding the content, allows it to be checked in without error — confirming the original file had become corrupted through the editing process.
Performing other checks if the issue is not file-specific
If the error occurs across multiple documents rather than one, work through the following checks before recreating any files.
Check the Automatic File Transfer (AFT) tool
If you are using AFT to check documents in and out, try reinstalling the tool. This is available from your User Preferences page under the Client Tool Installers section.
Tip: If a document opens directly in Word showing symbols or code instead of readable text, the application used to open AFT files may be incorrectly associated with Word or your browser instead of the AFT tool itself. Changing the default application associated with the file type in your operating system settings can resolve this.
Check antivirus and security software
If you continue to experience issues after reinstalling AFT, ask your IT team to check whether your antivirus software is blocking or interfering with the AFT tool. The AFT tool may need to be added to your antivirus's list of trusted or safe applications.
Check browser and cache settings
Try clearing your browser's cache and cookies, or attempt the check-in using a different browser, to rule out a browser-specific issue.
Check server-side processes (administrators)
If multiple users across your organisation are affected, your system administrator can try the following on the server:
- Run Document Automation and check whether the issue persists
- Restart the application pool and related services
- Review the system error logs, typically located at
C:\Program Files\Ideagen Quality Management Core\Logs, for High, Medium, and Low severity entries that may indicate the underlying cause
Summary
| Symptom | Likely cause | Fix |
|---|---|---|
| Error occurs with one specific document only | File corruption, typically following extensive editing | Recreate the document in a new file |
| Error occurs across multiple unrelated documents | AFT tool, browser, antivirus, or server-side issue | Reinstall AFT, check antivirus settings, clear browser cache, or have an administrator check server logs and restart services |