I am working on updating our corridor for a project and in the process, I have started receiving the error in question, shown below.
This is occurring whenever I try to reprocess the corridor and no changes are actually made. I've tried changing the template drop frequency, removing corridor references, changing the Design Stage and none of these actually stick and still produce the same error. I have tried restoring to a previous version of the file and the error still occurs. Occasionally, it will start processing stations but doesn't actually make any progress and I am still free to manipulate the file (draw lines, attach references, etc.) which is not normally the case. I have had coworkers try on their machines and it results in the same error. Trying to apply a corridor and template in another file altogether still works however.
I have resolved to remaking the corridor but I was hoping someone might have some insight on what cause the issue so that an error like this can be prevented in the future.
Had an issue like this in the past and I detailed some of my findings.
Zachary Billings, P.E.
Senior Roadway Engineer (Licensed in FL and MI)
CONSOR Engineers, LLC
Windows 11 | Intel Core i7-13700k | Nvidia RTX 3080 FTW3 Ultra | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME
ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00
YouTube Page for ORD: https://tinyurl.com/BillingsCADD
I am unfortunately still encountering the error. Speaking with a coworker, we remembered that the alignment of the roadway was extended and under the same name in our gpk, "CL". When I was trying to reimport one of my point control profiles, I believe that's where the problem arose. I am now trying to fix the corridor by replacing the reference alignment to an older alignment that should have the same original active profile limits, but haven't had success with it yet.
The gpk isnt going to have anything to do with it. Did you extend the original Civil Element for your CL, or did you delete that element and reload a new one in from your gpk? If you did the latter, that is probably going to be your problem. Even though it has the same name, your corridor is seeing that new alignment as a completely new element.
What you need to do is Corridor Reattach. Check out below
The order of events was as follows:
I was hopeful that would work, but it's still throwing that error. I really appreciate all your suggestions and willingness to help, thank you!