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: 37
Registered: ‎02-19-2019
Accepted Solution

Error while starting workflow: 404 not found

[ Edited ]

Hi Communiny,

 

I'm getting this error (The resource you are looking for has been removed, had its name changed, or is temporarily unavailable) while opening any workflow. Apps is running perfectly but any button click showing bellow error. (It was working perfectly yesterday and then IIS configuration is changed and now not working) , I have repaired MAPP 2018 version. Please let me know what needs to do on IIS server. Thanks in advance !

 

button click.png

 

workflow error.png

 

 

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

Re: Error while starting workflow: 404 not found

Hi Liton,

 

Can you be more specific on the IIS configuration change?

What you can do to track down the issue is to check IIS log after failed Workflow launch attempt.

 

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Contributor
Posts: 37
Registered: ‎02-19-2019

Re: Error while starting workflow: 404 not found

Hi Jan,

 

Same server we installed 'FME Server software' after that getting this error. FME server uninstall from that server. I have repaired IIS and M.App but issue not resolve. Not sure why is getting this erro. I'm assuming its a IIS issue but not sure. 1 day ago application was running perfectly.

 

Thanks,

Liton

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

Re: Error while starting workflow: 404 not found

It may be that the FME Server changed binding information, or added some URL Rewrite / Redirect rules. IIS repair will not likely help as the configuration will be still stored in IIS XML file(s).

You might also add Failed Request Tracing component to IIS and then inspect how is the request for Workflow being processed.

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Contributor
Posts: 37
Registered: ‎02-19-2019

Re: Error while starting workflow: 404 not found

Hi Jan,

 

Please see the IIS log . Thank you.

#Software: Microsoft Internet Information Services 10.0
#Version: 1.0
#Date: 2019-05-28 11:56:14
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2019-05-28 11:56:14 193.120.94.182 POST /api/v1/oauth2/token - 443 - 193.120.94.93 Google-HTTP-Java-Client/1.22.0+(gzip) - 200 0 0 1246
2019-05-28 11:56:15 193.120.94.182 POST /Workflows/MapState/SaveMapState workflow=Planning&tenant=PlanningCapture&sessionid=ddb74b4a-d671-4abf-b7c9-bae79bc78c77&nodeid=Records 443 - 193.120.94.93 Google-HTTP-Java-Client/1.22.0+(gzip) - 404 0 2 997
2019-05-28 11:56:52 193.120.94.182 GET /api/v1/desktopclient/0ed8e3ae-8009-4606-bfd1-705f2a3b5b9e.hnlp tenant=PlanningCapture&refreshToken=9f8c7ec5-05a3-4725-af7f-f5e929caf46d 443 - 193.120.94.93 Java-http-client/11 - 200 0 0 1044
2019-05-28 11:56:52 193.120.94.182 GET /api/v3/desktopclient/hnlp/downloads resource=Images/appIcon.png&type=image 443 - 193.120.94.93 Java-http-client/11 - 200 0 0 29
2019-05-28 11:56:52 193.120.94.182 GET /api/v3/desktopclient/hnlp/downloads resource=Images/appSplashImage@1x.png&type=image 443 - 193.120.94.93 Java-http-client/11 - 200 0 0 15
2019-05-28 11:56:52 193.120.94.182 GET /api/v3/applauncher/localization language=en 443 - 193.120.94.93 Java-http-client/11 - 200 0 0 15
2019-05-28 11:56:55 193.120.94.182 POST /api/v1/oauth2/token - 443 - 193.120.94.93 Google-HTTP-Java-Client/1.22.0+(gzip) - 200 0 0 15
2019-05-28 11:56:55 193.120.94.182 GET /api/v3/desktopclient/localization - 443 - 193.120.94.93 Google-HTTP-Java-Client/1.22.0+(gzip) - 200 0 0 77
2019-05-28 11:56:56 193.120.94.182 GET /api/v3/desktopclient/localization - 443 - 193.120.94.93 Google-HTTP-Java-Client/1.22.0+(gzip) - 200 0 0 0
2019-05-28 11:56:56 193.120.94.182 GET /api/v1/desktopclient/0ed8e3ae-8009-4606-bfd1-705f2a3b5b9e.json - 443 - 193.120.94.93 Google-HTTP-Java-Client/1.22.0+(gzip) - 200 0 0 904
Technical Evangelist
Posts: 1,118
Registered: ‎09-11-2015

Re: Error while starting workflow: 404 not found

[ Edited ]

Ok, that doesn't bring much more light into the problem. You should basically inspect why the IIS responds with 404 error. As written above, Failed Request Tracing enabled on the MApp web site might help investigating the issue.

 

You can also use some simpler URL just for the sake of tests, e.g.:

https://193.120.94.182/Workflows/Content/Css/ig/ig-common.css

 

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Highlighted
Contributor
Posts: 37
Registered: ‎02-19-2019

Re: Error while starting workflow: 404 not found

Hi Jen,

 

Plase see the failedReqLogFiles at attached. If you get any info then  please suggest me. 

 

Thank,

Liton

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

Re: Error while starting workflow: 404 not found

With ASP.NET MVC (used in Workflows), the IIS shouldn't be looking for a physical folder such as 'C:\Program Files\Hexagon\M.App Enterprise\Workflows\MapState\SaveMapState'. There's something misconfigured on the server. If you are unable to revert the IIS changes after installing 3rd-party server products, you might want uninstall M.App Enterprise, restore IIS to the original settings and then install MAE back.

 

See:

 

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Contributor
Posts: 37
Registered: ‎02-19-2019

Re: Error while starting workflow: 404 not found

Issue resolved,

I restored my server from 2 days old backup .

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.