Error 1200 + error assign item

[Anonymous]

Hello everybody,

I have some problemes with Vault/Inventor. For information, I am administrator with full rights.

- The first one is in Vault, (see attachment "Error aseeign item.jpg"). This error appears when I want to assign an item (function "Assign item") in the Vault to a file. I have already assign an item to many files before this one but for this one it is impossible. What is the problem???

- The second one is when I want to open a file in Inventor. In tis software, I use the function "Open from Vault" to take the latest version of my assembly (and its dependants). But when I want to open it, I have the following message (see attachment "Error 3.jpg"). What is the problem with Vault or I don't know what but it is very frustrating to spend more time with this daily error. What I need to do?

Thank you for your help.

Sylvain

[mollons]

For the error 1200 problem some customers find that if they open the file in Inventor and run rebuild all and then check back in it solves the problem.

For the refresh dialog, do you already have the file open when you try to do open from vault? Or do you have the file open as part of another assembly which is already open?

[Dan_Malott]

I have several files with the 1200 error that even when I check them out and rebuild they continue to have the 1200 error. 

[mthomas]

We too have several files that show the Error 1200 when attempting to assign items... in some cases (very few) an open and rebuild all will correct the problem, in some cases just leaving it and trying again in a day or two corrects the problem, but in many of the instances we are stuck and can not assign the item

...but it is good to know that we are not the only ones!

Mike

[Anonymous]

For the error 1200: The fact to check out/check in the file work, but sometimes not. Thanks all.

[Anonymous]

The second problem appears when I am in Inventor and I want to open a file with the function "Open from Vault". There are no file open in the same time.

[mollons]

Can you see other Inventor processes running in Task Manager that might be hanging around?

Also, I asked because the screenshot you attached showed a file open behind the error dialog.

[mollons]

Error 1200 is what the server throws back to the client when it doesn't know anything else to do.

For unsolvable error 1200s it is probably best to log a support ticket with product support so they can help you out.

[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

[mthomas]

Our solution was to upgrade to 2012, since that time we haven't had any 1200 errors assigning items. We've had other errors, just not the 1200.

[Raider_71]

Thanks. I see there is a load of people struggling with this same issue. I hope there is a solution soon as I can't believe that even after update 2 with another three or four hot fixes we still have so many issues with vault! The quality of the product is not good at all and is causing us serious downtime.
Moving to 2012 will not even be considered right now without even a service pack released yet. Since we have started using vault we have learned to wait for the product to mature before even touching it. Now with 2011 it's just worse.
This specific issue is getting worse and worse and getting to a point where we can't produce.
I hope there is a fix soon.
Thanks for the reply!

[mollons]

There are a couple suggestions in this thread fo things to try to see fi they fix the problem. Do any of them work for you? If so, that can help us track down the issue.

Also, as I mentioned earlier, it may be a good idea to open a support ticket with product suppor tin these cases.

[Raider_71]

We have tried the checkout rebuild and check-in method but its not really fixing all assy's for us. We are sitting with items we can’t update because of this and we can’t do so. We had a support ticket open with Autodesk and their suggestion was the same. We have now re-opened it to try and resolve it. They replied that we must run a query on the database in SQl management studio and this will produce a list of Inventor files we need to go through and check out, rebuild and check back in. We will run this query tomorrow but my gut feel is that this will produce an enormous list of files we will have to go through and will be a huge task! What about released items? We will have to first pull them back to WIP and then do all of this! Anyway the Case No is: 06679216
It’s just very frustrating to have these issues. We specifically wait for at least one or two updates of Vault and Inventor to be released before we migrate but that’s not even helping. Autodesk needs to stop focusing on new features and get their quality sorted because it’s costing us loads of money!

[Raider_71 · Accepted solution]

Hi guys if there are anyone still struggling with this issue here is a solution. It was given to us by Autodesk on a case number we opened with them through our subscription portal.

Thanks to Autodesk for sorting this out for us!

"Please log a case with Autodesk Product Support if you have this issue"

Edited by
Discussion_Admin

[herrerh]

The moderators have modified the above posting to remove the SQL code.  Although the SQL code may work to identify problem files for one instance of the 1200 error, others may not have the same results.

Please log a request with product support if yout get the 1200 error and the other suggestions in this posting do not work for you.  This will help us keep track of the issue.

-Hywell

[Anonymous]

We have run into Error 1200 before.

Old data that has not been migrated and users with bad practices can kill productivity!

Here is the process that I use to resolve the problem.

1. Make sure that the existing Items are rolled back to "Work in Progress"
  (you might have to roll back a bunch of affected assemblies... "where used" comes in handy)

  (look for presentation files too)

2. Part files need to be migrated (I use task scheduler).

3. I-properties must be filled in properly. (per your own vault environment)

4.Assemblies need to be migrated (I use task scheduler).

5. I-properties must be filled in properly. (per your own vault environment)

  (open up the assembly.idw, double click the parts list, select "save overrides to BOM") if needed

6. Save your files and check them back into the vault

7. Create the Items (try the assembly first and see if the parts go along for the ride).

8. Update the parts and assemblies to the current version

If you have a failure, try assigning items to the parts. (don't release them yet)

If you have library parts, you may need to use a different vault project file. (per your own vault environment)

Eric

[Anonymous]

For error 1200 first try a rebuild, all files that can be checked out need to be checked out when doing rebuild.

If the rebuild don't solve the issue the do the following. Run the following SQL query on your host server for Vault:

Edited by
Discussion_Admin

This will return files with issues. You can then see exactly which files have issues and check them out rebuild and save. Should solve your issue then.

Good luck.

[herrerh]

The moderators have modified the above posting to remove the SQL code.  Although the SQL code may work to identify problem files for one instance of the 1200 error, others may not have the same results.

Please log a request with product support if yout get the 1200 error and the other suggestions in this posting do not work for you.  This will help us keep track of the issue.

-Hywell

[Anonymous]

"I am not picking on Autodesk, I just need some help!"

I have run into this error again.

I was in the process of updating an Item in the Item Master

Cannot Create new items either.

 Closed down application

Restarted application

Tried to update Item again

 

I am logged into the Vault but it doesn't recognize me?                                      

I Went to back to the File and tried to assign Item.

Same message as before.

When submitted to Autodesk we ended up with a response like this:

"This is a very generic error message and although the error is the same in a lot of circumstances, the root cause can be different.

1. Check the files Custom iProperties for any anomalies;look for things such as very long parameters or duplicate parameters.
2. Try checking out the entire item, "rebuild all" to dirty ALL files then check them back in again."

I use the approved Autodesk processes and workflows as standard practice.

The next error was related to the associated DWF.

I think that the problem is much deeper than "file related"

What does "communication failure" mean?

I think most of my issues are related to the system that runs in the background.

Do workstations get amnesia?  not likely....  Can the MS-SQL system get messed up behind the scenes, how does that work anyway?  I have asked this question through Gold Support, provided "logs" and screen shots.  I hope to get an answer and some good feeback through the discussion group.

[Raider_71]

Are you still using Vault 2011? We had the same issue as you can see further up in the thread. Its all good now after updating and migrating files that were highlighted with a sql script provided by autodesk.
Vault 2012 aparantly is much better and not as prone to this type of issue now. 2012 update 1 has also been released.