Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Part Family Error

Status
Not open for further replies.

Boarderline

Mechanical
Joined
Jun 25, 2010
Messages
4
Location
US

In the past 3 weeks our company has upgraded to NX6 and TC8. For some reason when trynig to do a part family we get a "Runtime-error '-2147417851 (80010105)': Method 'buttonClicked of object 'IXLMenuEvent' failed" , but it only happens some parts. I have given a part a new number and obsoleted the old part number, did a save as on the old part number to the new on the dataset, and the old number gives me a run time error and the new number shows no problems. I was wondering if anyone else has encountered this problem. I have treid to run it in my normal Group and role as well as changing to the Administrative group and role with no luck.

Software:
Win XP Pro x64 Edition
Microsoft Office 2007
NX 6.0.5.3
TC 8 (20100419.00)

Any info on someone may have on this would be great.

-------------------------------------------------
Daniel Mc
Mtd Southwest
Designer III
Tempe, Az
 

Also if it isn't the runtime error "Method 'buttonClicked of object 'IXLMenuEvent'" it is given the run time error "Automation error The server threw an exception"

------------------------------------
Daniel Mc
MTD Southwest
Designer III
Tempe, Az
 
Try copying ug.xla file from folder c:\apps\ugnx\UGII\... to the ADDINS folder of your microsoft office installation path. something like c:\program files\microsoft office\office12\Addins\...

Sometimes it solves the problem, sometimes it doesn't.

Best regards,

Michäël.

NX4.0.4.2 MP10 / TCE 9.1.3.8_build_0711 / NX6.0.2.8 / NX7.0.0.9

Belgium
 
Looks like we have come up with an answer to our run time error problem. We had to do 2 things to get the run time error to stop. One was we deleted the part family and recreated the table. That only made it work about 50% of the time. The second thing was, it looked like bad data was connected to the item revision and we had to delete the item revision also. So with the recreate of the part family table and item revision we have had 100% success out of the 5 or 6 part families that we have run that were not working.

------------------------------------
Daniel Mc
MTD Southwest
Designer III
Tempe, Az
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top