CAD import fails in recipe management when uploading STEP files, error: 'Invalid file type for import'

PLM Windchill
, , , , , , ,
1

We’re experiencing a blocking issue when trying to upload STEP files (.stp) to recipe management in Windchill 11.1 M030. The import process fails immediately with an ‘invalid file type’ error, even though STEP is supposedly supported.

I’ve verified the import configuration settings in the recipe management preferences, and STEP format appears to be enabled. The file mapping seems correct based on the documentation. We’ve tried restarting the method server multiple times, but the issue persists.

Error snippet from the logs:


ERROR: File type validation failed
wt.recipe.RecipeImportException: Invalid file type .stp
at RecipeImporter.validateFileType(line 234)

This is blocking our entire recipe creation workflow since we need to import geometry from our CAD system. Has anyone encountered this and found a solution?

2

Here’s the complete solution addressing all three areas - import configuration, file mapping, and method server setup:

1. Import Configuration Settings: Create a custom xconf file at WT_HOME/codebase/ext/yourcompany/conf/RecipeFileTypeOverride.xml:

<Property name="recipe.allowed.extensions" value=".stp,.step,.prt,.asm"/>
<Property name="recipe.step.mimetype" value="application/step"/>

Register it in your site.xconf and run xconfmanager:


xconfmanager -p

2. STEP File Mapping: Verify your CAD adapter configuration includes STEP translation. In cad.properties:


cad.recipe.import.step.enabled=true
cad.recipe.import.step.translator=StepImporter

Ensure the MIME type is registered in Windchill’s content type registry. Navigate to Site > Utilities > Content Type Management and verify that application/step is mapped to .stp and .step extensions. If missing, add it through the UI or via LoadFromFile utility.

3. Method Server Restart: After configuration changes:

  • Stop method server: `windchill stop MethodServer
  • Clear server cache: `windchill ext.recipe.clearCache
  • Start method server: `windchill start MethodServer
  • Verify logs show new file type registration

Additional Critical Step: The RecipeImporter class caches allowed file types at startup. You may need to clear the JVM cache or force a full method server restart (not just stop/start but actual process kill and restart) to ensure the validator picks up the new configuration.

After these changes, your STEP file imports should work. Test with a small STEP file first to verify the geometry processes correctly before attempting large assemblies. If you still see issues, check the recipe worker logs for CAD adapter errors - that would indicate a separate geometry translation problem beyond file type validation.

3

Create a custom xconf override rather than modifying the base file - that way your changes survive upgrades. Place it in WT_HOME/codebase/ext/yourcompany/conf and make sure it’s properly registered in your site.xconf. After xconfmanager runs and you restart the method server, the new file types should be recognized. The validation happens server-side so method server restart is sufficient.

4

Thanks for the suggestions. I checked the xconf files and found a RecipeFileTypeValidator.xml that only lists a limited set of formats. STEP wasn’t included. Is it safe to modify this directly, or should I create an override in a custom xconf? Also, after making changes, do I need to restart just the method server or the entire Windchill instance?