Attempts to open practically any Fritzing result in a “Can’t open component path/file, zip.open(): %d” Error (translating from German.
This happens whenever the files are stored, on the Desktop, in the Fritzing folder in Documents, i a new folder directly on C:\ . Happens with “official” files from github repositories and other files.
Fritzing has been reinstalled, de-installed and re-installed, Problem persists
…
What I expected should have happened instead:
… Open a file without errors. Sorry, don’t want to sound snarky, but this is some kind of basic functionality that I was kind of expecting. If I am doing something wrong, then a better Error Message would be useful.
My version of Fritzing and my operating system:
Fritzing 0.9.10 / Windows 10 64 Bit Version 10.0.19045 Build 19045
What Fritzing version are you using (the current version is 0.9.10)? Is this a new install? If so doing this (noting that it will delete anything in your mine parts bin!) may help. Normally .fzpz files open without problem on Win10.
There are two user directories (with your parts and the parts database) which don’t get touched during an install (to not affect your sketches during upgrades). On Windows they are in
c:\users\username\AppData\Fritzing\roaming\Fritzing (which is a hidden directory so you need to enable hidden directories in explorer) and
c:\Users\username\My Documents\Fritzing (where username is your windows id)
If you don’t have any parts or sketches you want to keep you can just delete those two directories and Fritzing will recreate them, or you can move them aside by renaming them if you want to keep something in them.
Thanks, this solved it. I deleted the AppData Folders and reinstalled Fritzing.
I still don’t understand how/why the files got corrupted and why this blocked everything else.
Oh, and uninstall show give you the option to really remove everything
Again, your kind and prompt help is really appreaciated.
That is possible but somewhat dangerous in that it will remove all the user’s parts. This used to be a common problem in the days of 0.9.3b when you interrupted the parts database update from github. Since 0.9.6 or later the parts update has been disabled and this hasn’t been a problem for the last couple of years. If you are still running 0.9.3b upgrading to the latest version (currently 0.9.10 I believe) is highly recommended because a lot of bug fixes have been done.
I’m actually having the exact same issue on my Mac! I’ve been working on a huge schematic for days and I’m finally ready to do the layout and I cannot open my project.
This has never happened to be before. The only thing I did differently was edited a custom part to have a different pin out. It seems like most people that have crashing issues result from custom parts.
I can work around not having this custom part, but I would love to be able to restore this file without having to spend another 2-3 hours redrawing the schematic from scratch.
First thing to do is check the size of the sketch file (the .fzz file), if it is close to 0 you are likely out of luck. It is possible that you ran out of disk space (or had another failure such as no write permissions) and the file got truncated. There isn’t any recovery from that. Keeping a backup file outside of Fritzing for a while may be a good bet til you see if the problem reoccurs. If you can reproduce the failure with the part you were using that would be interesting because the developers could then trace the error and possibly fix it, but that requires a reproducible error which may not be that easy to arrange.
Thanks for the update. I was trying what someone else suggested by deleting App Data folders and reinstalling the application, but doesn’t seem to work. I guess I’ll have to start over.
If you upload the .fzpz file of the part you are using I’ll have a look at it and see if it has errors (upload is 7th icon from the left in the reply menu) although a bad part is unlikely to be the problem. If it is sufficiently broken I guess it could happen as the custom parts are included in the .fzz file and it could be what is causing the issue. Corrupted .fzz files have been relatively rare although there were a number 5 or 6 years ago on Linux that were never resolved.
edit:
upload your corrupted .fzz sketch file as well and I’ll have a look at that too and see if I can figure out what went wrong.
