Civil3d 2025.1: The program crashes when an XRef is detached. (Internal error)

[cwr001]

Hello,

me and my colleagues just experienced a very disturbing behaviour. We are working with Civil3d 2025.1.

When we open a new out-of-the-box template (it happens regardless of which template is used, it's just to demonstrate that it's not connected to a faulty template), overlay an XRef (again, it doesn't matter which one, it happens with every file) and detach this XRef again, the software crashes.

The error message reads as follows: "Internal error: !xfile.cpp@11624: eWasOpenForWrite".

Does anyone have an idea what's going on? This can't be the fault of the core product, right? The only extension that is installed is the german country kit - could that be the culprit? It happened on different machines. Civil3d 2023 and 2024 work normally.

[ianjchap]

Hi, 

Do you get the same in either the 2025 Metric or Imperial OOTB Civil 3D sessions?

[cwr001]

We work in metric but it also happens when working in an imperial session.

[cwr001 · Accepted solution]

Autodesk confirmed the bug - it's caused by the country kit.

They are working on a fix so at the moment, I'd advise against using the german country kit.

[ianjchap]

Great to hear you have an answer at least. 
Out of interest, did they pickup the issue through this forum or a separate channel directly?

[cwr001]

In my support ticket they wrote that they are aware of the problem and are already working on a fix.

Which makes me quite mad and I hate everything about the way stuff like this is handled.

If they are unaware of it that's fine but I've just spend a couple of hours deinstalling and reinstalling Civil3d on different machines to make sure that the crashes are not caused by something on our side.

There's a Country Kit-Thread on this forum where, e.g. @lim.wendy could post known issues like this, if she'd be properly informed. They could place a warning sign in the download section of manage.autodesk.com or send E-Mails to users who installed the country kit.

To quietly hope that things will just fizzle out is frustrating (then again, you'd expect nothing else from Autodesk...).