LASR Analytic Server - not starting

[woo]

LIBNAME mylib SASIOLA  TAG=mylib  PORT=10121 HOST="compute-servername.com"  SIGNER="https://midtier-alias.com:443/SASLASRAuthorization" ;

+

library has correct "data server" definition defined. i also checked that none other same engine library has same tag name

we have alias in place for server names - is that a problem? if that is the case then i believe "server definition" + authorization service definition needs to be changed with alias name instead straight server name, isn't it?

[woo]

sorry, i overlooked. server definition and "lasr authorization service" definition is correct, no alias name mentioned anywhere for any midtier server.

so problem still there, somehow display libname statement showing SIGNER="https://midtier-alis:443/SASLASRAuthorization" ;

not sure where it is coming from...

[Donna_SAS]

I am assuming that these tasks previously worked as expected in your deployment.

You indicated that you have changed some components of the configuration, including the proxy server.

I recommend that you open a discussion with SAS Technical Support.  Be sure to provide specifics about your OS and infrastructure, as well as changes you have made to the SAS configuration.

https://support.sas.com/en/technical-support/contact-sas.html

[alexal · Accepted solution]

@woo,

If you open a track and send me a number, I can schedule a WebEx with you next week.