pack and go assemblies not saving

[RobinParkes]

I am a single user and after I pack and go some assemblies they will not save after the assembly is re-opened.
Any ideas?

[Anonymous]

Could you be a bit clearer.

Are you saying there's no H/D activity or Inv spits out and error message ?

Which version of Inv are you using ?

Which project file are you using to open the P&G'd files ?

What settings in P&G and the new project file are you using, in particular are you using relative file paths, do you keep the
directory structure and how do you treat Library files ?


--
Duncan
"Humour ... is one man shouting gibberish in the face of authority, and proving by fabricated insanity that nothing could be as mad
as what passes for ordinary living."
(Terence 'Spike' Milligan K.B.E., 1918-2002)
www.autodesk.co.uk/inventorjobs



wrote in message news:4860302@discussion.autodesk.com...
I am a single user and after I pack and go some assemblies they will not save after the assembly is re-opened.
Any ideas?

[RobinParkes]

Sorry for vagueness.
Most P&G's do save but when they don't there's an error message similar to the following:
! Erros detected while writing segment Am Graphics Segment in database.
! Error detected while saving object of type AM x Node Override Attribute.
! The database in (main assy number) could not be saved.
Version is IV8
Using main assembly to open the P&G file.
I copy to single path and include linked files and don't skip library files.

And there are holes in the sky where the rain gets in but the holes are small, that's why rain's so thin! (Same chap)

[Anonymous]

Have you tried going back to the original un-P&G'd assembly and tried saving that ? What was the outcome ?

Is the error repeatable for the affected assemblies ?

Have you tried Re-build All then saving before P&Ging

(The next sounds crazy - but there is madness in my method )
Have you tried Update Mass Properties, then saving before P&Ging ?
Updating Mass Properties forces Inv to change the properties on more files and therefore forces it to save more. This might
highlight the problematic file before P&Ging.

When you get an error message select the Copy to Clipboard button in the bottom left hand corner. Then paste that into either
Notepad and save or paste it into E-mails / postings. The error message has more data hidden behind it which can be helpful -
particularly to Adesk - in solving this issue.

Which template files are you using, are they native Inv8 or migrated from an earlier edition ?

"You can fool some of the people all of the time, and all the people some of the time, which is just long enough to be president of
the United States." (Puckoon) {ibis}



--
Duncan
"Humour ... is one man shouting gibberish in the face of authority, and proving by fabricated insanity that nothing could be as mad
as what passes for ordinary living."
(Terence 'Spike' Milligan K.B.E., 1918-2002)
www.autodesk.co.uk/inventorjobs




wrote in message news:4860358@discussion.autodesk.com...
Sorry for vagueness.
Most P&G's do save but when they don't there's an error message similar to the following:
! Erros detected while writing segment Am Graphics Segment in database.
! Error detected while saving object of type AM x Node Override Attribute.
! The database in (main assy number) could not be saved.
Version is IV8
Using main assembly to open the P&G file.
I copy to single path and include linked files and don't skip library files.

And there are holes in the sky where the rain gets in but the holes are small, that's why rain's so thin! (Same chap)

[RobinParkes]

Tried all your suggestions, which didn't cure the problem but made me realise that behind the daunting error message there might only be one problem file.
This was in fact the case and when I deleted this from a nested assembly, everything saved fine!
Thanks for your help, Duncan, and for the Milliganisms!

[Anonymous]

Glad to have been of assistance.

We are programmed to serve.



--
Duncan
"Humour ... is one man shouting gibberish in the face of authority, and proving by fabricated insanity that nothing could be as mad
as what passes for ordinary living."
(Terence 'Spike' Milligan K.B.E., 1918-2002)
www.autodesk.co.uk/inventorjobs


wrote in message news:4860379@discussion.autodesk.com...
Tried all your suggestions, which didn't cure the problem but made me realise that behind the daunting error message there might
only be one problem file.
This was in fact the case and when I deleted this from a nested assembly, everything saved fine!
Thanks for your help, Duncan, and for the Milliganisms!