8.2.1. Error message: "Can't find symbol for specified part"

8.2.1. Error message: „Can’t find symbol for specified part“

Learn how to solve the error message "Can't find symbol for specified part" in Plant 3D. A correct configuration of the paths and scripts is essential for the error-free placement of components.

Prerequisites

• You use Autodesk AutoCAD Plant 3D.
• The SuCri extension is installed.
• You have an active license for component placement.

Step-by-step guide

1. Check content paths

   Make sure that all relevant catalogue and support data are located in the correct content folder. Compare the path stored in SuCri with your current project path.

   

   Result: The content (support catalogues, symbols, scripts) can be found again by the software.
2. Check and copy CustomScripts

   Copy all necessary scripts manually into the CustomScripts folder if they are missing there. When in doubt, use the original scripts from the SuCri installation.

3. Register scripts in Plant 3D

   In the command line of Plant 3D, enter the command PlantRegisterCustomScripts and confirm with Enter. This officially registers the scripts for the current installation.

4. Check license status

   Check whether your SuCri license is active and still valid. Note that with expired trial versions no new components can be placed.

Important notes

• Avoid multiple installations: If several Plant 3D or SuCri versions are installed in parallel, conflicts with the script paths can occur. Consolidate your system to a single, uniform version.
• Clean uninstallation: Remnants of old versions often cause incorrect paths to be referenced. In case of persistent problems, carry out a complete reinstallation.
• Best practice: In case of error messages, always check the content paths first and run the registration command.

Troubleshooting

• Problem: Components cannot be placed despite correct paths.
  Solution: Check whether a license is active; already placed components are retained even without a license, which can be misleading about the status.
• Problem: Scripts are not recognised.
  Solution: Run PlantRegisterCustomScripts again and make sure that no remnants of a faulty uninstallation remain in the CustomScripts path.