Weird corrupt assemblies in SWx2010

Hi All,

I'm having a REAL head scratcher here at the moment.

We're working with a bunch of large assemblies here at the moment on
our network and I'm having a problem on my workstation whereby when I
open one particular assembly it opens with a bunch of mate errors. If
I rebuild a bunch more pop up, but if I then RELOAD the assembly they
go away and the assembly builds fine.

The thing is that when I come to shut down SolidWorks, SLDWRKS.EXE
won't shut down and needs to be shut down from the task manager.

The odd thing is that this assembly opens, rebuilds, behaves and saves
fine on every other workstation in the office.

Colleagues of mine are having trouble with other assemblies that open
and build fine on my machine but not on theirs.

It's almost like there's some kind of local copy or outdated version
being held in memory or cache somewhere that's being dragged up when
it's loaded but disappears when it's reloaded. I don't think it's a
SolidWorks setting as it's occurring across multiple workstations with
different assemblies.

Right now this is pretty much crippling our design effort on a project
as there are a bunch of assemblies which are now extremely fragile or
unusable, and we're also reluctant to release designs for manufacture
when assemblies might not be building correctly.

I've tried everything I can think of to solve it, including creating
local copies of the assemblies, moving the entire master assembly to a
new folder or location and nothing seems to work.

Running SW2010 SP3.0 and also all other earlier service packs and the
problem is consistent across all.

Anyone got ANYTHING I can try to alleviate it?

Thanks,

George.

 

Hi George

I experianced something similar and finaly traced it down to a
subassembly a few levels down which was set to flexible.
Seems like SW2010 doesn't like flexible subassys in the same way 2009
did.

// Krister

 

Hi Krister,

Thanks for that. I'll try making the subassembly rigid and see if that
helps.

You'd think that flexible subassemblies would be something they'd have
gotten dorted out properly by now wouldn't you?!!?

George.

 

George

For sure, YES, but I see that every time I open an old assembly in a
new version the tree goes red so I'm not surprised.

// Krister

 

I don't want to explain ....

 

No worries, Huppe, we understand

// Krister

 

If you think about it instead of just whining ...

HTH

 

Dear Huprich

I was certainly no whining....first I tried to help George a little
and secondly I kind of agreed to that SW shoould have solved the
problems with flexible assys.
I have tried to open old assys in new versions of SW and the tree goes
red. Not surprised, but futher more not whining, simple clear
statement, Could have been my bad, could have been SW.

I've got a feeling that You are picking on me for other reasons than
above mentioned,........so........if You have nothing to add to this
specific or other clear SW issues,,,,please shut the **** up.
I can't really understand why You have to chime in everywhere, and
obviously You don't either, otherwise You would should understand that
You and Your buddy Bonker has sent thís newsgroup to a far too early
burial.
I can't remember even once that you have posted anything here that
could help anyone solve their problems with SolidWorks, coz after all,
and this might surprise You, this is a SolidWorks newsgroup.

// Krister

 

IIRC I sort of suspected hardware issues & corrupted files/software.

Did you want to migrate the old data to the new version?
Or do you expect this to be done without intervention by the user?
Sometimes what worked in a prior version is invalid in a later
one & needs to be checked & fixed. Natural state of affairs.
Sometiimes you do not want to change/update the older data ...

Having done a bit of data migration myself ... in a few cases up 10
or so major revision levels ... plus translation stuff, such as
Catia & CADAM & VDA to UG ... plus such as CADDS ...

I usually do not.

Speak to yonnie (bunko) bonkers.

Does that have anything to do with CAD, CAD/CAM, math models,
associativity, design, computers or data?

 

You always sort ot suspect things afterwards...... idiot....

Not of Your fucking business..... idiot

So why didn't You try to help George at first ...stupid
moron.....you're just a fucking besserwisser...always knows best
afterwards

Always does....but always afterwards when problem is already
solved ...idiot

I'm talking to You..... idiot....if Bonker speak, You speak....same
same

Does anything You post here have to do with above mentioned???????

// Krister

 

I just did not post. Til you jumped up & said "Me too".
Now you whine about that too, eh? LOL ...

See? So what do you expect it to do automatically?

Waited to see what you would say.

So NOW you agree with me & think you were perhaps wrong?
LOL.

In what way did "Me too" solve any probems?

Was your whine, not mine.

Free clues.

BTW, Know how to play 20 questions?
Try it to solve such problems.

HINT: Find the minimum part/assembly that demonstrates
the problem.

HTH

 

BTW, Check the cables too.
And ping the servers and the servers from other boxes.
If you are losing packets or retransmitting them or times
vary a lot ... you have network problems.
Bad ones can corrupt files IIRC.

 

Cliff

What do You actually know about SolidWorks?

// Krister

 

Just came across this myself.. Running SW2k9, I opened an assy, made one
of my rigid subs flexible, forgot to change it back, saved it and closed
it.. opened it a few days later and 'KAAPOWW' everything was broken.

Glad I still watch the group.. I would have went nutty trying to figure
out what was wrong.. lol

 

What do you actually know about CAD/CAM systems, data, computers & networks?

Or solving the related problems that sometimes crop up?

I had TECO programs mass-editing IGES files to make changes
to CAD part files otherwise costly before you were out of diapers
I suppose.
I've actually used AD-2000 too.
http://www.americanmachinist.com/304/Issue/Article/False/9168/Issue

BTW, Another free clue: IF this problem was endemic to SW
there would be constant complaints from almost all.
There are not.

Want to claim it's user error?

 

Don't know much about cam, don't use it. Used SolidWorks daily since
1998, AC before that.
(Irrelevant question and not a good answer to mine.)

Went out of diapers in the mid-50's and if You edited IGES files back
then, You'r'e really good.

Seen and heard about a few. In this group it's almost only You and
Bonker left and none of You use SW so no wonder You hear no
complaints.

More or less Yes, it sure could be. Documentation sais; Dont save
assemblies with flexible subassemblies inside. Sometimes we forget
about that, done it myself a number of times.

// Krister

 

I said CAD/CAM, not "CAD" & not "CAM".
SW is CAD.

So what did you do prior to 1998?
There were computers, CAD, CAM & CAD/CAM things before that.
First one I wrote a program for: http://en.wikipedia.org/wiki/IBM_1620
Educational.

With higher (cheap) bandwidths many/most went to BBS systems
that allow binary files, coloured pictures & script kiddies.
Plus many ISPs dropped newsgroups.

BTW, SW is just CAD.

Fair enough. NOT SW's fault then, eh?

BTW, Good book: http://tinyurl.com/26dlv9m

 

I know SW is CAD...I use it every day. The problem appeared in SW
which is CAD. I asked You: What do You actually know about SW?
And as always You start babbeling about something else.

I used AC (AutoCad) prior to 98....and I believe Your program on that
IBM won't help George at all as he's using SolidWorks.

Never said it was SW's fault, never said it was anyones fault. Said
You most likely have a problem if You save flexible subassemblies
within a main assembly in SolidWorks.

// Krister

 

So You read just the subject line, ignoring what he wrote in the
message......no wonder
Then You started with: "I don't want to explain". Means "I have no
fucking idea what's going on here, coz I don't use SolidWorks"
Think my assumption was no too bad as it turned out later that he had
a flexible subassembly in there. Should be interesting to see if that
was the problem.

I already told You what SW said: Dont save an assembly with flexible
subassemblies inside.

What bonker said?....nothing could interest me less....and it can't be
worse than Your bunkum

// Krister

 

That was not CAD.
Juat learning a few programming languages back then & etc.
Mostly we used slide rules, pen & paper (though lesser beings used