Usage Note 44892: A "previously failed to connect" java.lang.RuntimeException error occurs when you log on to SAS® Model Manager
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
| SAS System | SAS Model Manager | Microsoft® Windows® for x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 2.2 | 3.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 2.2 | 3.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2003 for x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2008 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows 7 Enterprise 32 bit | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows 7 Enterprise x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows 7 Professional 32 bit | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows 7 Professional x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows 7 Ultimate 32 bit | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows 7 Ultimate x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows Vista | 2.2 | 3.1 | | 9.3 TS1M0 |
| Windows Vista for x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
| 64-bit Enabled AIX | 2.2 | 3.1 | | 9.3 TS1M0 |
| 64-bit Enabled Solaris | 2.2 | 3.1 | | 9.3 TS1M0 |
| HP-UX IPF | 2.2 | 3.1 | | 9.3 TS1M0 |
| Linux for x64 | 2.2 | 3.1 | | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2011-12-23 13:10:19 |
| Date Created: | 2011-11-16 10:00:29 |
