Windchill Cache Recovery Tool - Version 2.05 (WC_FileRecovery) - 64 bit version

Thanks Ron,

You can't even imagine how many times this tool got me and my users back-in-business.

Thank You

Hello,

I tired to recover using this tool but it didn't helped me.

I am looking for the .drw file that are missing from my local workspace and the tool showed me the .asm,prt files.

Any another option to take out the .drw files.

please suggest...!

Regards

Ashok

Does it work with 10.2?

Thanks

Pardeep

yes it will work.

please go throw the users feedback and the process of retrving the data from the corrupted workspace.

Windchill Cache Recovery Tool

Also, It only works with Pro/E files and not with third party CAD tools like Inventor, right?

Thanks

Pardeep

My apologies for the delay in responding.  In answer to your questions and others:

1. Ashok kumar: The tool examines all "lid" files you select and attempts to determine the Creo file type, including drawings.  After examining each file, the file type (PART, ASSEMBLY, DRAWING, etc.) is listed in the display.  If the tool cannot determine the file type, that field is left blank.  The user guide (included in the installation -- see your Start menu for a shortcut to the guide) has several screen captures that show examples of a recovery session.  If no drawings were recovered, I can only assume none of the lid files were of drawings.  Make sure you are collecting the lid files from the correct cache location.
2. Pardeep Singh: Yes, it will work with Windchill 10.2 cache files.  And currently it only recovers PTC Pro/E and Creo files -- no third party files at this time.

Ron

Ron,

Just wanted to say thanks (again) for the continued support with cache recovery tool.

I'm currently using it on Windchill 10.2 M030-CPS18 with Creo 3.0 M110 and it works great.

I can't tell you how many times I have used this tool to save someone's work (butt) when things crash on them.

Mike

What is the trick for getting this to install on Windows 7? It has a dependency for .net 2.0 which is not installable, as the dependency is supposed to be fulfilled by .net 3.5.

If I just install the .msi directly will it skip the detection, and just rely on the already installed 3.5.1?

Let me check my installer setup.  I thought I changed the .NET dependency with the last release.  Odd that it wouldn't have detected your 3.5 and accepted that.  Of course, the next question becomes, what version of .NET should I target?  The current is 4.6.2.

Glad you were able to get around the issue.

I actually have not gotten it installed. I was asking if I install the msi directly, will it bypass the check?