Overview
Suppose you receive the following type of error message when you are logging in to a vault with the New M-Files Desktop or M-Files Web:
Pressing the Show details button brings the following detailed error text visible:
Stack: TypeError: Cannot read properties of undefined (reading 'running')
at Ae.setModuleState (https://<removed from this example>.mfdesktop.local/get-content-of-script-application-file/<guid>/src/shellui.js:1:15542)
at https://< removed from this example >.mfdesktop.local/get-content-of-script-application-file/<guid>/src/shellui.js:5:1860
at Array.forEach (<anonymous>)
at se.onConfigurationLoaded (https://< removed from this example>.mfdesktop.local/get-content-of-script-application-file/<guid>/src/shellui.js:5:1846)
at se.loadConfigurationAsync (https://< removed from this example >.mfdesktop.local/get-content-of-script-application-file/<guid>/src/shellui.js:5:2145)
This type of error may occur when the vault has the Compliance Kit (impacts CK 24.10 and CK 25.3) installed, and some modules are not loaded at all in CK, for example, because the modules are included in CK's license or are disabled by configuration.
Solution
This is related to a known issue, fixed with ID: DXR-189.
We have released a newer Compliance Kit version - 25.3 SR1 (25.3.1262.2), which includes the fix.
It is available on our Catalog page.
Upgrading Compliance Kit to this newer version resolves the issue.
