Providing software solutions since 1976
SMU fails if the unrestricted administrative user is also a trusted SAS user.
When you specify DATECOPY in the PROC CPORT statement, catalog entries retain creation and last modified dates. Selecting <b>Properties</b> in the SAS Explorer displays the catalog datetime you imported with PROC ...
40474 - SASŪ BI Dashboard 4.3 is completely new software- Usage Note
Overview With version 4.3, SAS BI Dashboard has been completely rewritten, which means that there are some major usage differences between version 4.3 and version 4.2. This SAS note explains some of those differences, ...
40668 - SASŪ BI Dashboard 4.3 charts might not display labels clearly after migration- Usage Note
When viewing SAS BI Dashboard charts that were migrated from version 4.2 to version 4.3, labels might not display correctly. The following charts might be affected: Bar Chart with reference lines Line Chart Targeted ...
41156 - Migrated SASŪ BI Dashboard content does not support user customizations- Usage Note
In SAS BI Dashboard 4.2, you could enable users to make customizations to their view of indicators. This feature is no longer available in SAS BI Dashboard 4.3. In addition, any user customizations made in version 4.2 ...
After upgrading from SAS BI Dashboard 4.2 to SAS BI Dashboard 4.3, you should view the migrated content in order to make sure that it displays correctly in version 4.3. Because version 4.3 is completely new software, ...
If you attempt to migrate a SAS Enterprise Guide project using the Migration Wizard found in the default installation directory for the SAS Add-In for Microsoft Office (C:\Program Files\SAS\Add-InForMicrosoftOffice\4.2 ...
39556 - Migrated SASŪ BI Dashboard 3.1 data models should be reviewed in SAS BI Dashboard 4.2- Usage Note
If you migrate SAS BI Dashboard content from 3.1 to 4.2, you should review the data models that were moved. Any data models that are based on information maps that have filters applied will not have the filters applied ...
36784 - Some tables do not display results if the section query contains more than 31 categories- Problem Note
In SAS Web Report Studio, if the section query contains more than 31 category data items from a relational information map, then some tables might not display. In the Edit view, the tables appear with a yellow warning ...
35828 - "Cannot open the report xxxxx" after promotion from SASŪ Web Report Studio 3.1 to SAS Web Report Studio 4.2- Problem Note
In SAS Web Report Studio 4.2, you might see an error message that is similar to the following when you attempt to open a multi-section report that has been promoted from version 3.1: Cannot open the report Sales ...
35138 - An error regarding invalid XML characters occurs when upgrading a SASŪ 9.1.3 metadata repository to SASŪ 9.2- Installation Note
In SAS 9.1.3, when the length of an attribute for a metadata object exceeds the documented length for that attribute, the metadata server invokes an overflow algorithm. This overflow algorithm might mark the attribute ...
SASŪ Metadata Server repository files should only be installed on Local paths or high performance, high availability file systems. I/O errors or file locking issues on network file systems might cause interruptions in ...
36771 - Graph images might be missing or errors might occur when distributing a migrated report in SASŪ Web Report Studio- Problem Note
When distributing a migrated report in SAS Web Report Studio, graph images might be missing from the distributed PDF file, and the HTML version of the report might not be distributed at all. Instead, the HTML file ...
36834 - Promoted SASŪ Web Report Studio reports cannot be opened or repaired- Problem Note
If a SAS Web Report Studio 3.1 report contains &, <, or > symbols in a Text Object, header, or footer, you might see an error similar to the following when you attempt to open the promoted report in SAS Web ...
If you migrate or promote a report that is manifesting the problem described in SAS Note 36796, the values in the migrated report become unsynchronized with the selected group break. This problem is in addition to the ...
36560 - Reports are no longer linked after migrating or promoting from SASŪ Web Report Studio 3.1 to SAS Web Report Studio 4.2- Problem Note
In a SAS Web Report Studio 3.1 crosstabulation table, you can create a link that is based on a category data item with an numeric data type. This kind of association is not supported in SAS Web Report Studio 4.2, ...
36080 - After migrating to SASŪ 9.2, an error message is recorded in the SASŪ Migration Utility log file- Problem Note
After migrating SASŪ Metadata Server repositories from SAS 9.1.3 to SAS 9.2, you might see a message similar to this in the log file: 008-12-04 13:09:36,050 [ERROR ] {databuildata.analyzeDI.databuildataAnalyze} <Status ...
35657 - Migrating from OpenVMS Alpha Server Environments to OpenVMS on HP Integrity Servers- Usage Note
Hewlett-Packard offers the following links for making an easy transition from OpenVMS Alpha to OpenVMS on HP Integrity: HP's OpenVMS homepage for OpenVMS Transition Overview Transition Modules Transition Tools ...
36463 - Repair Report wizard in SASŪ Web Report Studio fails with a "java.lang.NullPointerException" error- Usage Note
SAS Web Report Studio 4.2 includes a Repair Report wizard that enables you to repair reports that do not open because they have become separated from their original information maps. This feature is often used after an ...
36075 - "Browser and Platform Reports already exists" might occur when using the Batch Import Tool to import packages- Problem Note
The following error might occur when importing packages into SASŪ Management Console: com.sas.report.repository.RepositoryDuplicateNameException: Browser and Platform Reports already exists. at com.sas.report. ...
35922 - Migrating projects to SASŪ Enterprise Guide 4.2- Problem Note
By design, SAS Enterprise Guide 4.2 will not migrate projects created with versions prior to SAS Enterprise Guide 3.0. To migrate projects created with versions prior to SAS Enterprise Guide 3.0 to SAS Enterprise Guide ...
35673 - Report authors cannot change aggregation settings after migrating to SASŪ Web Report Studio 4.2- Usage Note
After migrating to SAS Web Report Studio 4.2, members of the WRS Report Author role might no longer be able to change aggregation settings for a relational report. In SAS Web Report Studio 4.2, in order to change ...
35674 - Report authors cannot link reports after migrating to SASŪ Web Report Studio 4.2- Usage Note
After migrating to SAS Web Report Studio 4.2, members of the WRS Report Author role might no longer be able to link reports. In SAS Web Report Studio 4.2, in order to see the Report Linking option when you open the ...
35566 - Properties of some identity-based filters are changed after migrating an information map from SASŪ 9.1.3 to SAS 9.2- Problem Note
When you migrate an information map from SAS 9.1.3 to SAS 9.2, the Property value for a filter that is based on SAS.PersonName is changed from SAS.PersonName to The user name as defined in metadata. Here is how the ...
34886 - An error might occur when migrating SASŪ 9.1.3 from a Windows 32-bit platform to SASŪ 9.2 on a Windows 64-bit platform- Problem Note
Migration of SAS 9.1.3 from a Windows 32?bit format platform to SAS 9.2 on a Windows 64?bit format platform might fail if any Foundation repository data sets have been corrupted. During configuration of the metadata ...
