System Fault 20301

I am opening this post to prompt our User Community to post issues here and begin a Community Discussion on the causes and possible fixes or workarounds for the reported Error Message as shown in the image below.

 

If you have seen or experienced this Error Message, please indicate the steps you took just prior to seeing this message (in other words what procedure, process and/or tool you were using) and let us know if it can be reproduced. We may need to ask for files to test to try to resolve the issue.

Please don’t post any other issues to this discussion thread. Only post comments in relation to the Error Message displayed. If you have experienced another error message we encourage you to use the search function to locate a discussion thread on the FDOT CADD Support Forum/Communities Site related to your specific error message. If one does not exist, please Join Bentley Communities and begin a new discussion thread on the FDOT CADD Support Forum/Communities Site.

Parents
  • System Fault: 20301 error:

     

    I think we’re a little closer to knowing the cause of the System Fault: 20301 error.

     

    This Error also may be related to 2 other errors we come across:

     

    System Fault: bad memory access

    Exception has been thrown by the target of an invocation

     

    In the example presented, the System Fault: 20301 error seems to be due to a CadInputQueue.SendCommand "Save Design"Command initiated in our LoadVBA.mvba necessary for our Drainage Platform to function correctly coupled with the Microstation Preference setting Automatically Save Design Changes. In the FDOTSS4 workspace, we use a LoadVBA.mvba to set settings and perform certain functions when opening a Microstation session. The settings, functions and application initiation are necessary for our FDOTSS4 workspace to function correctly for our many disciplines.

     

    In the case where DWG's will be edited in a Microstation Session in our FDOTSS4 workspace try the following:

     

    1. Comment out the following from the configuration in the SiteFdot.txt file (in red):

       

      %if !defined (_CONSOLEAPP)

        MS_DGNAPPS > $(_USTN_SITE)menu/Program/ustn0811/cadpilot.ui.ma

       MS_DGNAPPS < ustnqcinspector

       MS_DGNAPPS > FDOT.LDM

        MS_DGNAPPS > $(_USTN_SITE)apps/SyncXS/SyncXS.dll

        #MS_VBAAUTOLOADPROJECTS > $(_ustn_site)vba/LoadVBA.mvba

      %endif

       

    2. Navigate to the Microstation Menubar > Workspace > Preferences… > Operation > Set Operational Preferences > toggle off the Automatically Save Design Changes.

       

      Note: You will have to manually save your files.

     

    This will stop the initial System Fault: 20301 error, but will affect your FDOTSS4 workspace.

     

     

    Subsequent file switching Crash with the “Save Design” and Automatically Save Design Changes:

     

    There is another issue which I believe is related to the System Fault: 20301 error. This issue is caused by having a DGN file referenced to a DWG file with the “Save Design” and Automatically Save Design Changes on.

     

    This issue produces the following errors when switching from DWG to DWG with Automatically Save Design Changes toggled on and the Loadvba.mvba not commented out in the Sitefdot.txt file:

     

    System Fault: bad memory access

    Exception has been thrown by the target of an invocation

     

    Generally, having a DWG file referenced to a DGN is opposite of our current recommended workflow involving utilization of DWG’s in a Microstation session. If DWG’s are needed for some detail work within a project we recommend referencing the DWG to a DGN and Merging to Master the needed detail from the DWG.

     

    Also, there is no true compatibility with DGN and DWG files. (The Working Units/Resolution don’t truly/exactly translate.)

     

    What I found is the issue seems to be related to having a DGN file Referenced to a DWG file with a substituted name (Microstation substitutes automatically) which changes the DGN extension to DWG. When closing the file with substituted DGN to DWG extension reference, Microstation Crashes. The cause of the crash seems to be related to Microstation’s Automatically Save Design Changes Preference. Microstation seems to attempt to write to the file being closed (probably trying to save the Substituted DGN to DWG name). However, when a DGN file is attached as a reference to a DWG file it is not possible to store the DGN name in a the DWG file.

     

    Workaround Suggestion:

     

    • The workaround is to Toggle off the Automatically Save Design Changes in the Microstation Menubar > Workspace > Preferences… > Operation > Set Operational Preferences and comment out the Loadvba.mvba from the Sitefdot.txt file.

    • Merge into master the detail needed from the DWG and Detach the DGN referenced to the DWG file and only work in DGN’s.

     

      

