Error 1200 communication failure between client and server

[Dan_Malott]

I keep getting this error when I try to Update and item master in Vault Professional 2011. Error 1200 An error occurred due to a communication failure between client and server. I have tried to change the State to Released and I cannot do that because he file needs to be updated.  Continuous loop.  Any ideas on what to change to get the item masters released?

[mollons]

This is an error that can happen due to many reasons, usually when the server doesn't know what else to do. Unfortunately the error message itself doesn't help us track down the problem.

Could you rerun the workflow that causes the error and attach the server logs from the same time? This shoudl help point to the actual error taking place.

[Dan_Malott]

Here is the log file.  I currently have over 50 files i cannot update the item master or change the state to work in progress.

[mollons]

What version of Vault are you using?

[mollons]

Actually it looks like you are using Vault 2011 SP1.

Can you try installing SP2 and see if you still have the problem?

I think this looks similar ot something we fixed in SP2...

[Dan_Malott]

I have installed SP2 on the server and the client locations and i still have some files that will not update or allow me to change the state.

[mollons]

Could you try to check out one of the files in the appropriate CAD app, make some small change (even draw a line and delete it), save the file and check it back in and then try the update again?

This would be to check to see if something had gone wrong with check-in of the file.

[Dan_Malott]

These all appear to be IAM files.  I open one, moved a constraint, and checked it back in with the same error when I try to update the item master.

[mollons]

Your log file also shows that there are alot of files the server does not seem to have access to.

Was your filestore recently moved to a new location?

Can you change your working folder to a new empty location, and do an Open From Vault on one of these assemblies? Does the assembly then open without any unresolved files?

It might be best to open a case with Product Support, as they can do a remote support session and look at your situation directly.

[steveh4]

FYI...Installed Update 2 and did not fix our problem either with this error. I have an SR also in regards to this issue.

[Fedor76]

Same problem over here now. Only after installing update2. The error apears on the AssignItem action on existing vault files. With new created files it's works well.

[Dan_Malott]

Update 2 did resolve some of the problems but I still have a handful of items I cannot change state to released.  I am still working with tech support on this issue.

[steveh4]

I was pointed in a direction that something is not getting from INV to Vault. It was recommended to do a RebuildAll in INV and check the file that is causing the issue back in.

I had a dozen or so files causing the 1200 Error. I did the RebuildAll and checked them back in. It appears that it has resolved the error. At least for me it did.

Good Luck,

[Anonymous]

I'm having this same issue with a specific file, but the rebuild all command does not resolve the issue. Our IT personel says our server log isn't available do to a nightly server backup. Could this backup be causing my error 1200?  If so why hasn't it effected any other files? What are some other possible cause are there that I could troubleshoot?

edit: I only have service pack 1, IT personel are getting me service pack 2 now.

Thanks,

Karl

[mthomas]

We're getting this error more and more frequently now. In some cases a Rebuild All of the Inventor component will correct it but in most cases it won't. If anyone has found a solution I'd really like to know

[Raider_71]

Hi has anyone got an answer for this issue yet? I have even loaded the latest hotfixes for Vault 2011 on Satureday but we are still getting the error 1200 communication error. What could it be? Any help would be appreciated! We have managed to get by with doing the rebuild all but this only works on some of the items!

Pieter

[Richard.Rankin · Accepted solution]

Hi Reader,

This appears to be one our most viewed threads without an accepted solution.

To summarise the thread, most incidents of this error have involved the following:-

1. Check out file from Vault
2. Open the Inventor assembly in Inventor
3. Perform a rebuild all
4. Check in file to Vault
5. Assign Item to the file

Reports of this in newer versions of Vault are rare. However if you still are experiencing this issue, upgrade to a newer version of Vault and ensure you have the latest updates installed.

If you still continue to have issues with supported versions of Vault, contact Autodesk Support for assistance.

[olegd.prod]

Hello there,
we've noticed a lot more traffic to this forum post recently.

If you arrived at this topic because you searched for a problem you are having in Vault, I'd like to ask for your help.
Can you please post any screenshots/error details/etc that you saw in Vault and that caused you to find this topic?

My hope is that we may get some clues as to what is going on, and that we can come with a few theories we can test on our side.

Thank you in advance!

Oleg