Microsoft .NET Framework Error

Good morning,

I am trying to runt he Import Geometry tool and as soon as I click it, my laptop dock seems like it flickers off/on. Enough to make my screens go black and then it starts making the sounds like thing got unplugged and then plugged back in. Once the screens come back up and I select the .ALG file I wish to import, I get a Microsoft .NET Framework error indicating Illegal characters in path. I have copied the details of the error to the text file attached. I am able to click continue to move along with the import. When I click the feature definition drop-down, I get another error (same illegal characters error). It won't let me select a feature definition here, so I just import without one and seems to import ok. Once it is imported, the alignment does have the feature definition assigned though.

Any ideas on what would be causing the .NET issue?

Thanks,

Ken


ORD Error.txt

Parents
  • What happens if you put the alg file in a folder that has a very simple path? Something like C:\temp and make sure the filename is a legal 8.3 filename. Although not the same error, we have had occasional issues where a legal file or folder name conflicts with some code due to a non alphanumeric character, even though it is considered allowable by the OS.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Reply
  • What happens if you put the alg file in a folder that has a very simple path? Something like C:\temp and make sure the filename is a legal 8.3 filename. Although not the same error, we have had occasional issues where a legal file or folder name conflicts with some code due to a non alphanumeric character, even though it is considered allowable by the OS.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Children
  • I tried what you mentioned (move the file to C:/temp and rename to 12345A.alg) and it still came up with the same error. I then tried to open that same DGN file without a workspace and import that same simple .ALG file, and the same error came up. Lastly, I moved and renamed the DGN itself following the same rules and once again I got the error. There may be something other at play aside from a Bentley issue and may be my computer in general. I will reach out to IT and have them look through the error and see what they can find as well.

  • It's worth checking to see if there was an operating system update done recently. Occasionally those can affect .NET delivered files. I haven't seen anything here about known issues, but I've also seen stranger things.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2