You can diagnose a failed MDriven Turnkey deployment by identifying whether the Turnkey or MDrivenServer package failed, then checking the deployment package and the target IIS application.
Understand the deployment order
A Turnkey installation consists of two web applications:
- Turnkey is the web application that users access.
- MDrivenServer is the server application used by Turnkey.
Deploy them in this order:
- Deploy Turnkey.
- Deploy MDrivenServer.
For example, if the portal reports an error while deploying the MDrivenServer package, the Turnkey deployment may already have completed. Investigate the MDrivenServer deployment package and its target application rather than repeating unrelated Turnkey configuration.
Interpret a portal copy error
The deployment portal can show an error similar to:
AT <XXX> Doing MDrivenServerFor <XXX> Copying file <YYYY> to obj\Debug\Package\PackageTmp\<YYYY> failed.
This message means that the failure occurred during the MDrivenServer part of the deployment. The deployment process could not copy the named file (<YYYY>) into the package's obj\Debug\Package\PackageTmp directory.
The message identifies two useful facts:
| Message part | What it tells you |
|---|---|
Doing MDrivenServerFor
|
The failing deployment step is MDrivenServer, not Turnkey. |
Copying file ... failed
|
A file operation failed while preparing or applying the MDrivenServer deployment package. |
obj\Debug\Package\PackageTmp
|
The reported destination is the package staging path involved in this deployment attempt. |
Diagnose the failure
Follow these steps in order. Keep the full portal message, including the server, application, and file names represented by <XXX> and <YYYY>.
- Confirm that the error contains
Doing MDrivenServerFor. If it does, focus on the latest MDrivenServer deployment package. - Identify the file named in the error. Check whether that file is present and usable in the MDrivenServer package you selected for deployment.
- Obtain or select the latest MDrivenServer deployment package again, then retry the MDrivenServer deployment.
- Confirm that you are deploying the MDrivenServer package to the intended MDrivenServer IIS application, not to the Turnkey application.
- If the package deployment completes but the application does not start, use Troubleshooting IIS application startup issues. A successful file deployment and a successful application startup are separate checks.
- If you deploy from the command line or a batch file, use the procedure and command examples in Automate Deployment of Turnkey and MDrivenServer on IIS. Run those commands from an elevated command prompt.
Verify the deployed MDrivenServer
After a successful MDrivenServer deployment on Windows, open MDrivenServer using the application URL described in Installing MDriven Server on Windows. Use the hostname that matches your certificate rather than localhost when the installation requires it.
Example URL structure:
https://<your-server>/<your-application-name>/__MDrivenServer/
If this URL returns HTTP 403, verify the prerequisite stated in the installation guide: ASP.NET 4.7 or later must be installed.
When this page does not apply
This procedure applies to a portal error that explicitly reports a MDrivenServer package copy failure.
Use the relevant guide for other deployment environments or symptoms:
- For an IIS application that deploys but fails to start, see Troubleshooting IIS application startup issues.
- For scripted IIS package updates, including retaining existing settings and resources, see Automate Deployment of Turnkey and MDrivenServer on IIS.
- For a local Linux installation, including log locations, see Local Installation.
- For Docker deployments, including the required Turnkey-to-MDrivenServer password alignment and networking requirement, see Deploying MDriven Server and Turnkey with Docker.