Skip to Content
SuCri® Knowledge Base 8. Tools 8.2. Module 1 8.2.3. Error message: "ImportError: DLL load failed"

8.2.3. Error message: "ImportError: DLL load failed"

Updated on 27/08/2026

On this page

    In this article, you will learn how to resolve the "ImportError: DLL load failed" error in AutoCAD Plant 3D. This message frequently occurs when file paths for scripts exceed the character length permitted by Windows.

    Prerequisites

    • You have administrative rights on your local machine to move file paths or adjust directories.
    • Plant 3D is closed to avoid conflicts when moving files.

    Step-by-Step Instructions

    1. Identify the path that is too long: Check if your CustomScripts are located in deeply nested directories, such as in OneDrive: c:\users\username\onedrive\documents - detail engineering plant 3d\autocad plant 3d 2024 content\cpak common\customscripts\...
    2. Move the directory structure: Move the CustomScripts folder to a local directory with a short path structure, for example: C:\P3DContent\CustomScripts

      Result: Use of a shorter path significantly reduces the length, bypassing the Windows restriction (MAX_PATH).

    3. Adjust the Content path in Plant 3D: Open the Project Setup or the Content Path Settings in Plant 3D and point to the new, shortened directory.
    4. Run the registration command again: Enter PLANTREGISTERCUSTOMSCRIPTS in the Plant 3D command line again.

      Result: The scripts should now load without an error message.

    Important Notes

    • Avoid OneDrive: Avoid storing content folders in synchronized cloud directories, as these often create extremely long default paths due to the Windows folder hierarchy.
    • Flat Hierarchy: Always use short and flat directory paths (e.g., directly under C:\) for your Plant 3D content.
    • Unified Standard: Define a uniform local path (e.g., C:\P3DContent) for all project participants to avoid compilation errors within the team.

    Troubleshooting

    • Error despite short path: If the error persists, experts can enable the Windows setting for long paths (>260 characters) via group policy or the registry. However, this is only recommended if the IT infrastructure supports it; shortening the paths is the safer method.

    Still a question open?

    Write to us, we answer within 24 hours on business days.

    Request a consultation