1 - 10 of top 500 results
Previous   |    1 , 2, 3 ... Last   |    Next >
Sort by:
Date | Relevance


40501 - SASŪ 9.2 requires JRE 1.6.0_14 32-bit on Microsoft Windows 7 system and JRE 1.6.0_23 32-bit on Microsoft Windows Server 2008 R2 system- Problem Note

You must use the 32-bit version, even if you are installing on an x64 machine. This SAS note explains the typical error messages that occur if you use the wrong JRE with SAS 9.2 and provides resolutions for the error ...

http://support.sas.com/kb/40/501.html, 45KB


36058 - The installation might fail when you install SASŪ 9.2 Foundation from a SAS Software Depot if the fully qualified pathname is too long- Installation Note

When you install SAS 9.2 Foundation software from a SAS Software Depot, the installation might fail. If this happens, you will see the following error in the sasinstall log file: PROCFILES: -> The following error ...

http://support.sas.com/kb/36/058.html, 28KB


45492 - An INSTALn job fails and errors occur when you attempt to install SASŪ 9.3 or SASŪ 9.4 on a z/OS platform- Installation Note

Occasionally during the installation of SAS 9.3 or SAS 9.4 on a z/OS system, one of the installation jobs fails and a message similar to the following appears: NOTE: SAS DATA LIBRARY (HFS DIRECTORY) /tmp/ ...

http://support.sas.com/kb/45/492.html, 31KB


31854 - WRITE= and ALTER= passwords ignored for SASŪ Scalable Performance Data Server tables- Problem Note

Up to and including SPD Server 4.4, assigning a WRITE= or ALTER= password to a table accessed via the SASSPDS engine has no effect. The table can be written or deleted without specifying the corresponding password. To ...

http://support.sas.com/kb/31/854.html, 29KB


54358 - Incorrect score chi-square values with SELECTION=SCORE and extremely ill conditioned data- Problem Note

When using the best subset selection method (SELECTION=SCORE option) in PROC LOGISTIC, if the data in the candidate predictors are extremely ill-conditioned then the score chi-square statistics reported in the

http://support.sas.com/kb/54/358.html, 33KB


54123 - SQL queries against a DB2 database fail in SASŪ Anti-Money Laundering- Problem Note

A reference to a non-existing FSK_USER table in sasaml.db2 is causing the failure.

http://support.sas.com/kb/54/123.html, 31KB


11460 - Incorrect results or an abend might occur when bulk loading to an existing DB2 table- Problem Note

In SASŪ 9.1, using BULKLOAD=yes to insert new rows into an existing DB2 table might lead to unexpected results or to an S0C4 abend. Unexpected or Incorrect Results Occur Unexpected results occur when the input data set ...

http://support.sas.com/kb/11/460.html, 30KB


54019 - Avast! antivirus software quarantines modules that are required by the SQL procedure in Windows operating environments- Usage Note

PROC SQL terminates when required modules have been quarantined by avast! antivirus software in Windows environments. When avast! antivirus software quarantines modules that PROC SQL relies on, it removes them from the ...

http://support.sas.com/kb/54/019.html, 30KB


53896 - The Interactive Grouping node Count and Non Event Count values might be incorrect when a Special Codes Data Set is specified- Problem Note

The Interactive Grouping node in SASŪ Enterprise Miner? has a Special Codes Data Set property. The property enables you to specify the name of the data set that is used to map values to the corresponding special ...

http://support.sas.com/kb/53/896.html, 31KB


53732 - A PROC SQL query might return incorrect results in dynamic locking domain in SASŪ Scalable Performance Data Server- Problem Note

If you are running more than one client session where one session is querying a table while another is performing UPDATE or APPEND operations, you might see incorrect results.

http://support.sas.com/kb/53/732.html, 28KB

1 - 10 of top 500 results
Previous   |    1 , 2, 3 ... Last   |    Next >