Custom Open From CC Broke

[cadman777]

Has anybody had this happen to them, and do they know the cause and how to fix it?

I've been 'working' the software for the past 2 weeks making custom CC parts (some Authored to work in FG and others not).

All of a sudden, when I tried "Open From CC" > "As Custom", this error pops-up "Unable to Create Component".

I've had that before when the part wasn't made right, so I spent the past 6 hours trying to trouble shoot the problem.

Finally I downloaded a known good part from CBliss's iParts, and authored it exactly as Dennis Jeffrey's "Publishing Structural Components to CC" white paper lays-out. SAME ERROR.

At this point, I'm beginning to believe this installation of Inventor is CORRUPT, and the cause of it was 'pushing' the software to make all these custom parts. This is what leads me to believe that the program installation is corrupt: I had rebooted and cleaned-out all the system temp folder files, and did everything from a clean boot/open Inventor. Then I used CBliss iPart, and the Author/Publish failed in the same way. Also, I can create this same part in the FG, AND place an instance of the part into an assembly using RMB>"Place from CC", AND create an instance of it using "Open From CC" > "As Standard", WITH NO ERRORS. So, the problem is, the damned program won't allow me to create the part "As Custom". Also, for the past few days, the program has repeatedly locked-up after numerous uses of Excel to edit the iPart Table, which forces me to close the program, clear the system temp folder of all files, and restart the program to resume my work. Sometimes the program forces me to reboot the computer in order to clear the temp folder of all files to ensure there's no lingering data tied into the program. This reminds me of my Autocad days when I wrote AutoLISP progams for Autocad using Visual Lisp Editor. My guess is the data-link between Inventor and Excel has caused a corruption. If that is the case, I would like to know the truth, and if it is true, then I want to know if the developers have fixed this problem in release 2015.

Something in the program is broken, and I don't know how to fix it. If someone out there knows what it is, or has had the same experience, I would appreciate help in fixing this. Thanx.

[blair]

The only thing left would be a failing component such as the HD where the disc data is becoming corrupt. Possibly a severly fragmented HD that's now written bad data that the software is no longer able to read properly.

It would mean doing a full re-format of the HD, install Windows, Windows Updates, software and software updates.

[cadman777]

After a few reboots of the computer the parts seem to be working now.

The only thing I did new on this machine is uninstall and install the .NET Framework programs (4.0, 4.5.1 & 4.5.2)

So, I'm guessing that was the problem.

But knowing which one fixed it is difficult to determine, b/c I tested the machine after each install, and nothing was fixed. But now, WHO KNOWS WHAT HAPPENED (???), and it's fixed.

Thanx for your extended help.

I learned a lot about .NET and how important it is for app functionality on the OS.

Cheers

[blair]

Glad to hear everything is working,

Have a Merry Christmas.

[cadman777]

Same to you!

[blair]

I would run the Windows Disc Defrag tool on this unit and defrag the HD. Depending on which version/flavor of Win7 you have, you might be able to set this to defrag on a regular basis.

Little anomalies pop up like this when a drive becomes heavily fragmented. On our servers and workstations we found the number of "issues" drops considerably when they are properly defragmented.

[cadman777]

Thanx for the advice.

I forgot all about that.

I got a 64 bit defrager that's pretty good (forgot what it's called), but it's supposed to be much better than the MS one.

We'll see if it helps.

Do you guys run the defrager on your SSD's or only your HD's?

reason I ask is b/c the tech guy I bought the SSD told me they degrade from read/write cycles (which is what a defrager does), but not from read cycles only.

[blair]

We use "Condusiv" that has functionality designed for SSD drives as well.

[cadman777]

Thanx for the tip, I'll give it a try.

I thought that was the one I already had, but guess not.

It's the SSD function that makes it valuable.