Autodesk Inventor Publisher

[#1]

I have a user who is trying to insert an Inventor 2012 file into Inventor Publisher 2012..

Here is his workflow:

Opened Publisher 2012

Clicked Create New File

Went to Vautl tab in ribbon panel

Clicked on the insert button

Drilled down into Vault Product libraries folder and clicked on Saturn folder and got the error shown in the attached screen capture.

The user hit the continue button and nothing happens.  The user then closed the application and re-opened and gets the same result.  He does not get this error on all folders, but he does on some..

I just tried the same workflow on my workstation and I do not get this error.

Please help ASAP because my user cannot get his work done.

Thanks!

[#2]

I want to keep this problem relevant because this problem also exists in Publisher 2013 but instead of getting an error message, Publisher crashes.  See Autodesk case 07709148.

Please help!

[#3]

Thank you for reporting this issue. I have filed a issue in our internal track system.

By the information of the screenshot, I guess there might be a file which has no file extension in the 'problem' folder.

If yes, please try this workaround :

rename the no extension file to has a extension or remove this no extension file.

Publisher QA

[#4]

That is not the issue at all.  This is a Vault folder filled with 1811 Inventor files.  Inventor Publisher will not display the contents of certain Vault folders and we get this error in Pub2012.  In Pub2013, we do not even get an error, the application crashes. These folders are children folder in Vault with ACL's defined by the parent folder, so we should have the same permissions in every child folder.  The problem is that we don't, only in Publisher.  We cannot access certain folders in Vault because of this error and we are unable to get our work done!

See tech support case #07709148 for more details

I'm attaching a copy of the error details.

Thanks for your help with this issue.

[#5 · Accepted solution]

I just received a new dll file from the Autodesk Publisher development team and it fixed the problem.  Thanks to all at Autodesk who helped fix this problem for us!