Problems checking in SolidWorks files from Inventor

[lucmartzz]

Hello,

I'm having an error when trying to check in SW files that are inside an Inventor assembly, it is the typical "An existing connection was forcibly closed by the remote host" error and I have tried all the things that can be found on the help pages.

Today I found out that the problem is just happening with files saved in SW2023 SP2.1, because I tried with files from SW SP2022 SP5 and the check in happened without problems.

Can someone try to replicate this problem or share a possible solution?

Thanks

[Gabriel_Watson]

What are your Inventor and Vault (plugin) versions? If your Vault is 2023, perhaps the Vault plugin must be updated to support a later release of SW files.

I know it is different, but every Vault add-in for Solidworks only seems to support files of the year-before SW release:
https://apps.autodesk.com/VLTC/en/Detail/Index?id=2739166946862058678&appLang=en&os=Win64
So maybe you're looking at one-year-earlier version support — just a thought!

[lucmartzz]

Thanks @Gabriel_Watson for the answer.

Unfortunately I'm using Vault Basic, so I don't have access to the vault plug in. 

I'm using Autodesk Inventor 2024, vault basic 2024 and Solidworks 2023 SP2.1

Any other suggestion?

Thanks in advance 

[Gabriel_Watson]

Vault Basic should have the Inventor add-in too, I believe. Maybe reinstall Vault after Inventor is already installed to get the add-in.

I would try updating all apps and testing the same assembly checked in from another PC. If those fail you could probably check the Vault server logs at the time of check in to get more information on that connection loss.

I would also submit a post-purchase support ticket where you may be able to share your data for testing under NDA:
https://www.autodesk.ca/en/support/contact-support

[lucmartzz]

Hello @Gabriel_Watson 

Indeed, that's what I'm doing, using the add-in in Inventor. 

I installed the latest update on server and clients, tried from different computers as well and always have the same results.

Maybe someone can try with the attached files.

Thanks in advance for the help!

[Gabriel_Watson]

That was great, thanks for the files for testing... I was about to throw in the towel on this one! =D

I was able to check in the assembly with the reference just fine in Vault 2024.1 (Beta), but I wonder if you are running the latest update 2024.0.1 for Vault. And according to this article below, you can also check if the Vault server has the same level of updates as your client... although that rarely would break anything:
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Vault-Check-in-err...

What happens when you break or at least suppress link to the SLDPRT file reference in Inventor?

Another thing to try is asking your Vault admin to start the command prompt (cmd) in the Vault server, and execute this command "iisreset". This spooks some ghosts in the machine when it comes to connection services too.

[lucmartzz]

@Gabriel_Watson 

I can see the server and client on 2024.0.1 

I wonder when the 2024.1 is going to be released 🙂 

About the other list of possible issues 

• Latest updates for Vault Server and Client are not installed. - Checked
• Vault updates only installed on client but not on server. - Checked
• Firewall configuration. - I doubt this is the problem. I can do check in with older SW files
• Vault connection blocked by Antivirus software. - Same reason as above
• Unreliable connectivity between the Vault Server and Client. - Same as above
• Performance problems on the Vault Server. - Same as above
• A misconfigured Proxy setting. - Same as above
• Corrupted file data. - You already tested the file by doing check in.
• Vault Client installed using Windows account with insufficient privileges. - Any other type of files can be checked in.

The reset of the IIS didn't solved and if I break the link it can be checked in.

Any other suggestion? 

[Gabriel_Watson]

Well, you did your homework, but now it's up to the devs or support team I guess. I don't want to think it is a version compatibility issue because then it would take longer to wait for 2024.1 to come out...
Let me tag @ihayesjr to see if he can test your file ahead of anyone on support.

[ihayesjr]

@lucmartzz 

I am not able to reproduce this issue. Can you review the Vault server logs at the moment that this failed to see what it recorded?

[lucmartzz]

@ihayesjr thanks for the answer. 

I think this is the right file that should include the log error but I can not find anything explicit about it inside.

Please advice.

[ihayesjr]

Look in this log.

[lucmartzz]

@ihayesjr please check the attached image

[ihayesjr]

Does this error happen only when you attempt to check in this version of a Solidworks file?

[lucmartzz]

Correct, only SW 2023 SP2.1, I did check in of SW 2022 SP5.0 without problems.

[ihayesjr]

I recommend you create a support ticket so that it can be further investigated.

[lucmartzz]

@ihayesjr alright!! Thanks for the help!