SAS Visual Analytics unable to download maps for GeoMap features

[mwong]

SAS VA is uanble to download maps from the SAS servers.  We have been working with SAS' technical support for almost two weeks now and we still do not have a resolution to the issue. 

I followed the instructions on this page:  http://support.sas.com/kb/52/133.html and sent tech support a copy of the wrapper.conf file, screenshots, and the xml file from running the network profiling session using the F12 Developer tools in Internet Explorer.  But we are still unable to resolve this issue.

We have a single non-distributed windows environment of SAS VA with IWA implemented.  When I updated the wrapper.conf file to use the ip address of the machine as instructed on that page (wrapper.java.additional.nn=-Dhttp.nonProxyHosts="localhost|127.0.0.1|host-name|IP-address-of-middle-tier-machine") , SAS VA returns an authentication failed message when a user tries to login.  From the url, the message was returned from j_spring_cas_security_check.  At this point, no one can log in to use SAS VA.

So I reverted back to using the alias instead of the ip address and added the userProxy and userPassword option to the wrapper.conf file but maps are still not being downloaded.  If I keep refreshing the page, the maps sometimes will make an appearance but not long after that (probably ten minutes or so), the maps disappears again. 

I ran the network profiling scan and saw that it is getting a HTTP 407 GET error:

.../CrossDomainProxyServlet?destUrl={sasenc}560B7D4B1015D5510C353C692E176D703437BBB1537EE64E1411.....

Has anyone encounter similar issues and if so, are there any resolutions to this?  This is causing a lot of frustration and I have already started using Microsoft PowerBI and PowerMap to do the mapping but we want to be able to do the mapping in SAS VA.

Thanks.

[AnnaBrown]

Hi mwong,

Thanks for posting your challenge to the community! I understand from Tech Support that you've resolved the issue by tweaking some items specific to your environment - glad to hear it.

I hope to "see" you again on the community soon.

Anna

[mwong · Accepted solution]

Yes, the issue was resolved on Friday last week.  Meant to post the solution to this issue since I wasn't able to find a solution in the community.

Here is the solution for anyone else who is experiencing the same issue.

The wrapper.conf file needs to include the following lines:

wrapper.java.additional.nn=-Dhttp.proxySet=true
wrapper.java.additional.nn=-Dhttp.auth.ntlm.domain=<domain>
wrapper.java.additional.nn=-Dhttp.proxyUser=<username>
wrapper.java.additional.nn=-Dhttp.proxyPassword=<password>
wrapper.java.additional.nn=-Dsas.flex.ntlmKerberosSupport=true

[AnnaBrown]

Thanks for posting the solution, mwong!

[abcde]

Check this http://support.sas.com/kb/52/133.html