Corridor no longer processing, "object reference not set to an instance of an object"

Hello,

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.

Thanks,

Riley Parks

Parents
  • Had an issue like this in the past and I detailed some of my findings.

    • Corridor Not Processing
      • Background
        • When creating a corridor, it must be created along a Complex Element that has an Active Profile.
        • Many times, there isn't actual a proposed profile required on the CL of the roadway, such as:
          • Milling and resurfacing jobs where you need to show outside EOP profiles projected back to the CL,
          • Proposed divided roadways where the PGL elevations are projected back to the CL.
        • In this cases, those profiles do not need to be activated because there would be more than one.
        • In these instances, just set the Existing Ground as the active profile so you know you will have an active profile for the entire length of the CL.
      • Issues
        • No Active Profile on Corridor Alignment
          • Sometimes, when working on these profiles, you can accidently set the Active Profile to one of the proposed profiles.
          • In my case, this is what I did, then I deactivated that proposed profile, but never reactivated the Existing Ground.
          • So now there was no Active Profile at all.
          • This will cause the corridor to not process until an Active Profile has been assigned to the Complex Element the corridor is based upon.
        • Red Reference Files
          • When creating the corridor, it may have been created by ruling one of the limits of the template drop to a particular line in a reference file.
          • If this file or model is removed or renamed, the reference will appear red because Microstation cannot find the file any longer.
            • This also means it cannot access the rule that was created.
          • Fix the reference by double clicking and either selecting the appropriate model or hit Browse and select the new renamed file.
          • Once this is done, the corridor should be able to process.

    Zachary Billings, P.E.

    Senior Roadway Engineer (Licensed in FL and MI)

    CONSOR Engineers, LLC

    System Info:

    Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 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

  • Zach,

    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.

Reply
  • Zach,

    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.

Children
  • 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

    • Corridor Reattach
      • You can use this when you need to move a corridor to a new alignment
        • Or you can use it when you need to move the corridor back to the correct alignment if someone messed up a reference file.
      • It's important to make sure the new alignment has somewhat the same stationing as the old alignment if you want all your external references and point controls to work.
      • https://www.youtube.com/watch?v=Gdo5NCOX8UY
        • You need to use Key-In for this as I don't believe there is a button yet.
          • Key-In "corridor reattach" and hit enter
          • Select the corridor to move
          • Select the new alignment for the corridor
          • Reset (right-click) to accept the active profile.

    Zachary Billings, P.E.

    Senior Roadway Engineer (Licensed in FL and MI)

    CONSOR Engineers, LLC

    System Info:

    Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 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

  • Zach,

    The order of events was as follows:

    1. Corridor and Template creation on original alignment "CL" which had the CL Const feature definition in COGO
    2. Add parametric and point controls
    3. Alignment was overwritten under the same name with no feature definition. Same stationing was used.
    4. Reimport profiles for point controls (Original CL Const alignment -> Extended no feature alignment)
    5. Corridor does not process and shows the error whenever an edit is attempted.

    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!

    Riley