SERIOUS ISSUE: Corrupted Wildfire 4.0 files after update to CREO 2.0

[RBobroski]

Hey guys. Major problem I'm having here. We updated to Creo 2.0 from Wildfire 4.0 about two weeks ago. I haven't switched over however due to me being in the middle of a big design project that had to get finished. Two weeks go by, no real issues. Yesterday, however, in the process of me updating a hole size on a piece of sheetmetal 2 subassemblies deep I had a major crash. I was in the edit window (not edit definition) and adjusted the diameter and hit regenerate and all of a sudden I'm looking at my desktop; no error message, no lock ups or lag, nothing. I reboot my computer and I get an error upon shutdown that says something along the lines of "cannot write memory 0x000000000 for lmgrd.exe". Then upon restarting Pro/E some files keep getting corrupted. Some of them just trying to open brings me back to my desktop; some I can open but trying to view or regenerate or close the file crashes it. It isn't just corrupting the latest save files either but going several iterations down, ie if I have a screw.prt.12 that is corrupt screw.prt.8-11 won't work, but screw.prt.7 will.

Has anyone ever experienced anything like this? Would it have something to do with the update? Originally WF 4.0 license was on a server, when we installed CREO we moved the license file to the local machine, and I know lmgrd.exe has something to do with the licensing system. WF 4.0 is also only on M.040 and I am currently updating it to the latest build hoping it will resolve the issue. I can fins the corrupted files and delete them and redo some work but this isn't solving the root of the problem and I keep getting crashes and further corrupted files. Any help would be immense, as I'm at defcon 5 right now.

 

[dgallup]

I would say the installation of Creo2 is not your problem. I suspect you have a hard disk going bad. There is no way that Pro/E is corrupting screw.prt.8-11. Once Pro/E writes a file it NEVER changes it. Do you have backups?

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

 

[RBobroski]

I do have backups of all my files on another network drive and most of my work is saved on a separate network drive so no data is pulled from my local machine save the license files now. I have no indications in my event log of a potential HDD issue although I may have missed it. The file that went corrupt was a family table file however..could the index file potentially get corrupt as well? It's hard for me to troubleshoot; I eliminated a couple of the fastener backups (moved to a diff directory) and eventually it opened up one that worked, but I also removed the index file at some point so I'm not sure if that did it.

Is there any way to check whether a file has issues without having to open and just experience a crash?

 

[geesamand]

I would copy off those data files ASAP and attempt to read them from another computer. I agree with dgallup, first rule out hardware failures.

It wouldn't hurt to run a disk scan utility after you've copied off the data you can to see if it finds/corrects errors on that drive.

David