Weird error message

Weird error message

fridtjofZM5ME
Collaborator Collaborator
565 Views
4 Replies
Message 1 of 5

Weird error message

fridtjofZM5ME
Collaborator
Collaborator

I've made myself an iLogic configurator that basically is a generalized model of our product, which I use to make customized models for the specific products that go to production. This is fetched from Vault, editet through the iLogic, checked in, and copied through the "copy design" functionality within Vault, then fetched again for next model I'm making.

 

I've been working with this configurator for the past three months or so without much incident, but now I get this somewhat esotheric error message everytime I try to open it. Anybody knows what might cause it and how to get rid of it?

 

error.jpg

0 Likes
566 Views
4 Replies
Replies (4)
Message 2 of 5

bradeneuropeArthur
Mentor
Mentor

Take a look here.

https://forums.autodesk.com/t5/inventor-forum/redirection-rules-will-be-iqnore-inventor-redirection-...

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes
Message 3 of 5

fridtjofZM5ME
Collaborator
Collaborator

Hi there, thanks for your reply.

 

I'm aware of the post you're refering to here, but it sort of just point you towards the general direction of the source of the problem. As assemblies aren't supported by the Content Center, I have a vast array of small subassemblies in my Vault that represent various door handles, lock cases, strike plates, hinges etc.

 

While these ideally shouldn't be subjected to any changes as time passes, I've found that it isn't that simple as I've journied from working with separate project files for each main assembly I make (thus copying everything I need to that folder whenever I need to reuse any previous models), to using Vault and thereby omitting the need to make a new copy of every little piece of hardware, through "copy design"-functionality, and finally implementing iLogic and forms to further rationalize my workflows. Every so often the need to do some tiny changes to these small assemblies, to make them work in a larger context, presents itself and as a result these might end up causing little problems like these in the end.

 

To figure out the problem that generates the error message, I would need to know what causes it within the context of the subassemblies that presumably are the source of the problem and correct the error, rather than reverting to a previous version of them to make the error message simply go away. The more I work with these things, the deeper the rabbit hole gets though...

Message 4 of 5

M.Hawryluk
Advocate
Advocate

Hi @fridtjofZM5ME ,

 

I get the same message, even though parts and assemblies contain no iLogic. I tried to track down files causing the problem but so far, no success.

Message 5 of 5

gilsdorf_e
Collaborator
Collaborator

deleted

0 Likes