Using Inventor 2023.2
Suddenly SOME of my files can't be Checked in. Very weird.
Despite reaching 100%:
It prompts an error:
Are there any error logs somewhere (for Inventor and/or Vault), or some kind of info that goes at least a tiny bit further than "Unknown Server Error"....?
I've also tried to check-in directly through Vault (Professional 2023.2), but it just told med this:
@EdvinTailwind wrote:
Are there any error logs somewhere (for Inventor and/or Vault), or some kind of info that goes at least a tiny bit further than "Unknown Server Error"....?
That will be on the Vault Server.
Is that the only file has problem?
You're only user having this problem?
Reboot your computer?
Looks like they are new files. Duplicated name? Broken link?
Try update Vault Server, Vault Client and IV.
I have dreaded this error in the past.... it appears usually when the Vault Server ran out of disk/storage. Check with your PDM/Vault administrator or IT infrastructure folks if this is true. They will need to add hard disk space or increase the virtual machine partition allocation for the Filestore drive.
More here:
Sorry for the late reply! I left work before seeing your replies. Upon returning this morning, everything works normally.
@Frederick_Law : Prior to posting this topic I rebooted both Inventor, Vault and finally the computer, without any success. There were 5 files that didn't work of a total of around 20. Most of them have been checked in before, while a few were new to Vault.
The error was, as you wrote, most likely on the Vault Server, and @Gabriel_Watsons hypothesis regarding disk space seems quite likely. I never got the chance to check with the Vault Server admin before this was resolved. In case I get any additional info, I'll let you know.
Just had a chat with the senior mechanical designer over at our parent company where the servers are located (~45 km/~28 miles from here). Not Cloud-based storage, but virtual servers on our own hardware. They did have general server issues two days ago, mainly with the CMS though (which have more users than Vault), and IT had done a reboot on all hardware hoping that things would start working as expected. So unfortunately no clear answers on what could be the actual issue. The CMS and Vault Server aren't supposed to share the same hardware, but there are indications on someone (?) might have started utilizing the Vault hardware for CMS purposes.
Good Morning All, just wanted to let you know that I/we had the same issue, and the solution for us was a server reboot.
Can't find what you're looking for? Ask the community or share your knowledge.