Problem Notes for SAS®9 - 34805: Errors occur in SAS Warranty Analysis when you attempt to use any locales other than en_US

Wed, 27 Jan 2010 13:37:07 EST

Errors occur when you try to use any locales other than en_US in SAS Warranty Analysis. The errors occur because the rich client application in SAS Warranty Analysis supports only the en_US locale. SAS Warranty Analysis

Problem Notes for SAS®9 - 38414: The classification matrix in the Interactive Tree browser might contain incorrect values

Wed, 27 Jan 2010 13:39:38 EST

In the SAS ® Enterprise Miner™ Interactive Tree browser, you can select View ► Classification Matrix to display the classification matrix for the current tree. However, some of the numbe

Problem Notes for SAS®9 - 38440: The Risk Measures table name has been changed to Recent Value

Wed, 27 Jan 2010 15:09:40 EST

In SAS ® OpRisk Monitor, the ";Risk Measures"; table name has been changed to ";Recent Value."; However, the original table name still appears in the user guide. The basic content o

Problem Notes for SAS®9 - 38446: Project Migration does not change the Server name for the Filter and Sort task in SAS Enterprise Guide

Wed, 27 Jan 2010 15:17:18 EST

The Project Migration tool, nor the MigrationWizard.exe, will change the Server for the Filter and Sort task. Currently, the only circumvention is to use the Query Builder task instead of the Filter and Sort task.

Problem Notes for SAS®9 - 38453: Program code saved to the wrong location in SAS Enterprise Guide

Wed, 27 Jan 2010 15:21:30 EST

Saving a Program node to disk using the Save As or Change options in the Program Properties dialog box might not save the file correctly. In some cases, the File path opti

Problem Notes for SAS®9 - 38454: Apparent invocation of macro warning when attempting to run code exported from SAS Enterprise Guide

Wed, 27 Jan 2010 15:27:47 EST

Shared macro code might not be included in code exported from SAS Enterprise Guide using the Export Last Submitted Code or Export Last Submitted Code as a Step in Project features. T

Problem Notes for SAS®9 - 37643: Data definition language (DDL) scripts for SAS Customer Intelligence fail with an authorization error in UNIX operating environments

Wed, 27 Jan 2010 15:39:51 EST

When you execute the DDL script to create the reporting tables for the common data model in SAS Customer Intelligence, the script fails with an authorization error in UNIX operating environments:

Fri, 29 Jan 2010 16:57:04 EST

A timeout error might occur in SAS Model Manager 2.1 when importing a document.

Problem Notes for SAS®9 - 38304: When applying maintenance for SAS 9.2, messages might show that the original installation completed with errors, but the update installs successfully

Fri, 29 Jan 2010 16:58:28 EST

When you apply maintenance, the messages "Completed with errors - Report Fonts for Clients" and "Completed successfully - Report Fonts for Clients (Update)" might appear in the deploymentsummary.html file.

Problem Notes for SAS®9 - 37604: Error \"java.sql.SQLException: ORA-01795: maximum number of expressions in a list is 1000\" might be displayed

Mon, 1 Feb 2010 10:48:37 EST

In SAS ® Size Profiling, the UI cannot display the Data Project detail view for a data project if the data project contains more than 1000 size sets. You will also see the following error message from the UI:

Problem Notes for SAS®9 - 36741: Excel displays an error when you use Japanese Excel with versions 2.1 or 4.2 of the SAS Add-in for Microsoft Office and attempt to change fonts

Mon, 1 Feb 2010 11:29:42 EST

When you use Japanese Excel with versions 2.1 or 4.2 of the SAS Add-in for Microsoft Office installed in a Japanese edition of a Microsoft Windows operating environment, you might encounter the following error when you

Problem Notes for SAS®9 - 18484: An error is logged when SAS Marketing Automation uses its own stored process instead of a user-stored process with an identical name

Mon, 1 Feb 2010 11:50:40 EST

If you create a user-stored process with a name that is identical to a stored process that is owned by SAS Marketing Automation and then refer to the user-stored process from within a Code node in a SA

Problem Notes for SAS®9 - 37506: An \"ERROR: AN UNEXPECTED ERROR HAS OCCURRED IN BPX1SPN WITH RETURN CODE 0XB1B010F\" message displays in the SAS log

Mon, 1 Feb 2010 12:44:24 EST

