When I try to open my last Flowcode program, I get the error:
Failed to open document.
Can not load <schema> without a block header
OK
Can this be repaired?
Error opening Flowcode file
Moderator: Benj
-
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
Re: Error opening Flowcode file
First make sure you have the latest V6 then try and open the file again.
You can try looking for.001 file from the project directory and rename to .fcfx
That file is a backup copy.
If you want to keep the file that could be corrupted the rename it before completing the above step, so you don't have two files with the same name.
You can try looking for.001 file from the project directory and rename to .fcfx
That file is a backup copy.
If you want to keep the file that could be corrupted the rename it before completing the above step, so you don't have two files with the same name.
Martin
Re: Error opening Flowcode file
Thanks Martin,medelec35 wrote:First make sure you have the latest V6 then try and open the file again.
You can try looking for.001 file from the project directory and rename to .fcfx
That file is a backup copy.
If you want to keep the file that could be corrupted the rename it before completing the above step, so you don't have two files with the same name.
Unfortunately, that did not work.
Better safe then sorry
-
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
-
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
Re: Error opening Flowcode file
Hi,
Not a problem.
Just looked at the Flowchart you sent via pm.
There is no chance at all of any recovery.
It looks like the file has been totally wiped.
Every single byte from start to finish is a null character: That would be a typical file that has had an anti forensic data wiper used on it
Has one been used?
Not a problem.
Just looked at the Flowchart you sent via pm.
There is no chance at all of any recovery.
It looks like the file has been totally wiped.
Every single byte from start to finish is a null character: That would be a typical file that has had an anti forensic data wiper used on it
Has one been used?
Martin
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: Error opening Flowcode file
I've seen some network attached storage do this type of thing before too.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Re: Error opening Flowcode file
Hi,
I had a similar problem. After installing a Samsung 860 EVO SSD, I installed the supplied software "Samsung Magician". Everything worked fine, until exactly this described error message came when opening a FC file. When checking with an editor (Notepad ++) I saw that parts of the file contained useless strings. After some attempts without improving the bug, I uninstalled the Samsung software and have not had any problems since then.
For me, it was a software component, maybe this post helps a bit with troubleshooting.
Christina
I had a similar problem. After installing a Samsung 860 EVO SSD, I installed the supplied software "Samsung Magician". Everything worked fine, until exactly this described error message came when opening a FC file. When checking with an editor (Notepad ++) I saw that parts of the file contained useless strings. After some attempts without improving the bug, I uninstalled the Samsung software and have not had any problems since then.
For me, it was a software component, maybe this post helps a bit with troubleshooting.
Christina
Re: Error opening Flowcode file
Hi Martin,
Thanks for the effort.
@Benj
It is/was stored on a nas.
I saved the file before building the program. When the programming was finisched somehow the power of the NAS was cut of.
Due to the fact that the file was saved just before, I did not save the program local an stopped working at the project. I assume the file was not closed and that is what caused it.
Fortunate I had a backup of a week age, I did loose quite a bit of work but due to the fact that it was fresh in my memory I could program it back to where I was relatively fast.
Thanks for the effort.
@Benj
It is/was stored on a nas.
I saved the file before building the program. When the programming was finisched somehow the power of the NAS was cut of.
Due to the fact that the file was saved just before, I did not save the program local an stopped working at the project. I assume the file was not closed and that is what caused it.
Fortunate I had a backup of a week age, I did loose quite a bit of work but due to the fact that it was fresh in my memory I could program it back to where I was relatively fast.
Better safe then sorry