When logging on to SAS Model Manager, you might receive the following error:

java.lang.RuntimeException: com.sas.apps.session.ApplicationNotInitializedException: 
java.lang.RuntimeException: com.sas.services.ServiceException: 
Previously failed to connect to http://your_server_name_here:port/SASContentServer/repository/default
/ModelManager for sastrust@saspw 
    com.sas.analytics.modelmanager.client.APServerDelegate.connectToServer(APServerDelegate.java:166)
    com.sas.analytics.app.mds.api.RepositoryImpl.(RepositoryImpl.java:144)
    com.sas.analytics.app.mds.MDSApp.startApplication(MDSApp.java:120)
    com.sas.analytics.app.mds.MDSApp.(MDSApp.java:74)
    com.sas.analytics.app.mds.MDSApp.main(MDSApp.java:66)

You receive this error when SAS Analytics Platform is started before your Web application server is fully started. Before starting the SAS Analytics Platform server, check your Web application server log to verify that the server is fully started. (On Windows, the Services window might show that the Status is "Started". However, this Status value is not a true indicator of whether the server is started. You need to check the log.)

An example using JBoss

Verify that JBoss started before you start the SAS Analytics Platform Server service. For this example, the server.log file is located in "C:\JBoss\<jboss-version number>\server\SASServer1\log".

If JBoss started, then the log shows something like this:

2011-05-14 15:23:02,817 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: 
SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 15m:31s:878ms

Operating System and Release Information