As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.


Here are some tips for How to share your SAS knowledge with your professional network.


Difference between revisions of "Errors"

From sasCommunity
Jump to: navigation, search
(added ERROR 180-322, wrote brief intro, minor gardening)
Line 1: Line 1:
 +
This page documents some common errors in [[SAS]], and provides some pointers for resolution.
 +
 
== Cannot Start SAS ==
 
== Cannot Start SAS ==
  
Line 33: Line 35:
 
Solution.2: when running from a network drive such as Citrix,
 
Solution.2: when running from a network drive such as Citrix,
 
make sure the '''My Computer''' has the correct setting:
 
make sure the '''My Computer''' has the correct setting:
 
  
 
<pre>
 
<pre>
Line 41: Line 42:
 
== Macro statements ==
 
== Macro statements ==
  
Missing semicolon at end of assignment statement
+
Missing [[semicolon]] at end of assignment statement
  
 
<pre>
 
<pre>
Line 51: Line 52:
 
== SQL ==
 
== SQL ==
  
search SAS-L archives for:  
+
search [[SAS-L]] archives for:  
  
 
subject: PROC SQL ERROR 65-58: Name too long
 
subject: PROC SQL ERROR 65-58: Name too long
  
 +
== ERROR 180-322: Statement is not valid or it is used out of proper order. ==
 +
[http://blogs.sas.com/content/sasdummy/2016/08/25/error-180-322-missing-semicolon/ This SAS blog post] tells the interesting story of this common error message that often means "you forgot a semicolon!"
  
--macro maven == the radical programmer 11:28, 8 November 2008 (EST)
 
 
[[Category: Best Practices]]
 
[[Category: Best Practices]]
 
[[Category: Guides]]
 
[[Category: Guides]]

Revision as of 08:50, 26 August 2016

This page documents some common errors in SAS, and provides some pointers for resolution.

Cannot Start SAS

ERROR: Invalid physical name for library SASUSER.
FATAL: Unable to initialize the options subsystem.
ERROR:   (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
UNABLE TO INITIALIZE THE SAS KERNEL

Cause: invalid argument to option SASuser in Primary Configuration File:

  •  !SASroot\nls\en\SASv9.cfg
/* name: Primary Configuration file for SAS v9.1.3 or SAS v9.2 */
/* Setup the default SAS System user profile folder */
-SASUSER "?CSIDL_PERSONAL\My SAS Files\9.1"

/* Setup the MYSASFILES system variable             */
-SET MYSASFILES "?CSIDL_PERSONAL\My SAS Files\9.1"

Solution.1: add these lines to your Secondary config file:

/* name: Secondary Config File !SASroot\SASv9.cfg */
/* [snip] */

-SASUSER        'C:\temp\My SAS Files\9.2\'
-SET MYSASFILES 'C:\temp\My SAS Files\9.2\' /* *** */

Solution.2: when running from a network drive such as Citrix, make sure the My Computer has the correct setting:


Macro statements

Missing semicolon at end of assignment statement

1  %Let Test1 = missing semicolon
2  %Let Test2 = has semicolon;
ERROR: Open code statement recursion detected.

SQL

search SAS-L archives for:

subject: PROC SQL ERROR 65-58: Name too long

ERROR 180-322: Statement is not valid or it is used out of proper order.

This SAS blog post tells the interesting story of this common error message that often means "you forgot a semicolon!"