Redirection Rules will be iqnore - Inventor - Redirection rules?

[Mark.Lancaster]

Helping someone out and this is the first time I ever seen a message like this..

Since I'm unable to access the assembly at this time, is this message related to Inventor, iLogic or something from Vault..  I'm lost at this point..  

In

[mcgyvr]

My google skills show that this is related to an error from Vault (see post 15 in this thread for mention if like error messages)

https://forums.autodesk.com/t5/vault-forum/error-message/td-p/1674891?db=5

[Mark.Lancaster]

@mcgyvr

Really you have google skills?  Where did you go to school to learn that and who says things like that?  Are you here to help or simply state I can't google things?   

I guess putting too much info into google didn't point me to what you found..  Funny thing is, this has nothing to do with Vault Autoload.   This assembly has been in Vault for a year or so and has been worked on many times in Inventor.

[mcgyvr]

My fault... Let me restate...

My Google-Foo is strong grasshopper and the only mention of said message phrasing seemed to come up in a thread related to Vault..

I assumed that your question would be solved by an answer that determined if said message was generated by an ilogic rule or Vault or the Inventor software itself.. 

As the ONLY mention of said message was in a forum related to vault with zero other references on the internet I assumed that said message was generated by Vault and somehow related to that..  It may have only been generated this time because something is corrupted or something hence why it hasn't been seen before even though this assembly has been accessed numerous times in the past....

[Mark.Lancaster]

@mcgyvr

Now I need to hire a lawyer to understand the gibberish you just used in your reply..

[Mark.Lancaster · Accepted solution]

I discovered that a sub-assembly was the cause of this..  The end user noticed something didn't look right in one of the thumbnails of the assembly they were trying to open (and got the message).  When he went to open that given sub-assembly, he got the same message.  We looked into Vault and he realize the assembly was checked out a couple of weeks ago and no one was supposed to be working on it.  When we went back and got the previous version in Vault we noticed the assembly causing the issue had a file size of 7mb where-as the previous version was only 2mb in size.  Once we swapped with the previous version of the sub-assembly the issue went away.

[mcgyvr]

So you are saying it was an error message related to/generated by Vault 

[Mark.Lancaster]

Although we used the older version of the assembly in Vault to resolve the issue..  The issue had nothing to do with Vault.  One of the test we performed was to create a standard single user Inventor project file with no connection to Vault and still got the same message