Product(s):	MicroStation
	Version(s):	25.00.xx.xx
	Environment:	N\A
	Area:	Open/Save
	Subarea:	Performance

Problem

MicroStation and related Bentley design products may intermittently fail to start or stop while running.  The cause is that some external process has deleted the AddInLoader1.0 folder required by Bentley desktop products.

A typical failure would be:

It could affect any PowerPlatform based product.

Solutions:

1. The recommended solution is to download and copy KeepAddinFld.ma and KeepAddinFld.dll into the MdlSys\Required folder usually located at C:\Program Files\Bentley\MicroStation\MdlSys\Required.

The KeepAddinFld application will prevent the AddInLoader1.0 folder from being deleted by other processes while MicroStation is running.

Click on this link to download the files, MicroStation Files - Fix for Fatal Error "Could not create a .ma file for an Addin" - Communities 

2. Alternatively, you can discover which process is improperly deleting the required AddInLoader1.0 folder by doing the following steps.

Troubleshooting Option:

Use ProcMon to gather dump files for further analysis 

Actions

Gather usual system information.  In a command prompt enter

systeminfo | clip

Paste the results into the e-mail response and format the text with a mono-space font like Consolas or Courrier to make it easier to read.

Use ProcessMonitor to monitor file access.  In this case we monitor activity in the AddInLoader1.0 folder

To monitor access to files in the AddInLoader1.0 folder, we can specify the files in the folder using the Process Monitor utility.

Steps…

1. Download ProcMon (Process Monitor utility from here: Process Monitor - Sysinternals | Microsoft Learn using your favorite browser.
2. Expand the .ZIP into separate files
3. Run Command Prompt in administrator mode
4. Type in    cd %temp%
   to change prompt to temporary folder.  This will help prevent you from unintended changes.
5. Run Process Monitor from the path were the download .ZIP was expanded. The default is the current user’s download directory.

Run Process Monitor
  %USERPROFILE%\Downloads\ProcessMonitor\Procmon64.exe   /noconnect

The /noconnect option prevents Process Monitor from collecting events before filters are established.  We are establishing maximal filtering consistent with recording the information that we need without overwhelming and negatively impacting the user’s computer.

       6. The next steps add in filters to collect only those operation involving the folder path “AddInLoader1.0

         Add filter:

1. In the first option box change Operation to Path
2. In the second option box change is to contains
3. In the third option box type in AddInLoader1.0
4. In the fourth option box select Include
5. Click the Add button

7. Filter out other operations that are not needed for this analysis.
   Add filter:
   1. In the first option box change “Operation” to “ReadFile”
   2. In the second option box change “is” to “contains”
   3. In the third option box type in “AddInLoader1.0” (do not enter the quotes)
   4. In the fourth option box select “Exclude”

Click the Add button

8. Drop Filtered Events

9. Create Saved File, Go to File>Backing Files…

10. Choose a location and file name. I recommend a path like
        %temp%\Procmon-logs\CS0061200_2023-08-22_A
    where the tail of the path is replaced by your service case number followed by today’s date for uniqueness. The “_A” suffix can be used to distinguish multiple data collection cycles within a day.
11. Capture Events

Allow ProcMon to run in the background until error occurs again.  You can minimize the ProcMon window.

Once error has occurred go to ProcMon’s File>Save and save a .pml file. Please send that file to your Bentley support representative.  You can compress the file to reduce storage space and transmission time.