Good morning, experts,
It appears that my development environment has disappeared from my list of environments when I open up EM 14.1. The sas-environment.xml file seems to be fine - I was able to change the PROD definition's name to "PROD TEST" and the change got picked up the next time I opened up EM.
Opening up em_console.exe, I saw this message in the log:
2018-12-11 11:11:21,170 DEBUG SystemPropertyDiscovery - found URL [https://my-web-server:8343/sas/sas-environment.xml]
2018-12-11 11:11:21,170 DEBUG SystemPropertyDiscovery - Checking system property [env.definition.location]
2018-12-11 11:11:21,170 DEBUG EnvironmentVariableDiscovery - Checking environment variable [SAS_ENV_DEFINITION_LOCATION]
2018-12-11 11:11:21,170 DEBUG SASSWConfigDiscovery - Java system property sas.home is not defined
2018-12-11 11:11:21,170 DEBUG SASSWConfigDiscovery - Environment variable SASHOME is not defined
2018-12-11 11:11:21,170 DEBUG ValidatingNegotiator - Negotiating with environment manager...
2018-12-11 11:11:22,461 DEBUG ValidatingNegotiator - Validating member environment DEV...
2018-12-11 11:11:23,084 DEBUG ValidatingNegotiator - Basic registry access attempt failed - proxy was not usable
org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [https://my-web-server:8343/SASWIPClientAccess/remote/ServiceRegistry]; nested exception is java.io.IOException: Did not receive successful HTTP response: status code = 404, status message = [Not Found]
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:213)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:145)
at com.sas.svcs.remoting.client.SASClientTicketingProxy.invokeInternal(SASClientTicketingProxy.java:176)
at com.sas.svcs.remoting.client.SASClientTicketingProxy.invokeInternal(SASClientTicketingProxy.java:198)
at com.sas.svcs.remoting.client.SASClientTicketingProxy.invokeInternal(SASClientTicketingProxy.java:198)
at com.sas.svcs.remoting.client.SASClientTicketingProxy.invokeInternal(SASClientTicketingProxy.java:198)
at com.sas.svcs.remoting.client.SASClientTicketingProxy.invoke(SASClientTicketingProxy.java:212)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy1.getServiceByInterface(Unknown Source)
at com.sas.swing.login.negotiate.ValidatingNegotiator.getEnvironments(ValidatingNegotiator.java:92)
at com.sas.swing.login.EnvironmentLogonManager.getLogonTargets(EnvironmentLogonManager.java:171)
at com.sas.swing.login.visual.SwingEnvironmentLogonManager.fireLogon(SwingEnvironmentLogonManager.java:389)
at com.sas.analytics.eminer.visuals.Main.main(Main.java:719)
Caused by: java.io.IOException: Did not receive successful HTTP response: status code = 404, status message = [Not Found]
at org.springframework.remoting.httpinvoker.SimpleHttpInvokerRequestExecutor.validateResponse(SimpleHttpInvokerRequestExecutor.java:179)
at org.springframework.remoting.httpinvoker.SimpleHttpInvokerRequestExecutor.doExecuteRequest(SimpleHttpInvokerRequestExecutor.java:92)
at org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at com.sas.svcs.remoting.aspects.RemoteInvocationInterceptor.invoke(RemoteInvocationInterceptor.java:77)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy0.executeRequest(Unknown Source)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:192)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:174)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:142)
... 12 more
2018-12-11 11:11:23,087 DEBUG ValidatingNegotiator - ...failed
I'm also seeing that on the PROD environment (which appears to be working), if I visit https://my-web-PROD-server:8343/SASWIPClientAccess/remote/ServiceRegistry, I get a 405 error, whereas on DEV, it's a 404.
Can anyone help me make heads or tails of this?
Thanks in advance!
I was able to fix it.
The jaas.config file, located at Lev1/Web/WebAppServer/SASServer1_1/conf had an extra block for PFS, which was confusing things. I deleted the extra block, restarted services, and it worked.
I was able to fix it.
The jaas.config file, located at Lev1/Web/WebAppServer/SASServer1_1/conf had an extra block for PFS, which was confusing things. I deleted the extra block, restarted services, and it worked.
Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.
Register today!Use this tutorial as a handy guide to weigh the pros and cons of these commonly used machine learning algorithms.
Find more tutorials on the SAS Users YouTube channel.