If the FILENAME PIPE engine is used by a user ID that has an OMVS segment that is defined with a blank PROGRAM parameter, the following error message is generated in the SAS log:

ERROR: AN U

Problem Notes for SAS®9 - 37985: Metadata generation in SAS Customer Intelligence fails with an error if the length of a field name in the underlying database exceeds 28 characters

Mon, 1 Feb 2010 15:05:41 EST

Metadata generation fails if the length of a field name in the underlying database exceeds 28 characters (16 if you are using double-byte characters). The error "java.lang.IllegalArgumentException: An invalid resultset ID was specified." is

Problem Notes for SAS®9 - 37702: The Satterthwaite assessment might be incorrect for a TOST equivalence test

Tue, 2 Feb 2010 11:04:57 EST

For two-sample t tests, when the Pooled equivalence confidence limit falls within the equivalence bounds and the Satterthwaite interval does not, PROC TTEST incorrectly reports an Assessment of ";Equivalent"; for t

Problem Notes for SAS®9 - 38554: OLAP Analyzer requires a long time to open the Sales Summary cube installed with Microsoft Analysis Server

Tue, 2 Feb 2010 13:57:01 EST

The Sales Summary cube, which is included in the Microsoft Analysis Server installation, might take a significant amount of time to open using the OLAP Analyzer. This problem is likely caused by the configuration of th

Problem Notes for SAS®9 - 38096: With SAS Merchandise Planning, all children of a locked parent can be edited when selecting the Copy and Paste functions

Tue, 2 Feb 2010 14:39:31 EST

When using SAS Merchandise Planning, a user is able to edit all children of a locked parent when selecting the Copy and Paste functions. A user should not be able to edit childre

Problem Notes for SAS®9 - 38557: SAS Web Report Studio 4.2 includes level names in group break labels

Tue, 2 Feb 2010 14:45:02 EST

In SAS Web Report Studio 3.1, if you specify to label group break values in an OLAP-based report, the label text includes the hierarchy name and the member values. For example, if you create a group break on Pr

Problem Notes for SAS®9 - 38577: Line thickness and marker size properties might reset to defaults for bar-line charts in SAS Web Report Studio

Tue, 2 Feb 2010 15:01:46 EST

In SAS Web Report Studio, the Line thickness and Marker size property settings for a bar-line chart are sometimes reset to the default values. This problem occurs in bar-

Problem Notes for SAS®9 - 18780: The SAS Add-In for Microsoft Office might install languages that were not selected during the installation process

Tue, 2 Feb 2010 15:01:48 EST

Certain versions of the SAS Add-In for Microsoft Office might install languages in addition to the ones that you selected during the installation process.

SAS ® Add-In for Microsoft Office 2.1

Problem Notes for SAS®9 - 35687: Japanese and Chinese editions of SAS 9.2 do not include the sample SAS programs in the Help menu

Tue, 2 Feb 2010 17:02:53 EST

The problem does not occur in English editions of SAS 9.2. The problem occurs because Japanese and Chinese editions of SAS 9.2 are missing some files.

Problem Notes for SAS®9 - 38455: \"Array subscript out of range\" error when reading SAR data from Red Hat Linux

Tue, 2 Feb 2010 19:33:52 EST

When processing SAR data from Red Hat Linux, you may receive the following error: ERROR: Array subscript out of range at line nnn column nnn.

Problem Notes for SAS®9 - 38445: Variables in some SAS IT Resource Management tables for the collector HPOVPA are incorrectly populated with missing data

Tue, 2 Feb 2010 19:44:34 EST

The following tables may incorrectly display missing values for several variables: Table PCSDSK:
DSKDATE, DSKDAY, DSKINTV, DSKRCTY, DSKSECS, DSKTIME, DSKYEAR Table PCSPRO:

Problem Notes for SAS®9 - 38449: Read Access Violation error in PROC BOXPLOT or PROC SHEWHART

Wed, 3 Feb 2010 06:54:43 EST

When the HAXIS= or VAXIS= option is used on the PLOT statement in PROC BOXPLOT to assign an axis definition, if the corresponding AXIS statement contains a text description suboption after quoted text instead of before it,

Problem Notes for SAS®9 - 38527: PROC X12 crashes SAS session when input data contains all negative values and MODE=MULT is specified

Wed, 3 Feb 2010 06:57:32 EST

If PROC X12 is used to perform a multiplicative seasonal adjustment on a monthly or quarterly series, then the procedure causes SAS to crash and completely close out if all of the data values are negative. If one or more

Problem Notes for SAS®9 - 38530: SUBTRACT adjustments specified in the Forecast Studio interface are not applied

Wed, 3 Feb 2010 06:59:30 EST

When a project is created in Forecast Studio and an adjustment variable is specified with a pre or post subtraction operation, the underlying PROC HPFENGINE code is not correctly created and the specified adjustment is ign

Problem Notes for SAS®9 - 38531: ADJUST statement is ignored if the predefined pre or post adjustment operation is incorrectly specified

Wed, 3 Feb 2010 07:08:06 EST

The ADJUST statement in PROC HPFENGINE supports the following pre and post adjustment operations: NONE, ADD, SUBTRACT, MULTIPLY, DIVIDE, MIN, and MAX. If a pre or post adjustment operation is incorrectly specified in the

Problem Notes for SAS®9 - 37354: A segmentation violation might occur in SAS/ACCESS 9.1.3 Interface to ODBC in a Solaris x64 operating environment

Wed, 3 Feb 2010 08:21:35 EST

A segmentation violation might occur when you use a hybrid ODBC driver in SAS/ACCESS 9.1.3 Interface to ODBC in a Solaris x64 environment.

Problem Notes for SAS®9 - 38521: An error occurs when you use a LIBNAME statement with LDAP authentication to connect to Teradata in UNIX operating environments

Wed, 3 Feb 2010 09:22:13 EST

In UNIX environments, a connection to Teradata fails when you use a LIBNAME statement with LDAP authentication, as shown in the following example:

libname test1 teradata user=' ldap-id

Problem Notes for SAS®9 - 38398: Multiple Teradata sessions are generated when you use either the CONNECTION=GLOBAL option or the CONNECTION_GROUP= option

Wed, 3 Feb 2010 12:06:21 EST

Muiltiple Teradata sessions are generated when you use the CONNECTION=GLOBAL option in multiple LIBNAME statements or the CONNECTION_GROUP= option in a SAS/ACCESS LIBNAME statement from SAS Enterprise Guide .

Problem Notes for SAS®9 - 37881: \"ERROR: Bridge Failure Calling Unknown\" might occur when replaying an ODS Document created with PROC REPORT

Wed, 3 Feb 2010 12:07:16 EST

Replaying a document created with PROC REPORT in a prior session can generate errors.

Problem Notes for SAS®9 - 38008: PROC SUMMARY/MEANS running In-Database in Teradata generates \"A bug in SAS has been encountered\" error

Wed, 3 Feb 2010 13:41:31 EST

PROC SUMMARY/MEANS running In-Database in Teradata generates "A bug in SAS has been encountered" error. Results are not returned from Teradata.

Problem Notes for SAS®9 - 38538: Processing HP-OVPA data might produce an error

Wed, 3 Feb 2010 13:43:01 EST

Processing HP-OVPA data for the PCSTRN table might produce the following error messages: ERROR 180-322: Statement is not valid or it is used out of proper order. ERROR: Error during process DATA step.

Problem Notes for SAS®9 - 36088: A SAS Merchandise Data Integration reclassification is taking a long time to run the mdi_purge_analyze_lv10mast.sas program

Wed, 3 Feb 2010 14:37:13 EST

For a SAS Merchandise Data Integration reclassification, running the mdi_purge_analyze_lv10mast.sas program is taking a long time.

Problem Notes for SAS®9 - 38508: A null-pointer exception might occur after a session time-out in the SAS Stored Processes Web application

Wed, 3 Feb 2010 14:50:03 EST

When you add a Logon button that enables users to log on from a logoff window or from timed-out pages of a SAS Web application, the following error is displayed:

An E

Problem Notes for SAS®9 - 38000: PROC TABULATE might generate malformed output in ODS destinations

Wed, 3 Feb 2010 14:58:10 EST

If default and explicit statistics requested are specified in a TABLE statement, PROC TABULATE might generate malformed output in ODS destinations.

Problem Notes for SAS®9 - 37609: SAS IT Resource Management fails with an error when you process TMS data with version 27.04 of MXG software and DUPMODE=DISCARD

Wed, 3 Feb 2010 15:04:42 EST

A syntax error indicating that unexpected data was found is displayed in the SAS log. The error occurs because of the way SAS IT Resource Management interprets changes for the TMS collector in this version of MXG.

Problem Notes for SAS®9 - 17038: Limited support in SAS 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later

