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