hi, would you please give some other infomation to figure this out, such as:
- Did this error appear on the Vault client main window or other dialog? what operation made this error thrown?
- Did this error appear when login another Vault database in the same machine?
Thanks,
Fay
Hello Mr. Yuhui,
Thanks for your interesting. The environment is VM2010 SP1 with a SAP connector.
I have some items that when I click on (in item master environment) a dialog box appears with this message.
I have noticed that when I "delete SAP link" (for file and item) the dialog box does not appear.
If I do an "Update Item" (it is done without problems) and click on, the dialog box appears again.
Thanks
Please, I need help.
I hear about an aplication that can find the problem I'm talking about, but with older vault versions.
Maybe with a simple consultant to a SQL, the problem is solved.
How much it costttttt?????????????????
regards
Have you tried logging a support case against this issue? I, unfortunately, cannot add anything since it is something I haven't seen. But, I think we might be able to help you quicker if you went thru support.
-Jim
Are you using Autocad Mechanical with Vault Manufacturing?? We have had the same problem with a new vault set up, the previous had no issues - eventually we were told
"We only have a very few reports of this error occurring before. ... when they created an Item property. When the property was deleted, the error went away. I am wondering if they have recently created a new custom Item property or imported a configuration that has the same name as a property in the ACM BOM Table. The issue being that the custom Item property in 2010 should not have the same name as that in the ACM BOM table."
The issue is why there is no guidance on avoiding such problems in the first place
Goog evening Mr. Cadenza,
Well, people are using AutoCAD Mechanical with VM2010, but not are using the AM BOMS.
May is occurring what you say with Inventor too.
Through a friend, it has been opened an official support, I tell you something.
Regards
I too see this error message at random. I am using Vault 2010. It usually happens when I right-click on an Inventor file in Vault Explorer.
Is everyone who is seeing this error in this thread using Vault Connect?
Again if you are referring to the SAP connector then we are NOT.
A new clue discovered in rthe last hour - the error only appears when selecting the problematic items in item master when the "general" tab is selected ie if the history or Bill of materials is selected the error dialogue does not pop up!!
Could someone send me a screen cap of one of the problematic item's general tabs?
You can send it directly to me if you woudl rather not post it here.
scott dot mollon at autodesk dot com
I am be able to solve it by creating again the 3D model (not copy), but we have around 50 items affected and the drawing must be acoted again.
crazy
I have done some digging and found some information ...
The root cause of this issue is that properties are conflicting because of what appear to the Vault to be duplicate properties. This can happen by creating a Custom property on the file which has the same name as any other property in the file or in the bom in the file. We had seen this with dwg files, but I had not seen any indication that we saw this happening with Inventor files. It may happen with Inventor dwg files though.
For instance, if you had a BOM property named "Note" and a custom file property named "Note", Vault was getting property information from two sources and colliding.
This issue was fixed in Vault Professional 2011, because it also required fixes from outside the Vault development team to the ACAD .dwg side of property and bom handling. In Vault 2011, the assembly or BOM property will always be used if there is a collision from duplicate properties.
One thing to do is to take a look at the properties you are using on the items and their mappings, and compare to the properties in the CAD bom and file or custom file properties. If you have different properties in different locations with the same name it is probably the cause of this error. Renaming/remapping the duplicate property should fix this issue.
You might want to try installing ACADM 2010 Update 2 (if you haven't already) as it looks like it has some Vault specific fixes in it, but I am not sure if it will help.
Hi Mr. Mollon,
It is difficult to belive in it, because if I create a new IPT with the same properties, it runs well.
One more, there is only some items affected (random).
Are you telling us to migrate to V2011????????
Regards