• Print  |
  • Feedback  |

FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links

Analysis Report Messages

Migration

SAS® Web Report Studio

See also SAS Migration Utility issues for BI Report Services, which is a component of Web Report Studio.

For any updates or hot fixes that are required before you can migrate, see the baseline requirements topic.

For properties that you can specify for the SAS Migration Utility during analysis and migration, see the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.

Messages

error Property list file filename does not exist.
A required property file is missing. The script that runs the SAS Web Report Studio and SAS Web Report Viewer migration also generates this file. Therefore, this error suggests that something is wrong with the file system, or perhaps the script was paused between generating the file and executing the SAS Migration Utility logic and the file was deleted prior to executing the SAS Migration Utility logic.

error Style sheet filename, referenced by [filename] does not exist and cannot be migrated.
The LocalProperties.xml file refers to a stylesheet file that does not exist, and which cannot, therefore, be migrated. This message probably indicates that the specification is outdated in the LocalProperties.xml file. Determine whether you can remove the reference or supply the missing stylesheet file.

caution Clustering is enabled for deployments instance-name and disabled for deployments instance-name; choosing to default to clustering enabled.
No action is needed unless this information is unexpected.

caution item-name scheduling type will be selected by default. item-name scheduling is enabled for instance-name and item-name scheduling is enabled for instance-name. If this is a problem, disable scheduling for the deployments you do not want to use for this decision.
Take the action explained in the message if it is appropriate.

caution Scheduling type item-name defined for deployment instance-name not recognized.
Scheduling should be defined as either platform or inprocess. This message indicates that the deployment has something else defined. Investigate the reason for this customization.

caution Removing property property-name from instance-name; its value is illegal and cannot be migrated.
This message indicates that a property associated with the software component of a deployed Web Report Studio or Web Report Viewer instance contains a circular reference. This error in the property probably occurred when that instance was configured. Such a property is defective and cannot be migrated. Check, after migration, that the specified property has been assigned a valid value.

caution Multiple deployed instances of SAS Web Report Viewer were found; this is not a supported configuration.
Multiple deployments of Web Report Viewer were detected. Migration might not succeed. Multiple deployments of SAS Web Report Viewer are not supported in SAS 9.2 and later. Investigate the reason for this customization.

caution This instance is at release number.
Deployments of Web Report Studio were detected, and they are not all at the same version. This is unexpected. Migration will probably work, but this is not a supported configuration. Investigate the reason for this customization.

okay Clustering is disabled for deployments product-name.
No action is needed unless this information is unexpected.

okay Clustering is enabled for deployments product-name.
No action is needed unless this information is unexpected.

okay Clustering is not defined for any deployments.
No action is needed unless this information is unexpected.

okay Default scheduling ports defined as port-number, port-number, and port-number.
No action is needed unless this information is unexpected.

okay Scheduling ports are not defined for any deployments.
No action is needed unless this information is unexpected.

okay item-name scheduling type is enabled for product-name.
No action is needed unless this information is unexpected.

okay Scheduling is not enabled for any deployments.
No action is needed unless this information is unexpected.

okay Copying configuration file
No action is needed unless this information is unexpected.

okay Found configured instance product-name.
No action is needed. This is an informational message.

okay Style sheet file will be migrated.
No action is needed. This is an informational message.

Messages from previous releases

caution not found (MAJOR ERROR: Could not locate 'BIP Tree')
This message indicates that you have improperly edited the previous deployment's repository tree structure. If the folder structure in the repository is not parallel with directories in the external content server, or if the BIP Tree folder is not present, then the Web Report Studio instance that works with the repository in the previous deployment is probably not functioning. In this case, you probably have no content to migrate.

If you do have content to migrate, contact SAS Technical Support. Migration of the repository’s content is not possible with the current repository tree structure. For information about the proper storage of reports and report-related objects, see the chapter "Managing SAS Web Report Studio Content and Users" in SAS Intelligence Platform Web Application Administration Guide.

caution not found (item-name)
Verify that the report repository is running, and that the SAS Migration Utility parameters are correct.

