Configurator Files corrupt after about 4-6 months of operation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
We've been developing a robust configurator that builds out one of our companies flagship products, and works as intended....until after roughly 6 months it just randomly stops working. This has happened three times now. Essentially, what's happening is that our configurator builds the assembly and uses one of (6x) different part files to build out the length of the assembly. It's these 6 files that seem to be the culprit. I believe that after N amount of rebuilds, the files start to lose functionality. In one case, it completely corrupted and wasn't able to be opened. The other two times, the files still worked, you could open them and generate new lengths, however trying to export data from the file to an excel file causes the program to crash. Simply rebuilding the file from scratch and replacing it in the assembly fixed it. This implies that there is something inherently wrong with the .ipt file itself. Something interesting to note, the glitched file is 3x times bigger than the fresh one.
Current strategy is to back these finicky files up to a safe location, and then swap them out every 6 months (like replacing a belt on a machine after so many months of operation).
However, I was hoping that one of you guys may be able to provide an explanation to this issue, and a possible work around. Any ideas?