IV File Association and InventorReset_v1.1.exe

IV File Association and InventorReset_v1.1.exe

tahdesign1
Collaborator Collaborator
706 Views
3 Replies
Message 1 of 4

IV File Association and InventorReset_v1.1.exe

tahdesign1
Collaborator
Collaborator

So we an have issue here where a users profile will drop all the IV file associations.

This prevents several operations from being able to happen (Vault Design Copy for one) because the software does not recognize the file type.

All the IV icons, regardless of their types, revert to an icon that looks like the standard desktop IV shortcut.

 

I have always solved this issue by deleting the IV reg key under current user. Before I do that I make sure they have exported the app options from IV so that can be imported.

 

Sometime late last year I was able to get a little app written by an ADSKer name InventorReset_v1.1.exe

 

Does anybody else have this app and do you know if it alone will fix the file association issue?

 

It would be great if an ADSKer commented on this since it was written by them.

0 Likes
Accepted solutions (1)
707 Views
3 Replies
Replies (3)
Message 2 of 4

Sergio.Bertino
Autodesk Support
Autodesk Support
Accepted solution

Hi,

 

Maybe this link can be helpful for you:

http://knowledge.autodesk.com/support/inventor-products/troubleshooting/caas/sfdcarticles/sfdcarticl...

 


Thanks


Sergio Bertino
MFG Technical Support Specialist
0 Likes
Message 3 of 4

tahdesign1
Collaborator
Collaborator

Thank you for that quick reply.

I am trying to avoid going the route of reg key deletion as I normally have done.

 

In that article it does not specifically say it will fix the windows file associations which is the real problem here.

 

I guess it is just as easy to try and see if it fixes the issue.

 

I will post back if it does.

0 Likes
Message 4 of 4

tahdesign1
Collaborator
Collaborator

It did fix the users problem. So running this tool does reset the users IV file associations.

 

The only thing that he had to reset in his App Options was his name (since it reverted back to his system ID).

 

All other App Options were set when I developed my deployments so they stayed.

0 Likes