Wed, 3 Feb 2010 16:37:43 EST

SAS 9.1.3 Service Pack 4 running under z/OS operating system releases V1R7 and later has limited support for direct access (BASE engine) bound libraries that reside in DSNTYPE=LARGE after you apply the following hot fi

Problem Notes for SAS®9 - 38473: The rich client becomes unresponsive after you delete a project from the Project workspace in SAS Warranty Analysis

Thu, 4 Feb 2010 10:43:43 EST

The rich client becomes unresponsive after you delete a project from the Project workspace. The Diagnostic Client shows a DeleteProjectCommand running in the interactive jobs. The delete project job eventually times out after several hours without de

Problem Notes for SAS®9 - 38608: Read Access Violation in Task [X12] might occur if both the NOPRINT option and the OUTLIER statement are used

Thu, 4 Feb 2010 11:42:08 EST

If the NOPRINT option is specified in the PROC X12 statement and the OUTLIER statement is also used in the PROC X12 step, then the procedure might abend with the following Read Access Violation error if potential outliers

Problem Notes for SAS®9 - 38368: Incorrect probabilities might be generated from bagging models

Thu, 4 Feb 2010 13:07:43 EST

In SAS ® Enterprise Miner™, bagged models are created by iteratively modeling re-sampled observations. The model from each iteration contributes to the final overall score. Some of the lines in the Fl

Problem Notes for SAS®9 - 20228: Multi-machine sample plans include unsupported products on Linux and HP-UX

Thu, 4 Feb 2010 13:43:21 EST

The multi-tier sample plans included with SAS 9.1.3 include Query and Reporting Services on the server tier. Query and Reporting Services is not currently supported on the Linux or HP-UX PA-RISC platforms. The sa

Problem Notes for SAS®9 - 38475: The labels for cost-related variables display with extraneous text when multi-currency support is enabled in SAS Warranty Analysis

Thu, 4 Feb 2010 14:17:18 EST

For example, the text %ktrim and %kleft should not be displayed in this label: "Unadjusted Total Claim Cost (%ktrim(%kleft(United States Dollars )))" The problem is the result of a syntax error in a compiled macro.

Problem Notes for SAS®9 - 38476: The graph that results from a Pareto analysis has formatting issues in the title and does not display according to the BY variable

Thu, 4 Feb 2010 15:25:52 EST

Pareto analysis results are incorrect when a numeric variable is used as the BY variable. The graph displays with issues because the syntax of the WHERE clause is not correct for a numeric variable.

Problem Notes for SAS®9 - 34955: The SAS Metadata Server stops accepting new client connections and returns an error when too many files are open

Thu, 4 Feb 2010 15:32:03 EST

When there is a lot of activity on the SAS Metadata Server, the server might return the following error: ERROR: Bridge protocol engine socket access method was unable to accept a new client connection, error = 24 (Too many files are open.)

Problem Notes for SAS®9 - 38502: Importing an .xlsx file with variable names longer than eight characters might generate an error in SAS Enterprise Guide

Fri, 5 Feb 2010 13:50:55 EST

When importing an .xlsx file, you might see an error similar to the following:

ERROR: Variable NAME_OF_ is not on file WORK.DSETNAME.

Problem Notes for SAS®9 - 38579: SAS Information Delivery Portal can time-out even when there is activity in the Visual Data Explorer

Fri, 5 Feb 2010 14:00:40 EST

The time-out setting in SAS Information Delivery Portal is not affected by activity in the Visual Data Explorer. So, users who are working with an information map or data exploration in the Visual Data Explorer might

Problem Notes for SAS®9 - 38591: Formatted datetime values in SAS Web Report Studio reports might not display correctly in the SAS Add-In for Microsoft Office

Fri, 5 Feb 2010 14:07:01 EST

Formatted datetime values might not display correctly when viewed in a report displayed in the SAS Add-In for Microsoft Office. Instead of the expected datetime value, the value will be a large numerical value. Current

Problem Notes for SAS®9 - 38597: Multiple Language Support (MLS) OLAP cubes migrated from SAS 9.1.3 might generate errors in Cube Designer in SAS 9.2

Fri, 5 Feb 2010 14:15:52 EST

In SAS 9.2, if you attempt to edit a dimension for an OLAP cube using the Cube Designer wizard in SAS size="-1">® OLAP Cube Studio, you might receive errors similar to the following when se

