Problem Note 37580: Exiting the user interface while optimization is running results in subsequent logon issues
 |  |  |  |  |
In the SAS® Revenue Optimization Suite (SAS® Markdown Optimization, SAS® Regular Price Optimization, SAS® Promotion Optimization) and in SAS® Size Profiling, if you exit the user interface (UI) while optimization is occuring, you might prevent all users from being able to logon to the solution.
The UI appears to be attempting a logon. You might also see error messages similar to the following in the distudio.log:
ERROR main com.sas.solutions.di.studio.runtime.internal.StudioApplication - connection error com.sas.solutions.di.server.api.ConnectionException: Failed to connect to server: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: host_name; nested exception is: java.net.ConnectException: Connection refused: connect] at com.sas.solutions.di.server.api.SessionFactory.connectionException(SessionFactory.java:254) at com.sas.solutions.di.server.api.SessionFactory.createSession(SessionFactory.java:307) at com.sas.solutions.di.studio.ConnectionProfile.createSession(ConnectionProfile.java:175) at com.sas.solutions.di.studio.pool.SessionPool.createGlobalSession(SessionPool.java:225) at com.sas.solutions.di.studio.runtime.internal.StudioApplication.attemptLogin(StudioApplication.java:315) at com.sas.solutions.di.studio.runtime.internal.StudioApplication.displayLoginDialog(StudioApplication.java:282) at com.sas.solutions.di.studio.runtime.internal.StudioApplication.run(StudioApplication.java:180) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) ......
To work around this issue, you must restart the middle-tier server, object spawner, and the metadata server.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Regular Price Optimization | Microsoft Windows Server 2003 Standard Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
| Microsoft Windows Server 2003 Datacenter Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| SAS System | SAS Markdown Optimization | Microsoft Windows Server 2003 Datacenter Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
| Microsoft Windows Server 2003 Enterprise Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Standard Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| SAS System | SAS Promotion Optimization | Microsoft Windows Server 2003 Datacenter Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
| Microsoft Windows Server 2003 Enterprise Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Standard Edition | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 3.2 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| SAS System | SAS Size Profiling | 64-bit Enabled AIX | 1.2 | 2.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
| Microsoft Windows Server 2003 Standard Edition | 1.2 | 2.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 1.2 | 2.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 1.2 | 2.2 | 9.1 TS1M3 SP4 | 9.2 TS2M3 | ||
A fix for this issue for SAS Merchandise Intelligence 3.2 is available at:
http://www.sas.com/techsup/download/hotfix/ro32.html#037580A fix for this issue for SAS Merchandise Intelligence M5 3.2 is available at:
http://www.sas.com/techsup/download/hotfix/ro32m5.html#037580| Type: | Problem Note |
| Priority: | alert |
| Date Modified: | 2009-10-31 09:35:53 |
| Date Created: | 2009-10-26 05:46:25 |