You can use this page to find the right procedure for configuring, operating, backing up, and recovering an MDriven Server environment.
MDriven Server is the server component that you administer after deployment. Use the guides below to configure access and server behavior, carry out routine maintenance, and respond to failures. If you are deploying a new environment, start with an installation guide rather than making configuration changes on an uninstalled server.
Choose your task
| If you need to... | Use this guide |
|---|---|
| Install MDriven Server and MDriven Turnkey on Windows and configure IIS | HowTos:Installing MDriven Server on Windows |
| Install a local Linux-based environment and inspect service logs | HowTos:Local Installation |
| Run MDriven on Synology | HowTos:MDriven on Synology |
| Deploy on macOS | HowTos:Deploying on MacOs |
| Deploy MDriven Server and Turnkey on Microsoft Azure | HowTos:Install MDriven Server and Turnkey on Microsoft Azure |
| Install on Windows 7 Enterprise | HowTos:Install MDriven Server on Windows 7 Enterprise |
| Find server documentation by subject | Documentation:Server |
Configure MDriven Server
Start with the server administration interface
After installation, open the MDriven Server URL configured for your deployment and register an administrative user. On an IIS deployment, use the host name that matches the SSL certificate; using a different host name can cause certificate errors and prevent internal server communication. For the Windows deployment path and first-administrator steps, follow HowTos:Installing MDriven Server on Windows.
Use the server administration interface to manage the server's administrative database and user records. In the Windows installation workflow, evolve the administrative database from Admin area → Infos, errors and MDrivenServer evolve → Evolve Admin database before configuring the user account used by MDriven Turnkey.
Configure users and web access
Read User and Web Interface before giving users access to the server. This is where you should establish which accounts administer MDriven Server and which account is used by MDriven Turnkey.
For example, the Windows installation procedure reserves the account name a for MDriven Turnkey. Create your administrator account first, then review the ASP_User records through AutoForm and configure the Turnkey account with its own password. Do not use the Turnkey account as your general administrator account.
If your environment requires integrated Windows identities, use HowTos:MDriven Server with Windows Authentication.
Configure server-wide behavior
Use Server Wide Variables for values that apply across the server. Use Injecting Core Server Parameters when you need to provide parameters to a Core Server deployment. Keep configuration changes documented with the environment and purpose they apply to; for example, record whether a variable is intended for test or production.
Operate and maintain the server
Schedule server-side work
Use Serverside Jobs to understand and manage periodic server-side actions. A periodic action runs on the server rather than in an individual user's client session. Review its schedule and expected result after deployment so that you can tell the difference between a failed job and a job that has not yet become due.
If your solution uses asynchronous work, also review Async Ticket Management.
Monitor logs and service state
Monitor the server after configuration changes, upgrades, and reported errors. On a local Linux installation, the documented log files include:
sudo tail -f /var/www/html/mdrivenserver/Logs/MDrivenServerRollingDEBUG.txt
sudo tail -f /var/www/html/mdrivenserver/Logs/MDrivenServerLogRollingERRORS.txt
The first command follows debug output and the second follows error output. Use the local-installation guide for the complete service setup, including enabling MDriven Server and MDriven Turnkey to start after a restart: HowTos:Local Installation.
Plan upgrades
Before an upgrade, identify the deployed server, its administrative access, and the database backup you can restore. For IIS-based installations, the Windows guide states that an upgrade normally overwrites existing framework files without removing the existing database. Preserve the required folder structure when importing into an existing application, then verify the server URL and logs after the update. Follow the full deployment procedure in HowTos:Installing MDriven Server on Windows rather than treating this note as a standalone upgrade procedure.
Manage data and files
Export files
Use SQL Export from MDriven Server when you need an SQL export from MDriven Server. Use it as part of an intentional backup or migration procedure, not as a substitute for confirming that your database backup is usable.
Download or upload a database
Use Database Download and Upload to download or upload a database. Confirm the target environment before uploading: an upload changes the database used by that environment.
If you need to build the database again rather than transfer it, use HowTos:Recreate SQL Database.
Security and access checklist
Before exposing MDriven Server beyond a trusted network, review these operational controls:
- Use HTTPS and access the server through the host name in its certificate. On IIS, an incorrect host name produces a certificate error and can stop internal communication.
- Give administrators their own accounts. Keep the MDriven Turnkey account separate from administrator accounts.
- Grant the application identity only the file access it needs. On IIS, the application pool identity needs access to the application files and write/modify access to the log directory; it also uses
%temp%when extracting deployed assets and assemblies. See HowTos:Installing MDriven Server on Windows. - Restrict access to server administration, database-transfer functions, and exported data to authorized operators.
- Record who can recover an administrator account before an incident occurs.
Troubleshoot and recover
You cannot sign in
If you have lost an administrator password or are locked out, follow Documentation:Lost Password or Locked Out. Do not make unrelated database changes while resolving access; first establish which account and server environment you are recovering.
The server database is corrupt
Follow Documentation:Corrupt MDriven Server for the recovery process. Gather the relevant error log entries and identify the affected environment before attempting repair or restoration.
The server does not start or returns an IIS error
For Windows deployments, verify the IIS prerequisites and application-pool configuration in HowTos:Installing MDriven Server on Windows. In particular, a 403 error can indicate that ASP.NET 4.7 or later is not installed. If the login screen returns HTTP 405, verify that HTTP Activation is installed when the deployment requires it.
For local Linux deployments, inspect the rolling debug and error logs described in HowTos:Local Installation.
Evolve fails
Use Documentation:Problem with Evolve when the administrative database evolve operation fails. Record the error text and the point in the evolve process at which it occurs before changing configuration.