Overview
In some cases (usually when hosting M-Files Vaults in your own cloud environment), you may have the vault database in an Azure SQL MI (Azure SQL Managed Instance).
This article lists a few points to consider and keep in mind for such a deployment scenario:
- Basic User Credentials must be manual
- A service break in Azure may cause the M-Files service to be interrupted and it may be necessary to cycle the vault(s) offline-online
Basic User Credentials must be manual
The "basic user" credentials must not be automatically generated. You can read more about this user role here.
With automatic user created by M-Files errors similar to the following can be seen:
M-Files Online
My Vault {3951A183-7504-4231-BB77-0EFFC5765854}
M-Files Server cannot connect to the vault database.
Unspecified error. (Login failed for user 'mfserver {3951A183-7504-4231-BB77-0EFFC5765854}'. (ERROR: 18456, SQLSTATE: 28000))
Cannot open database "My Vault" requested by the login. The login failed. (ERROR: 4060, SQLSTATE: 42000)
BackgroundOperationScheduler.cpp, 867, M-Files Server cannot connect to the vault database. (0x80040456)
VaultOperationsMngr.cpp, 600, M-Files Server cannot connect to the vault database. (0x80040456)
VaultDBSession.cpp, 910, M-Files Server cannot connect to the vault database. (0x80040456)
VaultDBSession.cpp, 843, M-Files Server cannot connect to the vault database. (0x80040456)
DBSession.cpp, 650, M-Files Server cannot connect to the vault database. (0x80040456)
DBSession.cpp, 650, Unspecified error. (Login failed for user 'mfserver {3951A183-7504-4231-BB77-0EFFC5765854}'. (ERROR: 18456, SQLSTATE: 28000)) (0x80004005)
DBSession.cpp, 592, Unspecified error. (Login failed for user 'mfserver {3951A183-7504-4231-BB77-0EFFC5765854}'. (ERROR: 18456, SQLSTATE: 28000)) (0x80004005)
DBSession.cpp, 592, Cannot open database "My Vault" requested by the login. The login failed. (ERROR: 4060, SQLSTATE: 42000) (0x89790002)
(M-Files 23.2.12340.6 2023-03-31T07:02:16.287Z)
Make sure to enter valid credentials that are not generated by M-Files in the Vault properties:
Plan for Service Breaks
Azure will post a list of planned maintenance breaks for your database(s). Make sure to subscribe to it and monitor for upcoming breaks.
With M-Files Admin, it is recommended to take the vault(s) offline just before the database availability break happens and bring them back online after the break ends.
Please also subscribe to the Azure service issues at https://azure.microsoft.com/en-us/blog/three-ways-to-get-notified-about-azure-service-issues/ to receive notifications of service outages. Please note that the link provided is controlled by a 3rd party and M-Files has no control on the contents available via the link.
