AutoCAD MEP General Discussion

AutoCAD MEP General Discussion

Reply
Product Support
Joshua.Benoist
Posts: 518
Registered: ‎08-23-2006
Message 11 of 13 (272 Views)

Re: Invalid Enum Map String

04-17-2012 08:28 AM in reply to: luxy72462

<2013 IS A FILE FORMAT RELEASE>

 

This news needs to be spread around more.  Every 4th release historically has been a file format release and 2013 is no different.  That means that 2010 was a file format release.  And 2011 and 2012 were on the 2010 file format.  2011 and 2012 are backwards compatible with 2010.  You can save and open between any of those 3 releases, since they are on the same format.  2013 is the start of a new format.  Files saved in 2013 and then saved back to an earlier format cannot be edited in the prior format.  They become proxy objects.  You can Export to AutoCAD and then edit them as Core AutoCAD objects in an earlier release.

 

HTH,

Joshua



Joshua Benoist, PE
Senior Support Specialist
Product Support
Autodesk, Inc.

*Expert Elite*
Keith.Brown
Posts: 1,236
Registered: ‎03-13-2008
Message 12 of 13 (267 Views)

Re: Invalid Enum Map String

04-17-2012 11:00 AM in reply to: Joshua.Benoist

I have "messed" up my catalogs in the past and had to copy the catalog from a new installation.  You will of course have to regen the catalog to add any new parts that might have been created after the initial installation on the original machine.  This would be a last resort in my opinion but it definately works.  Just copy your original catalog to a safe place so you can copy over any custom fittings if need be.


Keith Brown AutoCAD MEP BLOG | RSS Feed
AutoCAD MEP 2014 | Revit 2014 | EastCoast CAD/CAM V6.1 | Visual Studio 2013
────────────────────────────────────
⁞|⁞ Please use Mark Solutions!.Accept as Solution and Give Kudos!Give Kudos as appropriate. Thank you!
Active Member
Mikanikal
Posts: 6
Registered: ‎10-11-2010
Message 13 of 13 (247 Views)

Re: Invalid Enum Map String

04-25-2012 01:17 PM in reply to: Keith.Brown

This error message is because any MvPart built using 2012 or 2013 Content builder adds an IFCTC key to the .xml file for that part. The 2010 and 2011 see this and throw the error because it doesnt know what that is. If you get your apc file back up and running and are able to regenerate your catalogs, you can run that catalog check and find the parts with the problem or if you can remember which ones you might have opened/edited/created in 2012, then just go those parts, open the .xml files, remove the IFCTC key and save the .xml.

 

I build all my MvParts using 2011 so that this IFCTC line is not created and they work in all versions. This prevents the guys using 2011 and 2010 from receiving that error when i send them Equipment.

Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Need installation help?

Start with some of our most frequented solutions to get help installing your software.

New AutoCAD MEP Category!

The AutoCAD MEP forum has moved into it's very own category page, and can no longer be found within the Additional Product Forums.

Announcements
Do you have 60 seconds to spare? The Autodesk Community Team is revamping our site ranking system and we want your feedback! Please click here to launch the 5 question survey. As always your input is greatly appreciated.