You can use MDrivenServer administration to find out why a Turnkey application is paused and verify that the model version is ready to run.
Check whether the application is paused
A paused Turnkey application cannot perform normal application work. Check its state in MDrivenServer when the application appears unavailable or reports that it is not able to start.
- Open the MDrivenServer administration site.
- When Turnkey and MDrivenServer are installed in the same Azure web application, the usual address is
https://yourapp.azurewebsites.net/__MDrivenServer.
- When Turnkey and MDrivenServer are installed in the same Azure web application, the usual address is
- Sign in with the MDrivenServer administrator account
aand its configured password.- For a hosted site, the password may be available in your License and Ticket information as MDriven Password.
- If you administer your own Azure installation and need to reset this password, follow HowTos:Install MDriven Server and Turnkey on Microsoft Azure.
- In the administration area, open Admin_area, then ModelVersionAdministration.
- Find the application model and inspect its state.
| What you find | What it means | What to do |
|---|---|---|
| Started | The application is enabled for normal operation. | Continue investigating logs or the active model version if the application still behaves unexpectedly. |
| Paused | The application is not enabled for normal work. | Start the application after confirming that a valid current model version is available and updated in the database. |
| No model versions | No model has been uploaded to MDrivenServer. | Upload a model from MDriven Designer before the application can start. |
Verify the model version before starting
A running Turnkey application needs a model version selected as its current version. The selected version must also be in the DatabaseUpdated state.
For example, if the application is paused after an initial site deployment, open ModelVersionAdministration and check the following in order:
- Confirm that at least one model version is listed.
- Confirm that a CurrentVersion is set.
- Confirm that the current version has the state DatabaseUpdated.
- Confirm that the application state is Started, not Paused.
If any of these checks fail, Turnkey can report an error such as Not able to start. Use HowTos:Resolve 'Not able to start' Error for the full resolution procedure.
Review server activity and logs
Use the administration area to review logs and recent server activity when the state is Started but the application still appears strange. The logs help you distinguish a startup or model-version issue from a problem that occurs while the application is running.
Check the application state and current model version first. A log entry is easier to interpret when you know whether the server had a model to run and whether that version was database-updated.
Common situations
A newly created Turnkey site has no application model
A new Turnkey site can contain only authorization services until you upload a model. In this case, the model-version list is empty and there is no current version to start. See Documentation:MDriven Turnkey site creation for site creation and model upload context.
You are editing the UI with Turnkey Live View
Turnkey Live View requires the Turnkey application to be running. If Live View cannot connect, verify that the application is Started and that the current model version is ready before investigating the ViewModel or UI changes.
You need to take the site offline for maintenance
Pausing an application is not a substitute for showing users a maintenance message. To present an offline page during a server update, use the procedure in Documentation:Maintenance page.