Problem Notes for SAS®9 -

In SAS Enterprise Guide, the following error might occur when using the Export Data as a Step in Project task:

The open data operation failed.

The following error might occur when opening a SAS data set from your local PC using SAS Enterprise Guide:

Enterprise Guide cannot open the data fi

In some cases, an output table might not be generated or a table might not automatically open. This will happen when using the option DBIDIRECTEXEC. As a circumvention, change the option to NODBIDECTEXEC. The NOD

Temporary files might remain on the SAS System server even after closing SAS Enterprise Guide. This can happen when using End SAS Process in the Task Manager of SAS Enterprise Guide. There is currently no ci

The following error might be generated when building a query in SAS Enterprise Guide:

Error: Unresolved reference to table/correlation name tab

An error similar to the following might occur when opening or importing a Microsoft Excel file from a UNIX server: An internal ADO data operation has failed. The requested data cannot be displayed. External ta

Null values might not return query results in SAS Enterprise Guide. This will most likely occur for Oracle tables, or other databases that requires a PROC SQL WHERE clause such as one of the following: where CharVar

Queries that contain a join and filter might return unexpected results in SAS Enterprise Guide. This will most likely occur for a LEFT or RIGHT OUTER join that also contains a filter. The reason the results are unexpect

The following error might occur when saving a project after migrating from SAS Enterprise Guide 2.x to 4.1:

Failed to save project. Object reference not set to an instance of an obj

By design, the option to Schedule an Ordered List is not enabled. To circumvent the problem, select and copy the objects from the project and paste them into a new Process Flow. Then arrange them in the order you wish a

Some code might cause a Status of ';RUNNING DATA STEP'; or ';RUNNING PROC proc_name'; and the process might appear to hang in SAS Enterprise Guide. In most cases, the process will complete successfully; however, the Statu

A message similar to the following might be generated running any task or code in SAS Enterprise Guide: %gaccessible; ERROR 180-322: Statement is not valid or it is used out of proper order. NOTE: Line ge

Importing a pipe delimited file may fail when using SAS Enterprise Guide. This will most likely occur when using the Korean version of SAS Enterprise Guide. There is currently no circumvention for the problem.

Using the operator ';Not equal to'; in the Query Builder causes the following message to be written to the SAS System Log of SAS Enterprise Guide 4.1. NOTE: The "&lt&gt" operator is interpreted as "not equa

In SAS Model Manager, when you try to register a SAS Factory Miner project, registering might fail. SAS Model Manager does not produce any input/output variables for the corresponding portfolio, or for any

When you access files through the Server Files and Folders tab under the Navigation pane in SAS Studio, the current focus in the folder tree might be lost when you save a new or existing program. The

Launching SAS Enterprise Miner using Java Web Start in a web browser gives the following error:

HTTP Status 500 - Main JAR either does

The LEAVE and CONTINUE statements generate the following error when they are used with PROC FCMP:

ERROR 180-322: Statement is not valid or it is used ou

The DS2 procedure connects to a data source by using active LIBNAME statements. When a SAS Scalable Performance Data (SPD) Engine library is defined with a LIBNAME statement, the DATAPATH= option must be specif

In SAS Model Manager, running a scoring task against a SAS analytical store file might fail. An error like the following is displayed in the SAS log:

Problem Notes for SAS®9 - 34836: Exporting a data file as .mdb might cause an error in SAS Enterprise Guide

Problem Notes for SAS®9 - 34511: \"Failed to open the data set in READ mode\" for local SAS data set in SAS Enterprise Guide

Problem Notes for SAS®9 - 34153: Option DBIDIRECTEXEC prevents SAS Enterprise Guide from opening tables created by PROC SQL

Problem Notes for SAS®9 - 30755: Temporary files might remain on the SAS server even after closing SAS Enterprise Guide

Problem Notes for SAS®9 - 30688: \"Error: Unresolved reference to table/correlation name table_name\" might occur when building a query in SAS Enterprise Guide

Problem Notes for SAS®9 - 20809: Error opening Microsoft Excel file from UNIX server using SAS Enterprise Guide

Problem Notes for SAS®9 - 20528: Null values might not return query results in SAS Enterprise Guide

Problem Notes for SAS®9 - 20442: Certain join and filters might return unexpected results in SAS Enterprise Guide

Problem Notes for SAS®9 - 19145: Unable to save project after migration in SAS Enterprise Guide

Problem Notes for SAS®9 - 19020: Unable to schedule an Ordered List in SAS Enterprise Guide

Problem Notes for SAS®9 - 18209: Status might hang with RUNNING DATA STEP / PROC in SAS Enterprise Guide

Problem Notes for SAS®9 - 18103: GACCESSIBLE or GOPTIONS might cause syntax errors in SAS Enterprise Guide

Problem Notes for SAS®9 - 18077: Importing a pipe delimited file may fail when using SAS Enterprise Guide

Problem Notes for SAS®9 - 17758: Using \';not equal to\'; operator writes a Note to the SAS System Log in SAS Enterprise Guide

Problem Notes for SAS®9 - 62439: SAS Model Manager fails to register a project from SAS Factory Miner, input/output variables are not produced, no model is imported

Problem Notes for SAS®9 - 62401: The SAS Studio Server Files and Folders tree might lose focus when programs are saved

Problem Notes for SAS®9 - 62329: Launching SAS Enterprise Miner(TM) Java Web Start gives \"error: HTTP Status 500 - Main JAR either does not exist or is not signed ...\"

Problem Notes for SAS®9 - 62392: The LEAVE and CONTINUE statements generate errors when they are used with PROC FCMP

Problem Notes for SAS®9 - 62417: Spaces are replaced with semicolons in pathnames specified with the DATAPATH= option in LIBNAME statements defining SAS® SPD Engine libraries

Problem Notes for SAS®9 - 62435: \"ERROR: Parse encountered identifier when expecting end of input ...\" is displayed when scoring SAS analytical store file model in SAS Model Manager