Hi All,
I’m currently working on an investigation regarding a corrupted file. The customer in question is from the Oil and Gas sector, and the Replication module is enabled in their system. This particular document has been uploaded across several off-shore environments as well.
In those off-shore environments, the document can be downloaded and viewed without any issues. However, when the same document is downloaded from the PROD environment and opened using Microsoft Word, the following error is encountered:-
I attempted to use Microsoft Word’s "Open and Repair" recovery option, but the document still throws an irrecoverable error.
After retrieving and analyzing the Base64-encoded version of the file, the investigation has been narrowed down to three possible causes:
-
The Base64 encoding might be incorrect.
-
The Base64 string could be incomplete or modified, leading to invalid content.
-
The file type may be incorrect — the content may not actually be a valid
.docxfile.
However, upon analyzing both the Base64-encoded content and the resulting corrupted .docx file, it was confirmed that the contents are identical. Since both versions are corrupted in the same way, the issue most likely originates from the original source file, before it was Base64-encoded.
What remains unclear is why the document becomes corrupted only when downloaded from the PROD environment, whereas the same document works perfectly fine in the off-shore environments.
Questions & Guidance Requested:
-
Are there any potential reasons specific to the PROD environment that could cause this corruption (e.g., file storage format, encoding transformations, replication timing issues)?
-
Is there a way to validate or compare the binary integrity of the document across environments?
-
Are there tools or logging options available in IFS Cloud that could help determine whether the corruption is happening during upload, replication, or download?
Any insights or suggestions to further narrow down and resolve this issue would be greatly appreciated.