Reply
  • System Fault: 20301 error:

     

    I think we’re a little closer to knowing the cause of the System Fault: 20301 error.

     

    This Error also may be related to 2 other errors we come across:

     

    System Fault: bad memory access

    Exception has been thrown by the target of an invocation

     

    In the example presented, the System Fault: 20301 error seems to be due to a CadInputQueue.SendCommand "Save Design"Command initiated in our LoadVBA.mvba necessary for our Drainage Platform to function correctly coupled with the Microstation Preference setting Automatically Save Design Changes. In the FDOTSS4 workspace, we use a LoadVBA.mvba to set settings and perform certain functions when opening a Microstation session. The settings, functions and application initiation are necessary for our FDOTSS4 workspace to function correctly for our many disciplines.

     

    In the case where DWG's will be edited in a Microstation Session in our FDOTSS4 workspace try the following:

     

    1. Comment out the following from the configuration in the SiteFdot.txt file (in red):

       

      %if !defined (_CONSOLEAPP)

        MS_DGNAPPS > $(_USTN_SITE)menu/Program/ustn0811/cadpilot.ui.ma

       MS_DGNAPPS < ustnqcinspector

       MS_DGNAPPS > FDOT.LDM

        MS_DGNAPPS > $(_USTN_SITE)apps/SyncXS/SyncXS.dll

        #MS_VBAAUTOLOADPROJECTS > $(_ustn_site)vba/LoadVBA.mvba

      %endif

       

    2. Navigate to the Microstation Menubar > Workspace > Preferences… > Operation > Set Operational Preferences > toggle off the Automatically Save Design Changes.

       

      Note: You will have to manually save your files.

     

    This will stop the initial System Fault: 20301 error, but will affect your FDOTSS4 workspace.

     

     

    Subsequent file switching Crash with the “Save Design” and Automatically Save Design Changes:

     

    There is another issue which I believe is related to the System Fault: 20301 error. This issue is caused by having a DGN file referenced to a DWG file with the “Save Design” and Automatically Save Design Changes on.

     

    This issue produces the following errors when switching from DWG to DWG with Automatically Save Design Changes toggled on and the Loadvba.mvba not commented out in the Sitefdot.txt file:

     

    System Fault: bad memory access

    Exception has been thrown by the target of an invocation

     

    Generally, having a DWG file referenced to a DGN is opposite of our current recommended workflow involving utilization of DWG’s in a Microstation session. If DWG’s are needed for some detail work within a project we recommend referencing the DWG to a DGN and Merging to Master the needed detail from the DWG.

     

    Also, there is no true compatibility with DGN and DWG files. (The Working Units/Resolution don’t truly/exactly translate.)

     

    What I found is the issue seems to be related to having a DGN file Referenced to a DWG file with a substituted name (Microstation substitutes automatically) which changes the DGN extension to DWG. When closing the file with substituted DGN to DWG extension reference, Microstation Crashes. The cause of the crash seems to be related to Microstation’s Automatically Save Design Changes Preference. Microstation seems to attempt to write to the file being closed (probably trying to save the Substituted DGN to DWG name). However, when a DGN file is attached as a reference to a DWG file it is not possible to store the DGN name in a the DWG file.

     

    Workaround Suggestion:

     

    • The workaround is to Toggle off the Automatically Save Design Changes in the Microstation Menubar > Workspace > Preferences… > Operation > Set Operational Preferences and comment out the Loadvba.mvba from the Sitefdot.txt file.

    • Merge into master the detail needed from the DWG and Detach the DGN referenced to the DWG file and only work in DGN’s.

     

      

Children
No Data