ERROR UNHANDLED EXCEPTION WHEN CHECK IN DWG WITH VIEWS FROM INVENTOR

[jeamy.baena]

Greetings, Experts

Currently, I have a drawing in AutoCAD with views generated from an inventor assembly, using the command viewbase. The inventor assembly is already in Vault.

Now, when I am going to check in the drawing in AutoCAD, I receive this error "UNHANDLED EXCEPTION"

Any ideas about this error?

I tested in two different Vault servers, but the error is the same.

Please, see the attached files, I hope that someone can reproduce the error.

Thanks!

The Vault 2016 build is 21.1.4.0, with the last hotfix DM211410.

[reidmatthew]

@jeamy.baena

Thanks for posting to the Autodesk Forums! Are you still looking for help on this check in issue? Let me know and I can attempt to reproduce on a test Vault and let you know what I find out.

Thanks

[jeamy.baena]

Hi, Matt

Yes, I am!. Any help will be appreciated!

Thanks!

[jeamy.baena]

Hi, Matt

Any news about this issue? 

Could you reproduce the error?

Please, Let me know if you have questions.

Thanks for your help!

[reidmatthew]

@jeamy.baena

I was able to reproduce this unhandled exception error you are seeing when checking in this particular DWG. The interesting thing to note is that the error only shows up when the latest hotfix for Vault (Cumulative Hotfix 1 for Autodesk Vault 2016 Service Pack 1 DM211410) is installed. I tested it on Vault 2016 SP1 without that hotfix and it checks in fine. 

Would you be willing to do a couple of things for me

1. Send me the exact steps you did to create this Views.dwg file or send a Autodesk Screencast video? That way I can try to reproduce this and possibly send it to our product teams for investigation and a potential fix.
2. Does this exception happen for all DWG files created using viewbase?

Let me know if you have questions.

[reidmatthew]

@jeamy.baena

Have you been able to record a video or compile the steps to reproduce this issue including the steps to create the DWGs that cannot be checked in?

If you need more help or have questions, let me know.

[jeamy.baena]

Hi, Matt

I apologize for the delay.

I tried with with new drawings and inventor parts, but the error is the same.

Also, I uninstalled the last hotfix (sever and client) but the error was the same.

The steps to reproduce the error are:

1. Generate a part or assembly inventor. A vault project must be exist and configured in Vault Desktop app.

2. Check in those inventor files and preserve the local copy in the working folder.

3. Create an empty drawing in AutoCAD (in the same folder with the inventor parts) and switch to layout.

4. Use the command viewbase, select the previous project file used in inventor and select the inventor file to generate some views.

5. Save, login into Vault.

6. Try to check in the files and the error appears.

If you need the complete video, let me know.

Thanks for your help!

[reidmatthew]

@jeamy.baena

Thanks for the steps to reproduce. That is interesting that you were still getting the error even after removing the hotfix. I am currently trying to get confirmation from a teammate to see if they can reproduce this using your files. I am going to remove the hotfix and see what effect that has on my test machines and do a bit more testing this week. I will get you an update soon.

[jeamy.baena]

Hi, Matt

Ok, Thanks for all your help!!

[jeamy.baena]

Hi, Matt

Any news o solution for this problem?

Thanks!! 

[reidmatthew]

@jeamy.baena

I tried to reproduce the error on my end again on a machine without the 2016 SP1 HF1 and was unable to reproduce it using your sample files or by creating new files. It seems that I can recreate the error only when the newest hotfix HF1 is installed on the client and server machine. I wonder if I am not understanding your workflow exactly. 

How did you remove the hotfix from the server? Did you completely uninstall the Vault ADMS on the server and reinstall?

Would you be willing to get on a call with me outside the forum to look into this a bit more?  

Thanks

[reidmatthew]

@jeamy.baena

I am just following up to see if you would like to be contacted outside the forum and discuss this error more. I have not been able to reproduce the error without the hotfix 1 for Vault 2016 SP1 installed. 

Thanks