BookmarkSubscribeRSS Feed
Ivan_Vovkanych
Fluorite | Level 6

Hello,

1. I am trying to set up Model Manager 12.1 (sas9.3). When trying to launch the application via Web Start http://hostnamet:8080/SASModelManagerJWS/Status (I am using actual hostname here). I am getting the following error:

environment error.png

My Web Start Settings:

Java Web Start Config.PNG

However the http://hostname:8080/SASLogon/sas-environment.xml is accessible via browser.


The script of the environment file:

"

<environments xmlns="http://www.sas.com/xml/schema/sas-environments-9.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sas.com/xml/schema/sas-environments-9.2 http://www.sas.com/xml/schema/sas-environments-9.2/sas-environments-9.2.xsd ">

<environment name="default" default="true">

<desc>Default SAS Environment</desc>

<service-registry interface-type="soap">

http://hostname:8080/SASWIPSoapServices/services/ServiceRegistry

</service-registry>

</environment>

</environments>

"

2. When I am trying to open the software with the client application (on Windows) I get the following error:

SAS MM client error.PNG

The log of the error is attached.

The log says:

"

java.lang.RuntimeException: java.lang.RuntimeException: com.sas.analytics.modelmanager.core.AuthorizationException: The application could not connect to the SAS Metadata Repository "dav://budsas20.finalyse.group:8080/SASContentServer/repository/default/ModelManager".

Make sure that the SAS Content Server is available, and that the user is a member of a SAS Model Manager group.

"

I have validated the Content Server via Management Console. The user I am using is in the Model Manager Administrator group (actually I added my user to all the MM groups and roles via Management Console)

The ModelManager.ini configuration file for the windows application is the following:

"

[properties]

MASTERPROP="C:\Prg\SASHome\sassw.config"

[default]

startdir=<LAUNCHERDIR>

applogloc=

launchercmd=<JREHOME>

JavaArgs_1=-Xms128m

JavaArgs_2=-Xmx512m

JavaArgs_3=-Dsas.env.definition.location="<SASENVIRONMENTSURL>"

JavaArgs_4=-Djava.system.class.loader=com.sas.app.AppClassLoader

JavaArgs_5=-Dsas.ext.config="<SASHOME>\sas.java.ext.config"

JavaArgs_6=-Dsas.app.launch.config=picklist

JavaArgs_7=-Dsas.app.repository.path="<VJRHOME>\eclipse"

JavaArgs_8=-Dsas.app.class.path=.;"C:\Prg\SASHome\SASModelManagerClient\12.1\build"

JavaArgs_9=-Dsas.app.launch.picklist=picklist;"help\primary.picklist"

"

And the sassw.config file is the following:

"

[properties]

JREHOME=C:\Program Files (x86)\Java\jre1.6.0_24\bin\java.exe

SASHOME=C:\Prg\SASHome

DPLMTREGLOC=C:\Prg\SASHome\deploymntreg

SASENVIRONMENTSURL=http://hostname:8080/SASLogon/sas-environment.xml

VJRHOME=C:\Prg\SASHome.\SASVersionedJarRepository

Classpath=-cp "<VJRHOME>/eclipse/plugins/sas.launcher.jar"

MainClass=com.sas.analytics.app.mds.MDSApp

"

Do you have any ideas what might be the problem?

Thank you

4 REPLIES 4
jakarman
Barite | Level 11

Why is the name in the popup hostname and you are using everywhere localhost?  Some java deployment failed?

---->-- ja karman --<-----
Ivan_Vovkanych
Fluorite | Level 6

Hostname=localhost=my host server. java is working fine

jakarman
Barite | Level 11

I made the notice as your are using both names. I do not expect the name hostname is valid hostname. It shows in the model manager checkpage and not your name localhost.

---->-- ja karman --<-----
Ivan_Vovkanych
Fluorite | Level 6

Thank you for considering this question. In terms of the Windows client the problem was with post configuration of Model Manager. The action that was missing:

since I selected to not automatically deploy the SAS Web Applications, manual steps were required to ensure the proper content is loaded to the SAS Content Server. The file, .../Lev1/Web/Utilities/manualLoadContent.sh, has been created to facilitate this process. I had to run the file and modify sas sassw file in the client folder.

Still can not access Model Manager via a web application. The error message with the inability to find the environment file even though I added path to environment file in the Management Console.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 3763 views
  • 0 likes
  • 2 in conversation