MDrivenServer is the back-end runtime for people who need to run, configure, or troubleshoot an MDriven application and connect it to MDriven Turnkey.
What MDrivenServer does
MDrivenServer runs the server-side part of an application defined in MDriven Designer. It is responsible for object-relational mapping, maintaining SQL evolve, and server-side jobs. MDriven Turnkey is the front-end server that provides the user interface and REST services.
For example, a local development environment can run MDrivenServer as the back end while MDriven Turnkey presents the application in a browser. Turnkey connects to the MDrivenServer URL configured for that installation.
For a conceptual introduction, see Documentation:What is MDriven Server?.
Choose your setup path
Use the route that matches where and how you will run the application.
| Your goal | Start here | What to check |
|---|---|---|
| Run a local MDrivenServer and Turnkey pair for development or testing | Documentation:LocalServers | Local server files and settings have moved from the Documents/OneDrive location to a local AppData location. If an existing local server appears missing, copy its old local database into the new installation's MDrServer/App_Data folder or download the local server again.
|
| Install MDrivenServer and Turnkey on a Linux host | Local Installation | Make TCP ports 5010 and 5011 available, then verify the services and their logs.
|
| Run MDrivenServer and Turnkey natively on macOS | MDriven Server & MDriven Turnkey on Native macOS | Keep the terminal windows open while running the processes, unless you have configured another way to keep them running. Check for port conflicts on 5010 and 5011.
|
| Find the legacy Windows 7 Enterprise installation page | Documentation:Installation of MDriven Server on Windows 7 Enterprise. | This page is a redirect; follow it to the current destination. |
Connect Turnkey to MDrivenServer
When Turnkey and MDrivenServer do not use the default server location, configure Turnkey with MDrivenServerOverride.xml. Place this file in Turnkey's App_data directory. The override replaces Turnkey's default server/__MDrivenServer location.
A basic override identifies the MDrivenServer URL and supplies the server password:
<root>
<MDrivenServerOverride MDrivenServerPWD="thepwd">https://TheUrl</MDrivenServerOverride>
</root>
For example, use an override when Turnkey runs on one host and MDrivenServer runs at a separate HTTPS URL. For the available attributes, including the compatibility option for incompatible SignalR versions and prototype options, see Documentation:MDrivenServerOverride.
Verify a running installation
After installation, verify the following before investigating application behavior:
- Confirm that MDrivenServer is running and that Turnkey can reach the configured MDrivenServer URL.
- Confirm that the required TCP ports are not blocked. The local-installation guidance uses
5010for MDrivenServer and5011for MDriven Turnkey. - Open the application through Turnkey, not by treating MDrivenServer as the UI server.
- Review the logs when a process fails to start or a connection fails.
On the Linux layout documented in Local Installation, MDrivenServer log files include:
sudo tail -f /var/www/html/mdrivenserver/Logs/MDrivenServerRollingDEBUG.txt
sudo tail -f /var/www/html/mdrivenserver/Logs/MDrivenServerLogRollingERRORS.txt
The same installation guide shows how to enable the MDrivenServer and MDriven Turnkey services to start after a host restart. Follow that guide rather than copying these paths to another operating system or installation layout.
Common administration tasks
| Task | Guidance |
|---|---|
| Change a server password | Use Documentation:Change password MDriven Server. If user registration has been turned back on and does not become available, the documented guidance notes that a server âzapâ may be needed. |
| Recover from a lost password or lockout | Start from Documentation:Change password MDriven Server, which directs you to the lost-password guidance. |
| Export SQL from MDrivenServer | Use Documentation:SQLExport from MDriven Server. This page redirects to the training material that owns the procedure. |
| Restore a missing local-server setup after the folder move | Use Documentation:LocalServers. Preserve the previous local database before replacing or recreating a local installation. |
Local-server folder move
Local server settings were moved to avoid OneDrive synchronization. An older local database may be found under a path such as:
C:\Users\<USER>\OneDrive\Dokument\MDrivenServers\Server1\MDrServer\App_Data\DatabaseVistaDB.vdb6
The documented new location is under:
C:\Users\<USER>\AppData\Local\MDrivenServers\Server1\MDrServer\App_Data
Copy the old local database to the corresponding new App_Data directory when you need to retain the local server state and settings. See Documentation:LocalServers for the complete recovery and download guidance.