Question

Why does my model fail when running with Cloud Execution?

Answer

The MIKE Cloud Engine Execution is a Cloud-based Service.
In case you experience issues with the Cloud Execution that cannot be explained by messages in the product log file it is possible to extract additional information as described below.

#01 - Using Simulation Launcher

The Simulation Launcher will appear when executing a model setup directly from the desktop GUI. It can also be opened directly from MIKE Zero. In the Simulation Launcher, ‘Debug’ and ‘Logging’ can be activated to generate two special text files (Debug.txt and Log.txt). The Log.txt is not a normal simulation log, but includes additional debugging information related to the Cloud process. The information in these txt files may be difficult to interpret but gives valuable information for our supporters when investigating the issue.

To activate this functionality, place the cursor in the Simulation Launcher window, press Ctrl-Shift and right-click mouse to enable a pop-up that can enable/disable logging of the Cloud Process.  See Fig. 1.

Fig 1 - Pop-op dialog to enable/disable creation of debug and logging text files in Simulation Launcher

The logged information can be accessed by double-clicking the links placed top right. This will open a File Explorer in the folder where the files are saved; C:\Users\[username]\AppData\Local\Temp\DHI.Cloud.SimulationLauncher.  See Fig. 2.


Fig 2 - Fly-by text when placing cursor 

In the Simulation Launcher, even if the simulations fails, you should be able to retrieve the simulation log file by selecting the simulation line and clicking [View log]. If this doesn’t work, then the log files will be available in the selected results folder in MIKE Cloud.  See Fig. 3.

Fig 3 - Information related to simulation output

#02 - Using Cloud Explorer

You can select to execute one of the existing setups in MIKE Cloud Admin from here.

The Cloud Explorer gives a user access to the files stored in MIKE Cloud Admin, that being e.g. setup files and result files. In the Cloud Explorer, ‘Logging’ can be enabled/disabled in similar way as for the Simulation Launcher described above.
Place the cursor on a folder in the Cloud Projects window to the left, and press Ctrl-Shift and right-click mouse to enable a pop-up that can enable/disable logging of the Cloud Process. Enabling this will create both a debug.txt and a log.txt file, however the files will be placed in another folder; C:\Users\[username]\AppData\Local\Temp\DHI.Cloud.PlatformClient.  See Fig. 4.

Fig 4 - Pop-op dialog to enable/disable creation of debug and logging text files in Cloud Explorer

#03 - Problems uploading files to MIKE Cloud

If you have problems uploading files to MIKE Cloud, you can check that all necessary files for a setup are uploaded to MIKE Cloud using the command inputfiles -c listinput -I “setup file” in a DOS prompt.  See Fig. 5.

Fig 5 - Example of listing of uploaded files for setup from command line

#04 - Error messages

Here are some common error messages and their meaning.

Directory does not exist

You may get the error message ‘Directory: Does not exist”, followed by “No files referred in setup file could be found!”
It could be related to the file setup referring to files on another drive, e.g. |\\my-shares\Site Development\HD models\MySetup\Boundaries\dfs0\1997\RiverS_April.dfs0|
Such references are not allowed in Cloud Execution (but they can work will on the desktop PC)

It could also be that there are special characters in the full path to the setup file or to one of the referenced data files. E.g. a model with ’æøå’ in the path runs OK on desktop PC, but not via Cloud Execution.

Could not upload files!

The model checks that all related files are available, even if they are not used in the simulation.
References to unavailable files in the setup is not permitted in Cloud Execution (but will work on desktop PC) 

FURTHER INFORMATION AND USEFUL LINKS

Manuals and User Guides
MIKE Cloud Execution.
MIKE Cloud Documentation Library.