Problem Notes for SAS®9 - 38601: Error when trying to display RTF results in SAS Enterprise Guide

Fri, 5 Feb 2010 14:22:44 EST

One of the following errors might be generated when you attempt to display RTF results in the SAS Enterprise Guide 4.x Results Viewer and the client machine does not have WINWORD.exe:

Problem Notes for SAS®9 - 38458: SQLPLAN internal errors might occur when you reference a view in a query that has variables that are defined with the the LENGTH= column modifier

Mon, 8 Feb 2010 09:40:12 EST

In Base SAS ® software, SQLPLAN internal errors might occur when the following events take place: You reference a view that has variables that are defined with the LENGTH= modifier. I

Problem Notes for SAS®9 - 38085: BY-line information might be missing from SAS/GRAPH output when using the MINIMAL style

Mon, 8 Feb 2010 09:54:26 EST

BY-line information might be missing from SAS/GRAPH output when using the MINIMAL style.

Problem Notes for SAS®9 - 38206: Table of contents text is illegible in a PDF file created on z/OS

Mon, 8 Feb 2010 10:11:04 EST

Table of contents text is illegible in a PDF file created on z/OS.

Problem Notes for SAS®9 - 38229: Incorrect graphics output is produced when plotting two character variables with ACTIVEX and JAVA

Mon, 8 Feb 2010 10:36:53 EST

Incorrect graphics output is produced when plotting two character variables with ACTIVEX and JAVA.

Problem Notes for SAS®9 - 38604: \"Submit SAS code when server is connected\" does not run correctly when scheduled for batch processing in SAS Enterprise Guide

Mon, 8 Feb 2010 10:50:48 EST

SAS Enterprise Guide 4.2 includes a new option in Tools ► Options ► SAS Programs named Submit SAS code when server is connected . This option takes the place of using the EGAuto.sas f

Problem Notes for SAS®9 - 38617: Location specified in Publish task might not persist in SAS Enterprise Guide

Mon, 8 Feb 2010 11:01:54 EST

In SAS Enterprise Guide, the Location path in the Publish task might reset back to its default path (such as My Folder) instead of maintaining the location that was specified the last time the Publish

Problem Notes for SAS®9 - 38266: Files created with ODS TAGSETS.EXCELXP might not open automatically in Microsoft Excel as they are generated

Mon, 8 Feb 2010 11:17:39 EST

Files created with ODS TAGSETS.EXCELXP might not open automatically when "View results as they are generated" is checked.

Problem Notes for SAS®9 - 38620: Scheduled SAS Enterprise Guide project might not send e-mail

Mon, 8 Feb 2010 11:18:00 EST

In SAS Enterprise Guide, scheduled projects that include the E-mail as a Step in Project task might not generate the e-mail. This behavior will happen if you schedule the process flow instead of scheduli

Problem Notes for SAS®9 - 38612: Poor performance when moving data items in an OLAP-based SAS Web Report Studio report

Mon, 8 Feb 2010 11:51:10 EST

In some cases, after applying a filter to your data, you might see slower than normal performance when moving data items within a crosstabulation table. This delay is likely caused by a new SAS size="-1">®

Problem Notes for SAS®9 - 38244: English version of SAS on Japanese version of Microsoft Windows shows different NEWFILE= behavior for ODS HTML

Mon, 8 Feb 2010 11:59:55 EST

The English version of SAS run on the Japanese version of Microsoft Windows shows different NEWFILE= behavior for ODS HTML.

Problem Notes for SAS®9 - 38644: SAS Web Report Studio might not correctly render values inside of a compute block in a stored process

Mon, 8 Feb 2010 12:02:02 EST

A stored process that includes PROC REPORT code might not render correctly in SAS Web Report Studio. This problem is most likely to occur if the stored process contains characters created inside of a compute block.

Problem Notes for SAS®9 - 31224: Stored processes that include graphs might not display in SAS Web Report Studio if the device is set to ACTIVEX

Mon, 8 Feb 2010 14:45:48 EST

In SAS Web Report Studio, if a stored process includes SAS/GRAPH code, then the graphs might not display correctly or they might not display at all. The exact behavior depends on which version of SAS Web Report Studio that

Problem Notes for SAS®9 -

Problem Notes for SAS®9 - 37071: The host name for the JAAS configuration of application server and remote services must match

Problem Notes for SAS®9 - 38439: Stored processes are missing from portlets after being updated with SAS Enterprise Guide