Getting Started

• Installation Overview
  • What is included
  • Key features of the installation packages
  • Download software
  • Deployment server model
• First time installation
  • Standard Installation
  • Content Package installation
  • Installing the Context Menu
  • Configuration of connection string
  • Installing the Web API
  • Database file connector installation
  • Using Agent for automated updates
  • Common installation errors and resolutions
  • Setup powershell utilities
  • Install package with logging
  • Installation scenarios
• Manual installation using scripts
  • Install package on workstation
  • Relevant Installation Files
  • Manual install MFSQL Connector on the M-Files Server
  • Manual install MFSQL Connector on the SQL Server
• Licensing Management
  • Application licenses
  • License types
  • Installing the license
  • Expiry notification
  • Check license validity
  • Update expired or due to expire license
  • Licensing trouble shooting
• Next Steps after installation
  • Test installation
  • Update metadata
  • View available class tables
  • Create first Class Table
  • Update Records in Class Table
  • Ready for real action
• Using example scripts
• Upgrades and hotfixes
  • M-Files automatic upgrade
  • Upgrading version 4.8.22.62 or later
  • Types of Upgrades
  • Preparation for upgrading
  • Automatic updates
  • Manual update of the Connector
  • Upgrade the Connector to a new version
  • Version Check
• Update settings
  • Installation
  • User definable settings
  • View settings
• Set-up and working with Connector Database
  • Backup and restore of Connector
  • Changing name of database
  • Fixing orphaned user account
• Database Mail
  • Send errors with database mail
  • Setup database mail
  • scripting Database Mail create
  • Monitoring of database mail

Quick steps for a new installation.

•  Check out the prerequisites Requirements

•  M-Files

  • Minimum version 12.0 (M-Files 2018)

  • Target Vault is pre-created

  • Named User dedicated to MFSQL Connector with Vault admin rights is available

  • The context menu connection string configuration will use the connection to the M-Files Server user credentials. This user must have system administrator rights configure or change the connection string.

  • The M-Files IML (Intelligent Metadata Layer) Core license is required for the MFSQL Database File Connector to operate

• SQL

  • Microsoft SQL Server version 2012, 2014, 2016, 2017, 2019 Express , Standard, or Enterprise editions.  (Note that procedures dependent on SSIS or SQL agents will only operate in Standard or Enterprise)

• Always start with installation on the M-Files Server, and then the SQL Server for standard installations or upgrades

• Follow the manual installation instructions for performing the SQL server installation without running the installation package

• Follow the Cloud installation instructions for performing an installation for M-Files Cloud

• Follow the WEB API instructions for installing a web service between M-Files and SQL Server

• Follow the workstation installation instruction for installing the installation files only. This method is used to get access to the installation files for manual installation of certain parts of the package.

• The installation package will install the SQL Server and M-Files Server in one session if it is on the same computer.

• Run installation as windows administrator with sysadmin access to the SQL Server.

• Always log into M-Files in the prompt.

• Always take vault off-line and bring back online after installing the vault applications on the M-Files Server

• Update DB File Connector Configurator using M-Files Admin

• Use SSMS and the examples scripts to get started with MFSQL Connector