Community
Inventor Forum
Welcome to Autodesk’s Inventor Forums. Share your knowledge, ask questions, and explore popular Inventor topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Inventor 8: FATAL ERROR: Schema Migration...

9 REPLIES 9
Reply
Message 1 of 10
rstadler
531 Views, 9 Replies

Inventor 8: FATAL ERROR: Schema Migration...

Loaded Iventor 8 yesterday and migrated a weldment assembly over. So far so good. Created an IDW of the weldment assembly using IV8. Everything was fine yesterday - I was able to open the close the IDW with no problems. Now this morning, when I try to open the IDW, I get the following message:

"FATAL ERROR: Schema Migration occurring without Schema Version change. Migrating: DLxView"

What is the problem? The IAM opens fine.
9 REPLIES 9
Message 2 of 10
rstadler
in reply to: rstadler

More clues... tried opening the IDW with "Defer Updates" option checked and file opened OK (w/ lightning bolts next to each view in the browser). Tried opening the IDW again (this time w/o "Defer Updates" selected) and the file opened OK - just as if the orginal "Migration Schema" error never occurred. Very strange behavior from IV8 and with sunspot activity very low today I'm at a lose as to what to blame this anomaly on.
Message 3 of 10
Anonymous
in reply to: rstadler

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)
Message 4 of 10
rstadler
in reply to: rstadler

I don't recall changing anything in the assembly - even if I did, I'm pretty sure I shouldn't be getting this error. Right now everything seems to be working good (fingers crossed, knock on wood). If this happens again, I'll post a new message under this thread.

Thanks for your response.
Message 5 of 10
Anonymous
in reply to: rstadler

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: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)
Message 6 of 10
Anonymous
in reply to: rstadler

I received the
following info on this problem this morning from Richard Rankin, and this
procedure did

work for me and I
was able to then open my drawing and work on it. Posting the info here for
anyone

else who may
experience this problem.


size=2>
 

Bob
S.


size=2>
 

From
Richard:


size=2>
 


size=2>Information received from other customers suggests that if you open
another idw first and then open the troublesome idw it should be OK to open,
save and open it again.


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

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)
Message 7 of 10
rstadler
in reply to: rstadler

I 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?
Message 8 of 10
Anonymous
in reply to: rstadler

Thanks for keeping us informed.
Message 9 of 10
Anonymous
in reply to: rstadler

AutoDesk's stance is that it should be able to
migrate templates with no problems.

 

Bob


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
I
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?
Message 10 of 10
Anonymous
in reply to: rstadler

My comment the other day was not meant to cast
doubt on migration.

 

If you have had (lots) of problems with basic
drawings, we have noted several situations where the template had
issues.

 

Typically it was a VERY OLD template that had an
imported title block and sometimes a log that came in from ACAD or
MDT.

 

If you have not had problems, R8 is should not
cause you any.

 

That said - there does seem to be an issue creating
drawings from weldment assemblies.

 

This seems to manifest with a "schema migration"
error.

 

We are working on it...

 

(not sure why it didn't show up in the
BETA)

 

- G

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report