When you launch SAS Forecast Studio for Desktop, the following error might be displayed in a dialog box:

This SAS note addresses some common causes of this error, which can help you diagnose and resolve it.

As the first step, click the Details button in the error dialog box to see what types of errors are listed.

The following errors are common scenarios, and details for diagnosing and resolving each error are explained later in this note:

• Unable to obtain the  data file lock.
• The native implementation module for the security package could not be found in the path.
• The application could not find a command to launch a SAS Workspace Server.
• The application could not log on to the server "localhost:0". Integrated Windows authentication failed.
• An error has occurred while processing your SAS installation data file (SID) for SAS Forecast Studio. The SID for forecaststdw is invalid. Please contact your SAS Installation Representative for assistance.
• The application could not log on to the server. The server process terminated unexpectedly with exit value 115.

Diagnosing and Resolving the Error Unable to obtain data file lock

Error Details

Diagnosing and Resolving the Error

This error usually occurs when there is a presence of one or more lock files in one or more of the following SAS Forecast Studio for Desktop file-system locations:

• C:\Users\user-ID\ForecastStudioDesktop
• C:\Users\user-ID\ForecastStudioDesktop\Environments
• C:\Users\user-ID\ForecastStudioDesktop\Environments\Default

Navigate to these locations and delete such lock files (those that have the .lck and .lock file extensions). Then, relaunch SAS Forecast Studio for Desktop. 

If the issue still persists after you delete the lock file, or if there are no such lock files in any of the locations from above, collect the following items/information:

• the release of your SAS Forecast Studio for Desktop application
• a screen capture showing the error message
• complete details (in text format) with the full stack trace that is shown when you click the Details button
• screen captures showing the contents of the file-system locations that were listed earlier

Then, send all of this information to SAS Technical Support.

Diagnosing and Resolving the Error The native implementation module for the security package could not be found in the path.

Error Details

Diagnosing and Resolving the Error

This error usually occurs when SAS Forecast Studio for Desktop fails to resolve a library path that it needs to access during the launch process. This path is defined by the -Djava.library.path argument in the forecaststdw.ini file, which is located in SASHome\SASForecastStudioforDesktop\release directory. The argument should point to full path of your SASHOME directory, as shown below:

Make sure that the path in your forecaststdw.ini file is valid.

If the issue still persists after you fix the path, or if the path is already valid, collect the following items/information:

• the release of your SAS Forecast Studio for Desktop
• a screen capture of the error message
• complete details (in text format) with the full stack trace that is listed when you click the Details button
• a copy of your forecaststdw.ini file

Then, send all of this information to SAS Technical Support.

Diagnosing and Resolving the Error The application could not find a command to launch a SAS Workspace Server

Error Details

Diagnosing and Resolving the Error

This error usually occurs either when the Prevent access to registry editing tools group policy is enabled on your Windows machine or when your installation is missing the SAS^® Foundation components that are required by SAS Forecast Studio for Desktop.

To resolve the error, follow these steps:

1. Work with your Windows or system administrator to disable the Prevent access to registry editing tools policy if it is enabled. The policy prevents SAS Forecast Studio for Desktop from creating a workspace-server connection during application launch because registry query commands are disabled. To determine whether this policy is enabled on your machine, follow the steps below:
   1. From the Microsoft Windows Start menu, type Run to open the Run command dialog box. In the Open text field, enter gpedit.msc. Then click OK.
   2. In the Local Group Policy Editor window that is displayed, select User Configuration ► Administrative Templates ► System. Check the System pane to see whether the policy Prevent access to registry editing tools is set to Enabled, as shown below. If it is, work with your administrator to disable it.

      



2. Relaunch SAS Forecast Studio for Desktop after you disable the policy. If the issue still persists, you might be missing the SAS Foundation components that are required by SAS Forecast Studio for Desktop. Follow these steps to install the missing components:
    
   1. Navigate to the SAS^® software depot that you use and execute the command setup.exe (via SAS^® Deployment Wizard) as an administrator.
   2. Select Install SAS Software ► Install SAS Foundation and Related Software.
   3. In the Select Products to Install pane, select SAS Foundation and SAS Forecast Studio for Desktop only.
   4. Use the defaults settings for the SAS Foundation products. 
   5. Continue through the remaining panes with appropriate selections.

If the issue still persists after you disable the Prevent access to registry editing tools policy and you install the missing SAS Foundation components, collect the following items/information:

• the release of your SAS Forecast Studio for Desktop
• a screen capture of the error message
• the complete details (in text format) with the full stack trace that is listed when you click the Details button
• a screen capture showing that the Prevent access to registry editing tools" policy is disabled on the machine
• a zipped copy of the C:\Users\user-ID-you-used-for-installation\AppData\Local\SAS\SASDeploymentWizard folder from your machine.

Then, send this information to SAS Technical Support.

Diagnosing and Resolving the Error The application could not log on to the server "localhost:0". Integrated Windows authentication failed.

Error Details

Diagnosing and Resolving the Error

This error typically occurs when there is an issue with the hosts file on your Windows operating system. The hosts file is used to map host names to IP addresses. For SAS Forecast Studio for Desktop to function properly, the operating system must be able to resolve the host name and the keyword localhost to the standard loop-back address: 127.0.0.1.

To resolve the error, follow the steps for editing your hosts file in the Resolve the problem section of SAS KB0036466,  "SAS^® Enterprise Miner(tm) Workstation might display an error when creating a project: 'The application could not log on to the server "localhost:0.".

If the issue still persists after you edit the hosts file, or if your hosts file looks correct, collect the following items/information:

• the release of your SAS Forecast Studio for Desktop
• a screen capture of the error message
• the complete details (in text format) with the full stack trace that is listed when you click the Details button
• a copy of your hosts file
• the output that you receive when you run the ipconfig /all command>

Then, send all of this information to SAS Technical Support. 

Diagnosing and Resolving the Error  An error has occurred while processing your SAS installation data file (SID) for SAS Forecast Studio. The SID for forecaststdw is invalid. Please contact your SAS Installation Representative for assistance.

Error Details

Diagnosing and Resolving the Error

This error typically occurs either when your SAS Forecasting for Desktop license is expired or the software is no longer licensed because you applied a SAS installation data file (SID file) that does not have SAS Forecasting for Desktop. To check the status of the license for your site, you can run the following code in a Base SAS^® (SAS 9.X) session and review the SAS log that is generated by the code.

The log that is generated lists all the SAS products for which your site is currently licensed as well as the expiration date for each product.                                      

If the log shows that your SAS Forecasting for Desktop license is expired, or if SAS Forecasting for Desktop is missing in the list of the SAS products that is returned by the log, you need to apply a valid SID file that includes all your SAS products from the log plus SAS Forecasting for Desktop. Make sure that the SID file is not expired. For details about obtaining and applying an appropriate SID file, see SAS KB0036286, "License file renewal instructions for SAS® 9.4 (TS1M3) and later SAS® 9.4 personal installations in Microsoft Windows operating environment."

If the issue still persists after you apply an appropriate SID file, or if your PROC SETINIT log shows that you have a valid SAS Forecasting for Desktop license, collect the following items/information:

• the release of your SAS Forecast Studio for Desktop application
• a screen capture showing the error message
• complete details (in text format) with the full stack trace that is shown when you click the Details button
• the complete SAS log that is returned by your PROC SETINIT code (from earlier in this note)
• a copy of the SID file you applied (if applicable)

Then, send all of this information to SAS Technical Support.

Diagnosing and Resolving the Error The application could not log on to the server. The process terminated unexpectedly with exit value 115.

Error Details

Diagnosing and Resolving the Error 

This error typically occurs when your Base SAS (SAS Foundation) license is expired. SAS Forecast Studio for Desktop needs Base SAS to function and this error can occur when it fails get a Base SAS session due to license expiration. You can check if your Base SAS license is expired by invoking a SAS 9.4 (English) session directly on the machine. If you get an error message about the current date being past the final expiration date of your SAS system, then that confirms that your license is expired.  

To resolve the error, you need to apply a valid SID file that includes all your existing SAS products, including Base SAS and SAS Forecasting for Desktop. Make sure that the SID file is not expired. For details about obtaining and applying an appropriate SID file, see SAS KB0036286, "License file renewal instructions for SAS® 9.4 (TS1M3) and later SAS® 9.4 personal installations in Microsoft Windows operating environment."

If the issue still persists after you apply an appropriate SID file and your SAS 9.4 (English) session launches successfully, then collect the following items/information:

• the release of your SAS Forecast Studio for Desktop application
• a screen capture showing the error message
• complete details (in text format) with the full stack trace that is shown when you click the Details button
• the complete SAS log that is returned by your PROC SETINIT code (from earlier in this note)
• a copy of the SID file you applied 

Then, send all of this information to SAS Technical Support.

Operating System and Release Information