Community
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Richard Rankin (Support)" <richard dot rankin at autodesk dot com>
wrote in message
href="news:99DDA9FA2E5B51CC1C64F7230FAC3712@in.WebX.maYIadrTaRb">news:99DDA9FA2E5B51CC1C64F7230FA......
Did you possibly change anything in the design view, in the
assembly, anything at all?
We did have a report of a similar error message during the
beta testing but this particular problem was resolved in the shipping product.
This was related to design views and newly defined design views.
Switching to one of the default design views helped in that
instance.
You mentioning this makes me think that it may be related
but not 100%. Maybe turning off Defer Updates helped avoid
this.
If this happens again, I would be very interested in getting
hold of the unhealthy dataset.
--
Best Regards
Richard Rankin
Autodesk Manufacturing
Solutions (Support)
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Bob" <
href="mailto:bobschader@yahoo.com">bobschader@yahoo.com> wrote in
message
href="news:257208AC6774FC6F507B359BCD7A7C03@in.WebX.maYIadrTaRb">news:257208AC6774FC6F507B359BCD7......
Richard, I have a drawing that is doing this now,
and I did not change anything in it.
I posted about it under a different thread. Defer
updates did not help, nor did even
renaming the asm and selecting skip at the dialog
box. Can you work directly
from just the drawing file, or do I need to try a
packngo operation?
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Richard Rankin (Support)" <richard dot rankin at autodesk dot
com> wrote in message
href="news:99DDA9FA2E5B51CC1C64F7230FAC3712@in.WebX.maYIadrTaRb">news:99DDA9FA2E5B51CC1C64F7230......
Did you possibly change anything in the design view, in
the assembly, anything at all?
We did have a report of a similar error message during the
beta testing but this particular problem was resolved in the shipping
product. This was related to design views and newly defined design
views. Switching to one of the default design views helped in that
instance.
You mentioning this makes me think that it may be related
but not 100%. Maybe turning off Defer Updates helped avoid
this.
If this happens again, I would be very interested in
getting hold of the unhealthy dataset.
--
Best Regards
Richard Rankin
Autodesk Manufacturing
Solutions (Support)
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"rstadler" <I
href="mailto:rstadler@havencut.com">rstadler@havencut.com> wrote in
message
href="news:f19ef9b.7@WebX.maYIadrTaRb">news:f19ef9b.7@WebX.maYIadrTaRb...
promised an update if this error surfaced again - well, it has. Weldment
assembly was created in IV8, IDW was created in IV8, but upon trying to reopen
the IDW after being away for lunch, the "Schema Migration" error showed it's
face. As suggested by others, I opened another IDW (radomly selected and
probably created in IV 6 or 7) and tried to open the afflicted IV8 IDW, the
IV8 file opened just fine. My IDW templete was created back with IV5 and has
been continously upgraded with each release. Should I recreate the IDW
templete from scratch with IV8?