Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile
• My SAS

• Print  |
• Feedback  |
• Share

  • E-mail
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When you create a SAS Forecast Studio 3.1 project by using the %FSCREATE macro with RUN=NO option, the newly created project does not run when you use the %FSRUNPRJ macro.

If you try to run the project with the %FSRUNPRJ macro, the following exception occurs in the SAS log:

NOTE: Could not initialize classpath.  Classpath variable is not set.
ERROR: Exception in fsrunprj
ERROR: RemoteException occurred in server thread; nested exception is:
 
        java.rmi.RemoteException: Can not open project because it was not yet forecasted.

        Wrong Stage: 0; nested exception is: 

        java.lang.IllegalStateException: Can not open project because it was not yet forecasted.

        Wrong Stage: 0

java.io.FileNotFoundException: ?/SAS_ForecastStudio_Lock_0 (No such file or directory)

     at java.io.FileOutputStream.open(Native Method)

     at java.io.FileOutputStream.(Unknown Source)

     at java.io.FileOutputStream.(Unknown Source)

     at com.sas.analytics.forecasting.rmi.ForecastingSessionRmi.getUniqueClientUserID(ForecastingSessionRmi.java:2503)

     at com.sas.analytics.forecasting.rmi.ForecastingSessionRmi.(ForecastingSessionRmi.java:174)

     at com.sas.analytics.forecasting.rmi.ForecastingSessionRmiLoader.createForecastingSession

To enable the project to run with the %FSRUNPRJ macro, use either of the following methods:

• Use Base SAS^® software to run the CREATE_PROJECT_IMPORT_DATA batch code. This batch code is located in the newly created SAS Forecast Studio project directory.
• Open the project in SAS Forecast Studio 3.1, which prompts you to run the project for the first time.

Note: For SAS^® 9.3, when you create a SAS Forecast Studio 4.1 project with the %FSCREATE macro and the RUN=NO option, you do not have to run the CREATE_PROJECT_IMPORT_DATA batch code. The project will run successfully with the %FSRUNPRJ macro. However, be aware that the same Java exception message still appears in the log.

Operating System and Release Information

When a Forecast Studio 3.1 project is created using the FSCREATE macro with RUN=No, the newly created project will not run using the FSRUNPRJ macro.

The following exception occurs in the SAS log:
>


NOTE: Could not initialize classpath.  Classpath variable is not set.

ERROR: Exception in fsrunprj

ERROR: RemoteException occurred in server thread; nested exception is:
 
        java.rmi.RemoteException: Can not open project because it was not yet forecasted.

        Wrong Stage: 0; nested exception is: 

        java.lang.IllegalStateException: Can not open project because it was not yet forecasted.

        Wrong Stage: 0

java.io.FileNotFoundException: ?/SAS_ForecastStudio_Lock_0 (No such file or directory)

     at java.io.FileOutputStream.open(Native Method)

     at java.io.FileOutputStream.(Unknown Source)

     at java.io.FileOutputStream.(Unknown Source)

     at com.sas.analytics.forecasting.rmi.ForecastingSessionRmi.getUniqueClientUserID(ForecastingSessionRmi.java:2503)

     at com.sas.analytics.forecasting.rmi.ForecastingSessionRmi.(ForecastingSessionRmi.java:174)

     at com.sas.analytics.forecasting.rmi.ForecastingSessionRmiLoader.createForecastingSession

Work around:
In order to run the project with the FSRUNPRJ macro, the CREATE_PROJECT_IMPORT_DATA batch file, located in the newly created Forecast Studio project directory, must be ran first; or the project must be opened in Forecast Studio and run there first.
 

In SAS 9.3 / Forecast Studio 4.1, when a project is created with FSCREATE where run=no, the project will run using the FSRUNPRJ macro without running the CREATE_PROJECT_IMPORT_DATA. However, even though FSRUNPRJ runs, it produces the same java exception and the same �Can
not open project because it was not yet forecasted.� error that comes out in FS 3.1� but the project does run.