Thanks Juan.
I am sorry, I am a bit confussed, I might need more information. In the first post you mention that VALIBLA AutoLoad cannot be started, but in your second post you say that it actually brings up the service. What am I understanding wrong?
Actually, since those two scripts are not running we created customized script to start autoload job. Anyways, The error I posted in first post happens while trying VALIBLA script.
Besides this little detail, what you mention is interesting, becasue metadata and scripts must be aligned:
- first check in Web Infrastructure Platform your URLs, specially LASRAuthorization service. Check if it is http or https.
config manager > sas app infrastructure
for LASR authorizations service,
internal connection has - http/real host name/port123
external connection has - https/alias for hostname/port456
- Then, for the LASR server related, it is important that the URL for LAST authorization service should be same http, or https, and
same port number.
under server manager, all server instaces, LASR Analytic server, public lasr, and model risk lasr has http/server host name/ 10011/10031/10121
so I see discrepancies there "config manager > sas app infrastructure" VS "server instance definition under server manager"
... View more