M-Files 26.1 Emergency Patch

Note

This emergency patch applies only to environments where M-Files version 26.1.XXXX or higher is installed on the SQL Server.

Background

Starting with M-Files version 26.1, the folder location for M-Files API assemblies has changed. This change affects MFSQL Connector installations and may cause assembly-related errors until the Connector is updated.

While we are working on a permanent solution in an upcoming release, you can apply the following workaround to restore functionality immediately.

When to Apply This Patch

Apply this emergency patch if:

  • M-Files version on your SQL Server is 26.1.XXXX or higher

  • You are experiencing assembly-related errors with MFSQL Connector

  • You cannot wait for the next official MFSQL Connector release

Warning

These steps modify a stored procedure and must be applied to each MFSQL database in your environment.

Emergency Patch Steps

Follow these steps carefully for each MFSQL Connector database:

  1. Open SQL Server Management Studio (SSMS) and connect to your SQL Server instance.

  2. Select the MFSQL Connector database in the Object Explorer.

  3. Expand the Programmability folder in the Object Explorer.

  4. Locate the procedure spMFUpdateAssemblies under Stored Procedures.

  5. Right-click on spMFUpdateAssemblies and select Modify.

  6. In the procedure code editor, press Ctrl+F to open the Find dialog.

  7. Search for the text: N'\Common'

  8. Replace it with: N'\Bin\X64'

    Tip

    The folder path change is from \Common to \Bin\X64

  9. Click Execute (or press F5) to save the modified procedure to the database.

  10. Execute the following command to update the assemblies, replacing the version number with your specific M-Files version:

    EXEC spMFUpdateAssemblies @MFilesVersion = '26.1.15632.6'

    Note

    Replace 26.1.15632.6 with the exact version of M-Files installed on your SQL Server. You can find your M-Files version by checking the M-Files Desktop application or by querying the MFDeploymentDetail table.

  11. Verify the procedure completes successfully with a message indicating no errors.

Verification

After applying the patch, verify the update was successful:

EXEC spMFVaultConnectionTest

The results should not return any errors. If the test is successful, you will see a success message confirming the vault connection, M-Files version validation, and license validation are all working correctly.

Next Steps

This emergency patch is a temporary workaround. When the next version of MFSQL Connector is released with permanent support for M-Files 26.1+, follow the standard Upgrades and hotfixes process to upgrade.

For additional assistance, contact support@lamininsolutions.com.