H90006 |
SAS Forecast Server 12.1 |
Issue(s) Addressed: | Introduced: |
47384 | The Forecasting View does not refresh in SAS® Forecast Studio |
H90001 |
48156 | Polish text in SAS® Forecast Studio 12.1 has been modified to clarify terms |
H90001 |
49306 | The Java Database Connectivity (JDBC) WIPTimeIntervalAnalysisAdapter resources are not properly freed when an internal software failure occurs |
H90001 |
49307 | The %FSLOAD macro fails when you try to load SAS® library definitions with the SAS® Forecasting for Desktop application |
H90001 |
49417 | A Java exception occurs and the SAS® Forecast Server 12.1 DataSpecification folder is deleted when you use the %FSCREATE macro to create a project |
H90001 |
49418 | The SAS® Forecast Server macro %FSRUNPRJ does not work for the METHOD=FORECAST and the IMPORTDATA=YES options |
H90001 |
48526 | Idle SAS® Forecast Studio sessions never time out |
H90002 |
48640 | You cannot use events that are created by using user-defined holidays |
H90002 |
48691 | Multiple occurrences of holiday name appear in the holiday selector |
H90002 |
49770 | Using SAS® Forecast Studio 12.1 with Java 7 |
H90003 |
49926 | The SAS® 9.3 Forecast Studio client cannot be configured to send TCP keep-alive messages |
H90004 |
50293 | SAS® Forecast Studio sets the differencing order of input variable to be the same as the differencing order of the response variable |
H90004 |
50294 | You cannot send TCP Keep Alive messages from the SAS® Forecast Studio 12.1 client to the SAS® Forecast Server 12.1 middle tier |
H90004 |
50133 | SAS® Forecast Studio 12.1 projects fail to open when DataSpecification files are missing |
H90005 |
51591 | The SAS® Forecast Studio 12.1 or later Java Web Start client fails with the error "Unable to load the SAS environment definitions" |
H90006 |
53020 | Errors occur when you try to invoke SAS® Forecast Studio or SAS® Time Series Studio with Java 1.7.0_51 or higher |
H90006 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |