Problem Notes for SAS®9 -

Under certain conditions, incorrect data occurs at the ends of character columns when the data is returned from Oracle views.

Teradata No Primary Index (NoPI) tables are not returned in SAS Explorer or PROC DATASETS search results if you set the SAS_NON_XVIEW_TABLES environment variable to YES.

SAS Studio is unable to load when you use Google Chrome release 67 and above. After you enter your user name and password, the application stops responding and shows a continuous, spinning indicator on the Ini

If you create metadata folders that use special characters, such as hyphens ( - ) or ampersands ( & ), SAS Web Infrastructure Platform Services might fail to properly find or load these folders. SAS

When you autoselect a line of code in SAS Enterprise Guide and attempt to run the code, the application might crash. imgalt="extra char" src="{fusion_61144_8_eg_snip.jpg}" /> If you run SAS Enter

PROC VARMAX might produce incorrect multistep-ahead forecasts if the model includes exogenous variables and one or more of the dependent (endogenous) variables are differenced with the DIF= or DIFY= option in the MODEL statement.

PROC VARMAX issues a warning when the ECM= option is specified in the MODEL statement and only one dependent variable is included in the model.

A memory leak in SAS LASR Analytic Server version 2.8.1, running in distributed mode, might cause a LASR session to fail.

When you use SAS Infrastructure for Risk Management, data might be pulled from the incorrect federated area. This problem occurs when there are two or more federated areas that use the same dynamic LIBNAME statement.

If you select File ? Close Project and the project has temporary data in the WORK library, then the following text appears in a pop-up window:

When you view a SAS ® data set in the data grid, SAS Enterprise Guide might display the following error:

An unexpected error occurred while attempting to read the data

When you open a project in SAS Enterprise Guide, you might see a pop-up message box with one or more notes that are similar to the following:

An unknown error occurred while trying to cr

In SAS Enterprise Guide, the blinking cursor in the Enhanced Program Editor window might disappear even though editor continues to function as expected. The exact cause has not been determined. However, in most c

When you attempt to open any custom task (.dll) file in SAS Enterprise Guide, you might see an error message that is similar to the following:

When you open a SAS Enterprise Guide project, an error similar to the following might occur:

The element with label "label here" of type

In SAS Enterprise Guide, the Find action might not work as expected. This problem occurs whether you use the shortcut combination CTRL+F, or you select Edit ► Find . To fix the problem, follow these

In the SAS Enterprise Guide Query Builder, you might not be able to successfully rename a summary column using the Select Data tab. Specifically, although you can type in a new name, the new name is not retained.

Send To E-mail Recipient might fail with the following message even though Send To E-mail as a Step in Project works fine.

There is no email prog

By current design, after a job, a task, or a SAS program is submitted from SAS Enterprise Guide, you are not able to access data from the file system, a library, the Process Flow, or the Project Tree until the job is finis

The following error might occur when running a Process Flow that contains an Export step:

Unable to export to File_Name. Please be sure the targe

Problem Notes for SAS®9 - 62366: A data integrity issue occurs after you query an Oracle view with an Oracle 12.1.0.2 server or a later server version

Problem Notes for SAS®9 - 61994: Teradata tables with no primary index are not returned in search results from SAS Explorer or PROC DATASETS

Problem Notes for SAS®9 - 62389: SAS Studio stops responding on the \"Initializing\" display when you use Google Chrome version 67 and later

Problem Notes for SAS®9 - 61729: \"Illegal character in the entity name\" error might occur in SAS Web Infrastructure Platform Services if metadata folders contain special characters

Problem Notes for SAS®9 - 61144: SAS Enterprise Guide might crash when you autoselect a line of code

Problem Notes for SAS®9 - 62394: PROC VARMAX generates incorrect multistep-ahead forecasts for some model specifications

Problem Notes for SAS®9 - 59640: PROC VARMAX returns \"WARNING: The ECM option is ignored in the univariate model\"

Problem Notes for SAS®9 - 62436: SAS LASR Analytic Server session terminates with ERROR: Resource is write-locked by another thread

Problem Notes for SAS®9 - 62433: Data is pulled from the incorrect federated area when there are two or more federated areas that use the same dynamic LIBNAME statement

Problem Notes for SAS®9 - 55958: When you close a project, SAS Enterprise Guide does not delete temporary data as described in a pop-up message

Problem Notes for SAS®9 - 55863: SAS Enterprise Guide might display an error in the data grid when you scroll, page up, or page down with certain data

Problem Notes for SAS®9 - 55841: SAS Enterprise Guide might display errors about removing project items

Problem Notes for SAS®9 - 54015: In SAS Enterprise Guide , the blinking cursor might disappear while you are using the Enhanced Program Editor

Problem Notes for SAS®9 - 49975: \"Unable to load file\" message might appear when you attempt to add any custom task to SAS Enterprise Guide

Problem Notes for SAS®9 - 49428: When you open a SAS Enterprise Guide project, you might be alerted that a project element caused a serialization error

Problem Notes for SAS®9 - 47355: CTRL+F might not work in SAS Enterprise Guide

Problem Notes for SAS®9 - 47111: Renaming a column in the SAS Enterprise Guide Query Builder might not work as expected

Problem Notes for SAS®9 - 46823: Send To E-mail Recipient might fail in SAS Enterprise Guide even though Send To E-mail as a Step in Project works fine

Problem Notes for SAS®9 - 46809: SAS Enterprise Guide might lock when a job is running

Problem Notes for SAS®9 - 46676: Export step might cause an error regarding the file already being open even though the file is not being accessed in SAS Enterprise Guide