Hexagon Geospatial
MENU

M.App Enterprise

Discuss topics with other M.App Enterprise Product pioneers and experts to get the most out of it.
Showing results for 
Search instead for 
Do you mean 
Reply
Contributor
Posts: 90
Registered: ‎11-29-2015
Accepted Solution

Geoprocessing server: error async process

Hey everyone,

 

we are trying to run the geoprocessing server with M.App Enterprise.

  • The client can browse the https-URL of the geoprocessing server
  • the servername has been configured within the MAE Installation using https://servername
  • The geoprocessingserver can access the warehouse folder
  • the installation of the geoprocessingserver has been done step by step to the manual

The spatial workshop is running an the recipe can be created. Unfortunately, the model fails by execution saying:

 

'Error: RemoteCallFailed: Execution of the async process has failed. url: https://zur-sgiv-maegeop/api/v1/geoprocesses/23caea1c-dfbe-4ec9-9363-f7ebe214f459/execute'

 

Can someone tell us more about this error? Does it point to a misconfiguraiton on the geoprocessing server?

Thanks and regards,

Hella

Technical Evangelist
Posts: 1,118
Registered: ‎09-11-2015

Re: Geoprocessing server: error async process

Hi Hella,

 

The major issue I am seeing is that the SSL certificate is self-signed. The JS will usually fail when there are certificate errors. You have following option:

  • use a valid certificate for fully qualified domain name
  • step down to HTTP on both M.App Enterprise and Geoprocessing servers

 

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Contributor
Posts: 90
Registered: ‎11-29-2015

Re: Geoprocessing server: error async process

Hey Jan,

 

thanks for your response.

I have now changed the geoprocessing-config to http://servername.

 

Are there configurations to do on the MAE-machine? At the end of the configs it is suggesting opening the management via https. However, I am able to open all the MAE-URLs through http://mae-server.

 

The problem still exists, when executing the mdoel on the http-URL.

 

Am I something missing out?

Regards,

Hella

Technical Evangelist
Posts: 1,118
Registered: ‎09-11-2015

Re: Geoprocessing server: error async process

Did you re-run Configuration Wizard on the MAE server to set up the new geoprocessing URL (the last step)?

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Contributor
Posts: 90
Registered: ‎11-29-2015

Re: Geoprocessing server: error async process

Yes I did. The error message is now the same but saying http:<>.

Technical Evangelist
Posts: 1,118
Registered: ‎09-11-2015

Re: Geoprocessing server: error async process

It looks like there's some misconfiguration on the Geoprocessing server. Are there some additional URL Rewrite rules? If it's a cluster node, there may be a problem in ARR / SSL configuration.

Capture.PNG

 

Instead of the Console, I suggest watching the Network tab, where you'll see all the requests, and responses that you can inspect in more details.

 

The geoprocessing server seems to work otherwise: http://zur-sgiv-maegeop/api/v1/models

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Staff
Posts: 1,036
Registered: ‎10-18-2015

Re: Geoprocessing server: error async process

please check on the server side the following windows services are up and running:

  • Geoprocessing Worker Service
  • ImageManagement Web API Service

Your geoprocessing server should correctly return JSON responses for the following endpoints:

 

  • /api/v1/geoprocesses/health
  • /v2/api-docs

 

Stefano

Stefano Turcato
Presale Engineer
Hexagon Geospatial
Contributor
Posts: 90
Registered: ‎11-29-2015

Re: Geoprocessing server: error async process

[ Edited ]

Hi Stefano,

the ImageManagement Web API Service is not installed. Should this be done through the geoprocessing installation?

 

Do you suggest to uninstall and install again?

 

Thanks and regard,

Hella

Contributor
Posts: 90
Registered: ‎11-29-2015

Re: Geoprocessing server: error async process

[ Edited ]

The console also lists something about the CORS policy..

I have just checked the configuration wizard and the CORS is enabled with the Access-Control-Allow-Origin header *.

 

 

In the installation-log I have found a FATAL about the MappX-ImageManagement.. 'FATAL Intergraph.Configuration.ConfigurationActionExecutor - Action type Intergraph.Configuration.GeoprocessingWorkerConfiguration.Actions.GeoprocessingWorkerConfigurationAction threw exception
Intergraph.Configuration.ConfigurationUtilException: Unable to change a service named: 'HXD-MappX-GeoprocessingJMS' to run under credentials of a user named: 'ingrnet\XXX''

 

This is the warehouse user defined in MAE. The guide just tells me this user needs the right to read the warehouse-folder (which it does). What are the prerequisitions for the user of the ImageManagment?

Contributor
Posts: 90
Registered: ‎11-29-2015

Re: Geoprocessing server: error async process

I was able to install the ImageManagement WebAPI Service.

 

Now I am confronted with the active directory:

 

INFO [Thread-3] 2019-08-08 14:04:18,779 e7c56f1f-162f-4034-a898-17dd51cfcfa6 MappX Checking all job inputs are valid and exist on active storage
FATAL [Thread-3] 2019-08-08 14:04:18,858 e7c56f1f-162f-4034-a898-17dd51cfcfa6 MappX Unable to ensure inputs are on active storage
java.lang.IllegalStateException: Input dataset '\\<Servername>\M.App Enterprise\Training\00_Data\Stadtkreis\Stadtkreis.shp' cannot be found
at com.hexagon.windmill.workflows.swfgeoprocessing.swf.actions.LocalPathDatasetActions.EnsureInputsAreOnActiveStorage(LocalPathDatasetActions.java:119)
at com.hexagon.windmill.workflows.geoprocessing.GeoprocessingValidator.Validate(GeoprocessingValidator.java:128)
at com.hexagon.windmill.workflows.geoprocessing.GeoprocessingValidationWorker.Execute(GeoprocessingValidationWorker.java:44)
at com.hexagon.windmill.workflows.geoprocessing.GeoprocessingValidationWorker.Execute(GeoprocessingValidationWorker.java:20)
at com.hexagon.windmill.workflows.WorkflowWorker.Process(WorkflowWorker.java:159)
at com.hexagon.windmill.workflows.WorkflowWorker.run(WorkflowWorker.java:182)

 

 

Did I understand correctly:

  • the warehouse will be accessed through the warehouse user on both servers?
  • I have tested the user on the geoprocessing server in the explorer and the access is fine. however, it is not a user on the geoprocessing-server..

 

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Development Ticket through our Development Ticket Portal.