I inherited a project that was working beautifully with Inventor/Intent 2010. I am trying to bring it into ETO 2013, but when I try to open the assembly, it starts to build then crashes with the error below. About 1/3 of the assembly gets built before the crash. It appears that Intent can't find what he's looking for, but I don't know how to tell him where it is. Please help.
An error was encountered while evaluating rule memberPathname, in part Root.Building.Roof.ShinglesGroup.ShingleOne
Exception in function iv_createInstanceDocument [Root.Building.Roof.ShinglesGroup.ShingleOne] Object reference not set to an instance of an object.
It seems that my Assembly is trying to use "old" parts when I try to open it. It is trying to use specific parts with partname.lotsoflettersandnumbers.ipt. I don't know if I need to clear the cache somehow or what. I haven't figured out how to get past this yet. Any ideas?
I woud check the ShingleOne part that is called out in Root.Building.Roof.ShinglesGroup.ShingleOne.
Check the following:
If everything listed above is correct and working then you may try re-adopting the part.
Thank you for the response, Chris. By Factory Files, do you mean Member Files? I opened all my parts with the 2013 version and saved them. Is there more to "migrating" them than that?
By Factory Files, I mean the files that Intent uses to create the member files. They should be in seperate folders.
If you just open the file and save it, this does not cause the file to be migrated to 2013.
There are two ways that you can migrate.
ok. I had skipped the migration step earlier. didn't know I needed to do that. i used the Task Scheduler to Migrate my entire project. But, it didn't help. My factory files (design files) are all where they belong. I have opened the project in Visual Studio and set a break point to try and get to the bottom of this, but Visual Studio just laughs at me when I run the project. No chance of hitting a break point in the ETO Project. not sure how to do that.
Have you tried using the built in "Intent Design Editor"? It can be found in the Inventor Ribbon under the Tools tab. You will not be able to apply breakpoints but you can try commenting things out until you get down to the problem.
If you think a certain file is causing the error, try creating a blank Intent assembly and only place that part as a child in the assembly. You may find that there is a problem with the .ipt or perhaps the intent code.
I have discovered that Intent 2013 is now catching coding errors that it was skipping over in 2010.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.