CODEWITHSUNDEEP
autocadautodesk-designautomation
thanh trang Nguyen
thanh trang Nguyen

Reputation: 36

FATAL ERROR: Unhandled e06d7363h Exception when Importing Surfaces in Civil 3D Design Automation

I am encountering a critical issue while running a script on Civil 3D Design Automation. The error appears during the process of importing surfaces. Below is the detailed log output:

[01/06/2025 01:10:01] Execute .......................:
[01/06/2025 01:10:01] Loading AeccLandXmlCmd in ACES instance...
[01/06/2025 01:10:01] Loading AECC Base Core...
[01/06/2025 01:10:01] Loading AECC LandXmlCmd...
[01/06/2025 01:10:04] .AeccLandXmlInNoDialog Import LandXML <Enter File Name>:C:\DARoot\Jobs\66d17d1d191e4d69a401a81b433f35e3\input.xml Converting Meters (LandXML units) to Imperial feet (DWG units)
[01/06/2025 01:10:04] Importing Surfaces ...
[01/06/2025 01:10:23] ERROR.Message :
[01/06/2025 01:10:23] External component has thrown an exception.
[01/06/2025 01:10:23] ERROR.StackTrace :
[01/06/2025 01:10:23]    at acedCmdS(resbuf* , Boolean , AcApDocument* )
[01/06/2025 01:10:23]    at Autodesk.AutoCAD.EditorInput.Editor.Command(Object[] parameter)
[01/06/2025 01:10:23]    at LandxmlConverter.Commands.LANDXMLCONVERTER()
[01/06/2025 01:11:24] Error: AutoCAD Core Console is shut down due to timeout.
[01/06/2025 01:11:24] End script phase.
[01/06/2025 01:11:25] Error: An unexpected error happened during phase CoreEngineExecution of job.
[01/06/2025 01:11:25] Job finished with result FailedExecution
[01/06/2025 01:11:25] Job Status:

After researching, it seems this error is related to a system-level issue. However, since this is running on Design Automation, I don't have direct access to the underlying system to debug or fix it. I would appreciate any help or pointers to troubleshoot this problem.

Updated on 2025/01/06(with additional information about the Design Automation script): I am using this command:

edf.Command(".AeccLandXmlInNoDialog", sFileName);

The script I use is basically similar to the script I mentioned here (link). Small LandXML input files work successfully, but some files that are tens of megabytes fail, and the Design Automation output is as mentioned above.

Running the code with accoreconsole.exe locally or directly importing through the Civil 3D local software both work perfectly with the same file. enter image description hereIt seems to be an issue with the Civil Design Automation beta. (Tested local version: 2022, Design Automation: Autodesk.AutoCAD+24_1)

Upvotes: -2

Views: 165

Answers (1)

Stephen C
Stephen C

Reputation: 718788

According to this link:

"This is caused due to file corruption and missing updates of AutoCAD.

Solution:

You said:

Sorry, I cannot provide the file as it belongs to the customer.

You may need to work with your customer to address the above.

Upvotes: 0

Related Questions