SolidWorks → STEP
Theme
CadExchange / Blog / SLDASM to STEP

SLDASM to STEP: Fix Missing Parts, Broken References, and Assembly Export Failures

A troubleshooting checklist for assembly conversions that fail because parts are missing, paths changed, or the upload bundle is incomplete.

SLDASM to STEP 2026-02-25 6 min read

A failed SLDASM to STEP conversion usually does not mean the assembly is corrupt. More often, the converter cannot resolve one or more referenced components because the upload package is incomplete or reorganized.

This page is a practical checklist you can use before requeueing the job. Fixing the bundle first saves time and avoids repeated failures.

Common Symptoms of Assembly Conversion Problems

  • The conversion fails immediately after queueing.
  • The exported STEP file is missing parts or subassemblies.
  • The assembly opens partially in the target system.
  • Retries keep failing with the same error message.

Root Cause #1: Missing Referenced Files

A SolidWorks assembly file points to other files. If you upload only the top-level .sldasm, the converter may not have access to the parts and subassemblies it needs to build the final STEP export.

The fix is simple: create a ZIP that includes the entire assembly bundle, not just the assembly file. Keep the original directory layout so references resolve the same way they do in your source project.

Root Cause #2: Folder Structure Changed Inside the ZIP

Even when every file is present, conversions can fail if the relative paths changed. Example: moving all parts into one folder after they were originally nested in multiple folders.

Best practice: ZIP the folder tree as-is from the source project instead of manually collecting individual files.

SLDASM to STEP Recovery Workflow

  1. Start from the original assembly project folder.
  2. Confirm the top-level .sldasm opens correctly in your own environment (if available).
  3. Create a fresh ZIP of the full folder tree.
  4. Upload the ZIP and run the conversion again at the converter.
  5. If the failure was transient, requeue once. If the error repeats, inspect the package again.

When Requeueing Helps (and When It Does Not)

Requeueing helps when the failure was caused by temporary issues such as worker availability, queue delays, or infrastructure hiccups. It does not fix missing parts, renamed files, or broken assembly references.

If you operate the site, the admin jobs console can bulk requeue failed jobs from the last 7 days after an outage. Use a class filter (for example, conversion jobs only) to avoid requeueing unrelated failed background jobs.

Related Reading

For the general upload workflow, read How to convert SolidWorks to STEP. If you are automating high-volume conversions, see API automation patterns.

The FAQ also covers assembly bundles and requeue basics for end users.

FAQ
Quick answers for common search intent around this topic.

Do I need to include every part file for an assembly conversion?

Yes. Include the .sldasm and all referenced .sldprt files (and subassemblies) in the same ZIP bundle with the same relative paths.

Should I requeue a failed conversion after fixing the ZIP?

Yes. Upload a corrected bundle or requeue after confirming the source package is complete. Admins can also manually requeue failed jobs from the jobs console.

Next Steps
Turn this topic into product-qualified traffic.
Related Articles
More long-tail pages around CAD exchange and conversion workflows.