M.App Enterprise Tutorials

Not sure on how to get started or looking for a workflow to get M.App Enterprise up and running. Tutorials provide step by instruction on some of the most common configurations and workflows to get M.App Enterprise configured up and running quickly.
Showing results for 
Search instead for 
Do you mean 

How to solve Spatial Workshop problems

by Technical Evangelist ‎08-15-2019 01:10 AM - edited ‎08-15-2019 06:22 AM (537 Views)


  • The Spatial Workshop window is grayed out when I try to add a new recipe.
  • I cannot see our old recipes there either.
  • Importing a spatial model from IMAGINE (gmdx or json formats) hangs Spatial Workshop.

Any way to troubleshoot this?


There are more possible reasons why the Spatial Workshop does not work, or load a spatial recipe (.gmdx or .json) properly.

Typical Problems List

  • Geoprocessing server is referenced through HTTP during standard HTTPS M.App Enterprise installation
  • Geoprocessing server is referenced with wrong domain name according to the SSL certificate, e.g. computer name vs. fully qualified domain name
  • Self-signed SSL certificate is used on either M.App Enterprise or Geoprocessing server
    Although it is theoretically possible to use self-signed certificate with proper configuration, it is not recommended approach.
  • Spatial Model contains unsupported operators
  • Spatial Model contains invalid references in its ports or operators (e.g. desktop database connection string, local files, ...)

Customer case #1 - Spatial Workshop doesn't load:

Open web browser's Developer Tools for the pop-up window where Spatial Workshop loads (F12 key)

  1. Switch to Network tab - you might need to refresh the window (F5 key)
  2. Watch for web requests and inspect the responses - you will usually find more meaningful message in the response details. Example:
  3. In the image above it is noticeable that the Geoprocessing server doesn't respond properly. You can try to call the request directly in a new browser window. Typically it is: https://[geoprocessing-server-url]/api/v1/models
    This request will tell you if:
    • SSL certificate is valid
    • Geoprocessing server is alive
    • Geoprocessing server has any models stored
  4. Sample issue above was caused by IIS misconfiguration on the Geoprocessing server.
    Similar case was discussed here.

Customer case #2 - Importing Recipe hangs Spatial Workshop:

  1. As in previous problem diagnosis, check if there is any meaningful message in the browser's console > Developer Tools > Network tab
  2. In this case, there was a following request: https://[geoprocessing-server-url]/api/v1/models/convertToJson/
    which lasted up to 2 minutes, and ended up with following error in response:
    {"timestamp":1557832439195,"status":500,"error":"Internal Server Error","exception":"java.net.SocketTimeoutException","message":"Read timed out"}
  3. Further inspection of the GMDX model in ERDAS IMAGINE revealed that there was a database operator present, pointing to database not reachable from the cloud (Smart M.Apps).
  4. After changing the model, the GMDX loaded fine.

Customer case #3 - Model validates but does not run:

  1. The only way to check for problems of a valid model is to run it and check for errors. Some basic information about the model results will be visible in the Spatial Recipe panel of the Browser App (or Smart M.App), but to get more details on the error, you can again use the Network tab of browser's developer tools. The Network tab must be activated prior launching the spatial model.
    1. In case of M.App Enterprise installation, look for request such as:
      GET [servername]/api/v1/geoprocesses/[GUID]/log
    2. In case of Smart M.Apps, look for request such as:
      GET https://mapp.hexagongeospatial.com/api/v1/geoprocesses/[GUID]/log
  2. Detailed exception log revealed a problem with UNC path in Features Output operator which was invalid for the server (or cloud) installation. After modifying the model, it was possible to run in.