Unzip error when opening zprj file
Earlier this week I tried to open a project file from a couple of months ago. After CLO has launched, I get an error message that it failed to read the project file because of an unzip error (see image). Opening or adding the project through the 'file' menu gives the same message. There are a couple of other users who reported the same problem but never got a proper reply.
Opening files that were created around the same time open just fine. The project file in question is 5MB, so I would say the project still contains data (or at least some of it).
Hopefully someone knows if and how to resolve this?!
-
Make a backup copy and rename that then try opening that copy with 7-zip.
You can open any .Zprj file with 7z (7-zip) and it should open up the compressed project file, then you can look at the garment .zpac itself (in isolation) which is packed in with the other project file data like avatar etc, that should at least allow you to see if that garment by itself can be extracted and salvaged as it may be anyone of the other packed elements causing the issue - if the .zpac garment inside the compressed project file has zero data that would be a problem. If however you cannot read the .Zprj data file itself with 7-zip the entire compressed file may be corrupt and so you might need to ask CLO3D if they can help you with extracting it to at least try and retrieve the garment file inside it.
-1 -
ottoline thanks for your help.
Sadly it doesn't work; when trying to open the file with 7-Zip I get a message that it 'Can not open file … as archive'. I am able to open other .zprj files with 7-Zip without any issues though.
I'll try to find another program that might be able to fix it, but I guess I've lost the file.
Thank anyway though!
-1 -
I am having the same issue and from the looks of it, the clo company has zero intention's of fixing this issue. I noticed a lot of people have been having this issue for years and still... not 1 direct solution to this. I've only been using clo for a month and so far l lost 3 files i worked hard to create. How can i fix or prevent this issue?
0 -
Back up your work in progress using an incremental backup like 95% of those companies using CAD. Then if a single project file gets corrupted you can dial back to the last 'good' save or work session for that datafile. You don't want to be in the 5% of companies that do not have a workflow backup strategy. Maybe this is a timely event to safe guard your work with some strategic system updates to how you backup data.
0 -
Ottoline is correct that a good back up system is always a good idea. 7-Zip is another good method. But many people to not realize that once unzipped they need to find the corrupt file inside and delete before re-zipping the file back together.
Usually once unzipped with 7-zip you can tell which file is corrupted by the thumbnail images. Delete that portion and re-zip. It is often a Texture or Normal Map
0 -
Yes have a great backup strategy.
Today a backup strategy is simple and low cost, not like when I first started out in design, so there are no excuse(s) in todays technology world. You can save work off a desktop in realtime via a internet connection to the cloud after every work-session. All that takes is to download a app or if you use Cloud based garment backup - synchronization.
There is little to no barrier and the transaction cost is almost friction free. The question is not about how software fails (or that your expectations is for perfect functional software all the time ....in this age of incremental rolling software development & updates) - that is a given reality there will be engineering failure points , as this is the dynamic world of rolling updates we now cross over with. Software will fail at some point, and so will project faults as it does with Autodesk, Solidworks, Maya, Modo, Windows OS updates ~et all. That is a 100% certainty in terms of project and business risk, that 'it' will happen at some point in time. What matters is how you decide to cope when it happens and what risk > mitigation< you put in place for your own safety and clients peace of mind. To drag any project onto a cloud based folder is a 'low friction' transaction, as is the automated version control offered by many data file cloud systems. The cost is measured in cents, where-as the risk not to use common sense is measured 100X, 1000X the cost if you don't. The buck stops with you and caring about your own peace of mind - when faced with the inevitable ... fact > it is going to happen, and likely when it is most inconvenient. The trick is reducing the impact so it does not matter to your workflow or costs. And that is well within reach for everyone connected ... on this planet.
In any project session, you can use both history save states to fork project versions, rather than overwrite a (WIP) work-in-progess datafile into version control on the desktop. By leveraging version updates back to the shared server/cloud or even USB hard-disk you create control at ISO level for documentation that is robust and limits risk per work session interval. Something to think about may be how you name files and work to versions that are under auditable control ?
0
Comments