08-28-2017 10:40 PM
One of our client is using load balancing for their production enviornment that have 3 machines. In order for geospatial portal to work correctly in load balancing configuration, we need to centralize all portal session data.
We start ASP.NET State Service. The portal web.config also has a section about session state setting, but our attempt to use that setting on one machine hasn' t been successful, the portal throws 500 error code when it launches
We also try to configure session state for the portal in IIS instead, it does launch but it looses all defined maps.
Appreciate all insights and suggestions on this matter.
08-29-2017 12:15 AM
Have you checked this topic?
08-29-2017 08:20 PM
Thank you for the reply. I have read the article, but it is still very vague to me and I haven't succeeded, would you mind showing a working configuration example ?
It would be great if I can simulate this on my local succesfully before trying on the real load balancer.
08-30-2017 04:12 AM
Unfortunately I don't have personal experiences in this area but it sounds reasonable to me that this should work:
08-31-2017 08:24 PM
Hi Jan & team,
Thank again for looking at this problem. I found an issue with the instructions from the topics.
Firstly, it seems to assume that user maps are stored in the portal instance itself. However, from version 2015, the user maps are defined in Admin Portal and they are stored at "C:\ProgramData\Hexagon\Geospatial Server\Admin Portal\Maps" and its location is stored in portal's configuration file. So, the path needs to be converted into UNC path; however, I have tried using UNC for the link but still haven't succeeded.
A way to get around that is placed the map content under the portal folder, then as the article mentions, use UNC path for mapStorageFolder parameter; however, it now shows problem initializing map service even though the map is so simple.
Appreciate all suggestions and insights,
08-31-2017 11:47 PM
Thanks for your suggestions, I will notify our documentation team abou the outdated instructions.
Regarding the Portal error - can you see any related error details in the Portal log file?
08-31-2017 11:49 PM
I had same problem using an instance of Geoportal 2015 version. This doesn't happen with an instance of version 2013.
Looking for differences I have found a workaround. It seems that administration console when written default workspace to app_data\configuration\configuration.xml write a extrange path to defaultWorkspaceId value with the unc path, then Geoportal complain when starting about invalid UNC url. I have modified the configuration.xml manually and set defaultWorkspaceId only with ID and not the file specification with path. It seems that if you set only the ID then it looks for mapstoragefolder configured in web.config that accepts the unc path.
09-01-2017 12:19 AM - edited 09-01-2017 12:19 AM
Also, the Portal configuration uses file URI to look for the file locations on the system, there for in case of UNC path, you should notation like this:
Another thing that you have to keep in mind is that if you create a network share, it is accessible only for the user who created it. Here comes a problem with UNC shared which might be tricky to set up for IIS_IUSRS / AppPool identity users. That is why I used a complete path with machine name (IP) in sample above.
09-03-2017 07:26 PM
Hi Jan & team,
I have tried your suggestions but it now shows me error "the starting workspace does not exist". I have tried quite a number of configurations but it hasn't work properly. Wonder whether there is other underlying configurations.
09-05-2017 04:24 AM - edited 09-05-2017 04:37 AM
Disclaimer: Bob already created a support ticket which forced me to actually spend few hours on this This is the current outcome: