Diagnosing and resolving SAS® Enterprise Miner(tm) project creation errors


When creating a new project within SAS Enterprise Miner, you might encounter an error message. This KB article describes how to diagnose and resolve errors that occur while creating a project within SAS Enterprise Miner 7.1 and later. Several common error messages are addressed. If the specific error that you encounter is not addressed below, then complete the steps in the Collect data for further investigation section and contact SAS Technical Support.

Diagnosing and resolving "The application could not log on to the server. The server process did not start."

Error

The application could not log on to the server. The server process did not start.

Steps to diagnose and resolve

There are a number of possible causes for this error message. Complete the following steps to diagnose and resolve the cause of the error message:

  1. Check the following articles to see whether any apply to your specific situation:
     
    • SAS KB0036252, "An 'application could not log on to the server ... server process did not start' error occurs when you create or open a project"
    • SAS Note 50479, "Creating a new project generates the error 'The application could not log on to the server ... The server process did not start ...'"
  2. If any of these articles apply to your situation, then try the resolution steps.
  3. If none of these articles apply, or if the issue persists performing the resolution steps, then collect the requested information in the Collect data for further investigation section below. Then, contact SAS Technical Support.

Diagnosing and resolving 'The application could not log on to the server. The server process terminated...'

Error

The application could not log on to the server. The server process terminated unexpectedly with exit value ###.

Steps to diagnose and resolve

In the error message above, the ### represents any numeric exit value that is displayed in the error message. A number of different exit values are displayed because there are a number of possible causes for this error message. Complete the following steps to diagnose and resolve the cause of the error message:

  1. If the exit value is 115, then see SAS Note 54722, "Creating a project gives 'Error: The application could not log on to the server ... The server process terminated unexpectedly with exit value 115'"
  2. Collect the requested information in the Collect data for further investigation section below if either of these conditions is met: 
      • The exit value is something other than 115.
      • The issue persists after completing the resolution steps.
  3. Then, contact SAS Technical Support.

Diagnosing and resolving 'The application could not log on to the server. No server is available now...'

Error

The application could not log on to the server. No server is available now. Please contact your administrator.
 
Resolution
See SAS Note 48060, "The Create New Project Browse button gives an 'application could not log on to the server.' error."

Diagnosing and resolving 'The application could not log on to the server "localhost:0"...'

Error

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

Resolution

See SAS KB0036466, "SAS Enterprise Miner Workstation might display an error when creating a project: The application could not log on to the server 'localhost:0'."

Diagnosing and resolving 'While trying to read from the file "...\projectServerInfo.xml"..."NO_FILE".'

Error

While trying to read from the file "...\projectServerInfo.xml" the following problem was encountered "NO_FILE".

Steps to diagnose and resolve

There are two primary causes for this error message: an incomplete installation of SAS Enterprise Miner or an expired license for SAS Enterprise Miner. Complete the following steps to diagnose and resolve the cause of the error:

  1. Generate the log for the "emproj" code (as found in step 5 in the Collect data for further investigation section below). Search the log for one of the following sets of errors:
     
    • ERROR: Catalog SASHELP.EMWIP does not exist.
      ERROR: Cannot open %INCLUDE file EMPROJ.

      If the "emproj" log includes these errors, then the cause is an incomplete installation of SAS Enterprise Miner. The steps to correct an incomplete installation of SAS Enterprise Miner are located in article:

      SAS KB0036251, "Creating a new project gives a 'NO_FILE' error."

      This article also includes another method (namely, inspecting the filesystem) to determine whether the installation is incomplete.
       
    • ERROR: The SAS Enterprise Miner product with which the procedure is associated is either not licensed for your system or the product license has expired. Please contact your SAS installation representative.
      ERROR: Cannot open SASHELP.EMWIP.EM_PROJECT.SCL.

      If the "emproj" log includes these errors, then the cause is an expired license for SAS Enterprise Miner. In order to correct the SAS Enterprise Miner error, you need to apply a license that contains SAS Enterprise Miner and is not expired.

 

2. If the "emproj" log does not contain either of these sets of errors and this SAS Enterprise Miner project-creation error persists, then collect the information that is requested below. Collect the information in addition to the information that is requested in the Collect data for further investigation section, and engage SAS Technical Support.

    1. The log that was generated when running the following code within a SAS session:
      proc setinit; run; proc product_status; run;

   b. If you are using SAS Enterprise Miner Workstation, then collect screenshots that illustrate the contents of these filesystem locations on the machine where SAS Enterprise Miner Workstation is installed:

 

      c. If you are using SAS Enterprise Miner Client or SAS Enterprise Miner via Java Web Start, then collect screenshots that illustrate the contents of these filesystem locations on the server to which you connect:

Diagnosing and resolving 'This server location is already registered for use...'

Error

This server location is already registered for use, either by another project, or by another SAS application. Or user does not have permission to create project at this location. Try using a different name for your project, or enter a different path.

Steps to diagnose and resolve

There are a number of possible causes for this error message. Complete the following steps to diagnose and resolve the cause of the error message:

  1. Check the following articles to see whether any apply to your specific situation:
     
    • SAS Note 43891, 'The error "server location is already registered for use. . ." occurs when you create a project in SAS Enterprise Miner'
      Note: This article applies only to SAS Enterprise Miner 7.1.
       
    • SAS Note 45425, 'A "server location is already registered for use.." error occurs when you create a project in SAS® Enterprise Miner(tm) 7.1 maintenance one'
      Note: This article applies only to SAS Enterprise Miner 7.1_M1.
       
    • SAS Note 45226, 'A "server location is already registered for use.." error occurs when you create a project'
      Note: The cause that is described in this article is very rare. Further, this article applies only to SAS Enterprise Miner 7.1 and 7.1_M1.
       
    • SAS Note 51567, 'A "server location is already registered for use..." error occurs when you create a new project'
      Note: This article applies only to SAS Enterprise Miner 12.3.
  2. If any of those articles apply to your situation, then try the resolution steps.
  3. Collect the requested information in the Collect data for further investigation section below if either of these conditions is met:
    • None of those articles apply to your situation.
    • The issue persists after performing the resolution steps.
    Then, contact SAS Technical Support.

Diagnosing and resolving 'Specified SAS Server Directory does not exist.'

Error

Specified SAS Server Directory does not exist.

Resolution

See SAS Note 56110, 'Creating a new project gives a "Specified SAS Server Directory does not exist" error when the workspace server is in a lockdown state.'

Collect data for further investigation

Many errors and causes are covered in the sections above. However, some cases require additional diagnostics and review by SAS Technical Support. When engaging SAS Technical Support about these problems, be sure to include the following information:

  1. The release of SAS Enterprise Miner that you are using. Examples: 7.1, 12.1, 12.3, 13.1, 13.2, 14.1, and so on.
     
  2. The variety of SAS Enterprise Miner that you are using:
    • SAS Enterprise Miner Workstation
    • SAS Enterprise Miner Client
    • SAS Enterprise Miner via Java Web Start
  3. A screenshot of the error message that you encountered.
     
  4. If you are using SAS Enterprise Miner Client or SAS Enterprise Miner Workstation, then include the em.ini file.
    Default location: SASHome\SASEnterpriseMiner*\version\em.ini
     
  5. The log that was generated when running the following code within a SAS session:
 
filename emproj catalog 'sashelp.emwip.em_project.source'; %inc emproj; filename emproj; %em_project(action=getServerInfo, outfile=projectServerInfo.xml);
 

If you are encountering an error while creating a project in either of these environments, then run this code in a SAS session on the server.


If you are encountering an error while creating a project in SAS Enterprise Miner Workstation, then run this code in a local SAS session. Example: Start ► All Programs ► SAS ► SAS 9.4 (English)
 

6. Client-side logging from the time of the issue:
 

    1. If you are using SAS Enterprise Miner Client or SAS Enterprise Miner Workstation, then em_console output serves as client-side logging. You can use the instructions that are located in the following article to enable em_console output:

      SAS Note 56002, "Collecting diagnostic output from SAS Enterprise Miner Client or SAS Enterprise Miner Workstation with em_console"

      If you are collecting em_console output to diagnose and resolve an occurrence of 'This server location is already registered for use...', then additional steps are needed.  Complete the steps in the Enable advanced diagnostic output section of SAS Note 56002.
       
    2. If you are using SAS Enterprise Miner via Java Web Start, then Java Console output serves as client-side logging. You can use the instructions that are located in KB0036243 to enable the Java Console output:

      SAS KB0036243, "How to enable logging when SAS Enterprise Miner is launched from Java Web Start"

      If you are collecting Java Console output to diagnose and resolve an occurrence of 'This server location is already registered for use...', then additional steps are needed. Complete the steps in the For detailed Java tracing section of SAS KB0036243.