File Reconciliation tool is developed to solve a very common problem of “missing files in store/location”. It generates excel file reports, which contains the list of files from object meta-data information (information as in a database) and gives a status of file availability on relevant locations/store folder path. The missing files scenario happens when files from locations/store folder path are deleted for various reasons, but object(s) still have the information (metadata) with the file path.
When the user tries to download such deleted files from 3DEXPERIENCE, he gets either of below error messages:
- FCS Server failure Response Code:400
- java.lang.Exception: 550 (followed by the STORE path/filename): The system cannot find the path specified
Typically, administrator creates copy of the Production system in 2 ways to make Test/QA/Dev system:
- Create VM copy using VM Workstation
- Export Production database user. Import this database backup on Test/QA/Dev system
And user thinks they are completely independent and disconnected from the Production system.
But No. they are NOT. Your copy VM/Database still has exactly same STORE/Location definition as your production system. It still points to same host and file path of production.
So, when you delete the object from your copy VM/Database, you end up deleting object metadata from your copy VM/database, but that object still has file reference to your production system. So, along with object, file will also be deleted for sure.
Your production object still has the file as metadata in the database, but it does not know that its file from store/location is lost…!!!