Start a conversation

MicroSurvey CAD 2021 Known Issues

The following is a list of critical bugs or important limitations that users should be aware of which affect MicroSurvey CAD 2021. It is not intended as an exhaustive list of all issues.

Important Note: If you ever experience a crash when using MicroSurvey CAD, when you are asked if you would like to send an error report, please always select Yes to send the report. MicroSurvey and IntelliCAD programmers can use these error reports to help investigate and fix crashing problems that occur within the program, even if it is a problem that is not easily reproducible. Please note the crash reports are not actively monitored for technical support purposes.

Please contact technical support if you experience any problems.

Reported: July 7, 2021

Problem: Entering a Network Floating License results in "There was a Problem Activating the License"

Solution: This was resolved by releasing a new installation to take the place of the June 2021 release, and the June 2021 release was removed from the downloads page. Please check Help | About MicroSurvey CAD. If your installation Date is June 2021 please uninstall and reinstall with using the July 7 release.

Reported: Sept 02, 2021

Problem: reactors don't start if you run a command too quickly in a new drawing

Workaround: Wait for the new drawing is completely started and the command line stops loading commands before type in any command in the command bar. 

Status: Will be fixed in a future update.

Reported: July 30, 2021

Problem: Transfer Between Drawings does not work.  Error Message: _ms_start_transferError while extracting file (File Name).msj\ch.dat 

_Error opening coordinate database: 70

Workaround: This problem only occurs when drawings are opened using the Start Page or the File | Open menu.  If you open the drawing using Project Manager the function works properly.

Status: Will be fixed in a future update.

Reported: July 15, 2021

Problem: Opening MSCAD prompts error Message: the code execution cannot proceed because MSVCP110.dll was not found, Reinstalling the program may fix this problem

Workaround: This problem is related to the windows 10 update KB5004237 associated with Visual C++, install the redistributable file will fix it.

Status: Will be fixed in a future update.

Reported: October 28, 2020

Problem: When exporting from an imperial (International Feet or US Survey Feet) project to shapefile, the projection file is written as metric.  This units mismatch is not accepted by some GIS programs, such as Google Earth or QGIS, wherein the projection file units are used to assume the units for the entire shapefile, making the shapefile appear to have incorrect units.

Workaround: The .prj (projection) file is an optional file in the shapefile.  In imperial projects, uncheck the checkbox to write projection data and import the shapefile into a GIS project that has had the coordinate system manually set.  The remainder of the shapefile data is correctly written in the appropriate imperial units.

If you must have a .prj file as part of the shapefile, you can modify the exported shapefile in a text editor manually, converting the projection units and noting the units and conversion factor in the file, as described in the following online article from ESRI:  Most projection details are available online at or, so you may be able to simply input the projection details as written there, ensuring units and conversion factor to metric are noted as described in the ESRI article.

Status: Partially fixed in MicroSurvey CAD 2021 Hotfix.  Coordinate systems with units matching project units will now be exported as expected.  Will fully fix in a future update.

Reported: October 27, 2020

Problem: Selecting closed, splined polylines for shapefile export will cause the program to crash.

Workaround: Change the "Closed" property of splined polylines to "No" prior to exporting.

Status: Will be fixed in a future update.

Reported: September 16, 2020

Problem: Smooth Contour causes an extra segment to be drawn from 0,0 to the first vertex of all smoothed contour polylines.

Workaround: The easiest method is to use MicroSurvey CAD 2020 SP2 or earlier to smooth any contours.  You may instead explode contours, delete erroneous segments, and join them en masse, but this is potentially a very long operation as the contours have been smoothed and contain many segments.

Here is a video going over the workaround.

Status: Fixed in Microsurvey CAD 2022 (v22.0.2), released December 2021.

Reported: November 6, 2020

Problem: BIM Undlerlay import does not work, and crashes the program during the import process.

Workaround: The current workaround is to use MicroSurvey CAD 2020 SP2 to import any necessary BIM files.

Status: Fixed in MicroSurvey CAD 2021 SP1, released February 17, 2021.

Reported: November 10, 2020

Problem: Some computers will always have a message when trying to install saying that it requires admin rights to install. We've found that this is caused by an issue with the installer of the program.

Workaround: Some computers are able to solve this issue by turning of your Antivirus and/or Windows Real Time Protection. We recommend disconnecting from the internet before trying this.

Status: Fixed in MicroSurvey CAD 2021 Hotfix, released December 22, 2020.

Reported: June 2, 2021

Problem: Surface volumes may be reported incorrectly at high coordinate values, such as UTM.

Workaround: Use MicroSurvey CAD 2020 SP2 or earlier, or MicroSurvey CAD 2021 SP2.

Status: Fixed in MicroSurvey CAD 2021 SP2, released July 7, 2021.

Reported: February 25, 2021

Problem: Arc Labels placed by MS_MAN_CURVE_LABEL_ON_ARC are incorrect if the arc has been trimmed by the AutoMap.

Workaround: Use wipeouts in your blocks to hide lines behind symbols, rather than trimming linework.

Status: Fixed in MicroSurvey CAD 2021 SP2, released July 7, 2021.

Reported: October 9, 2020

Problem: When inserting some blocks using insert command or Automap, an error "Duplicate Record name" is displayed and insertion fails.

Workaround: The issue is caused by the *IPN_INTERNAL layer which MSCAD always creates in order to display IPNs.  In some cases, when the block has the layer (which is normal with MSCAD) this issue arises.  If you have a non-MicroSurvey CAD program you can remove the *IPN_INTERNAL layer from the block, purge the destination drawing, and then reinsert.  1. Open the block in MSCAD.  2. _WBLOCK.  3. Configure the output path and file name.  4. Set insertion units to "undefined"  5. Select all visible elements of the block and select "OK."  This will create a new version of the block without the *IPN_INTERNAL layer.  Replace your old version of the block with this one. 

Status: Will be fixed in a future update.

Choose files or drag and drop files
Was this article helpful?
  1. Jeran Hopfe

  2. Posted
  3. Updated