caution An error occurred writing configuration.properties: item-name
This is an I/O error. Investigate the nature of the error, and run SAS Migration Utility again when the problem is resolved.

caution There were 0 roles found to be migrated. This is acceptable if the WRS roles were never created. The following roles were looked for: (role-name).
Verify that none of the specified roles were created. If any were created, contact SAS Technical Support.

caution The instance specified by citationweb.war.file (instance-name) does not exist.
Set the citationweb.war.file to the correct deployment and run SAS Migration Utility again. For more information, see the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.

caution Migration Summary: item-name was scanned for SAS Web Report Studio home folders. (n) were matched to metadata users, and will be relocated into their new home folder. (n) were not matched (possibly users with no metadata account) and will migrate in-place. (n) Metadata roles were located and will be migrated and converted.
No action is needed. In addition to the basic configuration, each SAS 9.1.3 deployment has home folders for users, which are typically located at BIP Tree/Report Studio/Users. The user home folders (for each deployment) are moved to the standard user folder location in the target deployment during migration.

SAS 9.2 and later provides expanded support for roles. For information about role changes in Web Report Studio, see SAS Intelligence Platform: Migration Guide.

caution NOTICE: there are (n) "unmatched" home folders, these are home folders not belonging to a SAS Metadata user (probably "Public users"). They will be migrated "in place", and not relocated to a new SAS 9.2 Home Folder. The file file-name lists each unmatched home folder.
No action is needed. If a user is not defined in metadata, the folder is unmatched. The unmatched SAS 9.1.3 folder is migrated to a different location than the other user folders in the target deployment. In SAS 9.2 and later, the parent folder of the unmatched folder is changed from Users to Users.913. The Users.913 folder is a system folder, which hides it from most applications, but the folder can be seen in SAS Management Console.

caution Did not find subfolder
Check the repository for possible corruption.

caution Stylesheet file-name does not exist and cannot be migrated.
The Web Report Studio deployment apparently references a stylesheet that does not exist. Either ignore this message or fix the deployment configuration files (WebReportStudioProperties.xml or LocalProperties.xml or both), looking for the specified stylesheet name in a sas.wrs.styles.css value.

ok Multiple instances of SAS Web Report Studio were found. This instance will be used for configuration.
No action is needed unless the message indicates the wrong Web Report Studio deployment. If that is the case, set the citationweb.war.file to the correct deployment and run SAS Migration Utility again.

This message is a result of an enhancement in SAS 9.2 and later. Now a single deployment can generally do the same work that was done by multiple deployments in SAS 9.1.3. In your SAS 9.1.3 installation, each deployment includes configuration information (such as scheduling user ID and password). When you migrate to SAS 9.2 or later, the migration creates one deployment. The analysis report identifies the SAS 9.1.3 configuration that will be migrated to the target deployment.

If two SAS 9.1.3 deployments refer to the same repository, the first one that is encountered is used to gather migration data. In this case, see the migration log for more information.

ok Stylesheet file will be migrated.
No action is needed unless the indicated file is not the expected file. If an unexpected file is indicated, check whether the value of citationweb.war.file is correct and points to the correct Web Report Studio deployment.

ok Platform PM scheduling credentials recorded
This message indicates that scheduling credentials exist in the previous deployment. The target deployment of SAS Web Report Studio will use platform process manager scheduling by default.

No action is needed unless platform process manager scheduling is not the correct default for the target SAS deployment. To avoid setting this default, remove the scheduling credentials from the WebReportStudioProperties.xml file that is in the specified location, run SAS Migration Utility again, and verify that the message is no longer present in the Analysis Report.

Here are the properties with the scheduling credentials removed: 

  <wrs.scheduling>
    <LSFSchedulingServerUID>  </LSFSchedulingServerUID>
    <LSFSchedulingServerPw>  </LSFSchedulingServerPw>
  </wrs.scheduling>

Contributing to Migration

The migration team appreciates your feedback. Send e-mail to Migration.Feedback@sas.com with questions and comments for our developers, testers, and writers.