This documents walks through the initial troubleshooting steps for the .NET Framework Issue
2 Impacted Products and Versions
All versions of M-Files.
This error can cause loss of many different vault functionalities not just one reoccurring issue. To name a few:
- Unable to create objects
- Unable to log in
- Unable to search
4 Cause and Reason
This can happen when a database is attach or restored from a different server. This problem can occur for several reasons. The login that you used to create the database on Server A is not in the same instance on Server B.
- As a preliminary fix, try to detach then attach the vault. See if this fixes the problem
- From here verify that the account credentials on the SQL server and M-Files database connection match. If they do not please update them, detach the vault, and then attach again
- Use the sp_changedbowner stored procedure to change the database owner to sysadmin or an available login on Server B.
- USE <DatabaseName>
EXEC sp_changedbowner ‘sa’
- The final step would be to make sure that the database has the TRUSTWORTHY property set. You can set this in MSSQL Server Management Studio by navigating to the database -> right click -> properties -> options.
- Note: if this is greyed out despite having sysadmin rights you must execute the following query to change the status.
- Query to see TRUSTWORTHY setting:
- SELECT is_trustworthy_on FROM sys.databases WHERE name = 'DatabaseName;'
- Query to change TRUSTWORTHY setting (Must use sysadmin account)
ALTER DATABASE DatabaseName SET TRUSTWORTHY ON;
6 Reference Documents