05-01-2018
11:04 PM
- last edited
Monday
by
fcaelen
We had an SDK project working well with Webmap 16.04 and then were ready to move it from behind a firewall and add a security certificate. Somewhere during this process we could no longer display the Admin console. Then the WMS service used to display imagery no longer initialized successfully. The WMPS service was working fine. We deinstalled and then reinstalled Webmap and now were getting an error message about Dense Geometry when the WMPS service attempts the map display and fails.
We have instructions to do this after deinstalling and then reinstall:
Remove Physical folders:
C:\Program Files\Windows Server\Bin\WebApps\Site\AdminConsole (CAN'T FIND THIS FOLDER)
C:\Program Files\Common Files\Hexagon\Services\AdminInstances
IIS app:
AdminConsole branch (contains adminportal and app)
AppPool:
AdminConsoleAppPool
AdminPortalAppPool (UNABLE TO DELETE THIS AS IT CONTAINS AN APPLICATION)
Also have instructions from this source which we tried
http://community.hexagongeospatial.com/t5/Support-WebGIS/HTTPS-Portal-and-services/td-p/14788
Just posting to put all this info in one place and in the hopes of any info that would help us better understand what could have happened and details to get Webmap including Admin Console WMPS and WMS service working again.
If we try to access the admin console the error we get is:
-1:
0:
Solved! Go to Solution.
05-02-2018 05:00 AM
Hi Jane,
Is this address - C:\Program Files\Windows Server\Bin\WebApps\Site\ ... - where the IIS Default Web Site resides?
It might be that the AdminConsole files installed into this typical location - %SystemDrive%\inetpub\wwwroot
...but quite unlikely because the installer should read the web site location from the system. I see that Windows Server 2012 Essentials can use C:\Program Files... subfolders instead.
Anyway, please check this article on how to perform clean reinstallation of WebMap:
05-14-2018 05:14 PM
Got it work after getting the latest web.config file for WMS with SDK 16.04 and making the changes required when using a SSL.
Despite deinstalling all of webmap and reinstalling 16.0, 02,03, 04 I did't have the latest web.config for WMS in my template folder.
Thanks!
05-14-2018 05:31 PM
Hi Jane,
Sticky folders could be your issue.
Refer to this guide:
Focus on step4, manually deleting residual folders/files.
Be careful NOT to over-do the delete (i.e. Read the instructions very carefully, and make backups!!!)
Thanks
Frank
05-14-2018 07:01 PM
The only problem i have left is that the icons are not showing up for WMPS when i am accessing the site via https:
An inspect on the webpage shows they are being referred to with an http URL so it makes sense that they are not displaying. Can change to an https: URL but then a hexadecimal image in part of the link rather than the image name and it doesn't display. Is this post in relation to the WMPS legend icon problem?
05-16-2018 05:02 AM - edited 05-16-2018 05:04 AM
WMPS is not compatible with HTTPS protocol as it uses some older type of bindings that are not possible to "convert" to HTTPS.
What do you mean by hexadecimal images?
05-17-2018 08:28 AM
Hi Jan,
Here is the problem Jane is facing:
WMPS icons are blank under https portal instance.
When ROOT URL is set to https://external.com, the legend icon image path is set to something like:
<img src="Proxy.WebClient.ashx?action=pictogram&mapServiceId=ce89d349-76a2-46d1-abce-41f0ffb7a55c&legendDefinitionId=&legendItemDefinitionId=Bas-Organisation_-_Bestand" class="x-tree-node-icon x-tree-node-inline-icon" unselectable="on" id="extdd-24" style="width: 20px; height: 15px;">
When ROOT URL is set to http://external.com, the image path is set to
http://external.com/JD1/cache/JD_GOV/6.png , however, the legend icon is still blank because it is not reachable (i.e. it is http instead of https), in other words, this is publicly accessible : https://external.com/JD1/cache/JD_GOV/6.png
WMPS are displaying all fine, the customer has tons of thematic legends so blank legend icons are not going to work for their live site.
Thanks
Frank
05-18-2018 01:27 AM
The WMPS service does not need to be externally accessible as all requests to the service are made by Geospatial Portal server-side components.
You could try creating a new IIS web site with a http binding on a custom tcp-port e.g. 81 and then connect to the WMPS using the URL in Geospatial Portal like http://<servername>:<port>/<servicename>/MapService.svc?wsdl
You will need to be careful what you have defined as your Root URL setting in WebMap Settings as depending on the rest of your setup you may need to include the custom tcp-port in the Root URL.
If you do use this configuration you will encounter an issue with the legend entry icons not showing for the WMPS features, this is because the URL to the legend icons will use the custom tcp-port but this is stored in the capabilities xml file generated for the Service Source under the "cache" folder of the WMPS Service Instance so you can edit the URLs to be accessible over HTTPS by creating a virtual directory in your IIS web site running under HTTPS that make points to the "cache" directory of the WMPS.
Not sure if this will help, but may be worth a try.
Colin
05-18-2018 06:32 AM - edited 05-18-2018 06:34 AM
Thanks! Frank Mak helped me and we got it to work by doing the following:
Edit service_source_name.xml (service_source is name of WMPS metadata file)
in C:\Program Files\Common Files\Hexagon\Services\Instances\INSTANCE_NAME\cache
(INSTANCE_NAME is name of the instance created in Adminconsole)
replacing http: with https: everywhere in file (each is a URL for a legend icon)
This must be done anytime the map file is remade after a GWS workspace change (the hex strings for starting up)
It worked perfectly and was exciting to see those legend icons appear on my remote machine!
05-20-2018 02:39 PM - edited 05-20-2018 02:40 PM
The solution for the icons work great. Have you been able to get printing to work (i am using GraphMagick) when you go to the site via https: When I go to the site with just the local machine name and no https then printing is great...but when I go through https i get only the wms instance images and no wmps features in my output pdf map.