Articles

SAS® Life Science Analytics Framework 5.4.1 - The session editor Find dialog box does not automatically populate with the selected text

Home page controls are not visible to all users with proper home page administrative access in SAS® Visual Investigator

SAS® DATA Step processing in Hadoop fails if the LIBNAME HADOOP statement contains certain characters or order of options

Custom application themes fail with the error "Unable to reach the theme at url" in SAS® Visual Analytics

The sas-viya-svi-alert-default service remains in a "not ready" state when you upgrade-in-place SAS® Visual Investigator from 23w25 to 25w25

"ERROR: Rename of temporary member for LIBREF.dsetname.DATA failed" occurs when using UNC path names

Valid TKMVSENV options required to enable SAS to run Java applications

What does the following message mean, and how does it affect my results? NOTE: MERGE statement has more than one data set with repeats of BY values.

Rebuild the SAS® Content Server search indexes

"Warning: Variable...already exists on file..." occurs when you use SAS/ACCESS® Interface to Microsoft SQL Server

The error "Insufficient authorization to access..." occurs when you use bidirectional line switched ring (BLSR) to allocate temporary SAS® data sets

The protobuf-java version that SAS® Fraud Management uses is not current

The Sort action is unavailable for the attributes columns on the "Published Columns" tab

The Upload to LASR task fails and returns the error "Unable to locate any LASR libraries. This task requires LASR Library"

Negative values appear for distinct counts in SAS® Visual Analytics reports

Confidence limits in the OUTSURV= data set in PROC LIFETEST are log-log transformed limits beginning in SAS® 9.1

Assign a specific folder location for each user that uses a custom Work location for SAS® Foundation

ADLM seen in MPRINT output of SAS® log when PROC IMPORT or PROC EXPORT is inside a macro

The automation interface in SAS® Fraud Management allows you to check out and assess a closed alert whose contact value is not set

A dynamic allocation failure in SAS® 9.4 TS1M2 causes a system abend 378 when system option FILEMSGS is set