Common Error Messages & Solutions
This page was created by Wikiadmin on 2026-07-29. Last edited by Wikiadmin on 2026-07-29.
You can use this page to find the right troubleshooting guidance when an error affects a Turnkey site, IIS deployment, or MDrivenServer.
Start with the error symptom
| Symptom or error | What to check | Direct guidance |
|---|---|---|
| HTTP Error 500.30 – ANCM In-Process Start Failure | Confirm that the correct bundle is installed, and that the application-pool account has read and write access to the application folder. | Deploying MDriven Server & Turnkey Core on IIS |
| Turnkey application does not start in IIS | Remove the httpErrors section that routes errors into the application, and confirm that <compilation debug="true" /> is configured.
|
Troubleshooting IIS application startup issues |
| Database connection error | Verify the connection string and network connectivity. | Deploying MDriven Server & Turnkey Core on IIS |
| MDrivenServer, Turnkey, or IIS issue without a clear error message | Review the application and server logs before changing configuration. | Turnkey and MDrivenServer logs |
| ServerSide action does not run as expected | Review the OCL expression, action configuration, and access group settings for the ViewModel. | ServerSide actions |
| WCF reports an unexpected server shutdown or provides too little detail | Enable explicit WCF logging in the server web.config.
|
WCF issues |
Collect diagnostic information
For an IIS-hosted installation, check Event Viewer Application Log and IIS log files.
For a Turnkey site, you can also use Turnkey and MDrivenServer logs to access browser, portal, Azure SCM, and command-line log options. For example, the current error log can be viewed at https://<yourturnkey>/logs/TurnkeyServerLogRollingERRORS.txt.
Check application status
If your Turnkey site has Show Debug Info enabled in the portal, open https://<yourSite>/Developer/Serverinfo to review application status. The IIS account that runs the application must have write access to the Logs folder for logging to succeed. See Serverinfo for details.