FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links

Analysis Report Messages

Migration

SAS® BI Report Services

BI Report Services is a component of SAS Web Report Studio. In previous releases, this component was named SAS Query and Reporting Services. For information about administering BI Report Services (for example, setting up a distribution library), see SAS Intelligence Platform: Web Application Administration Guide.

For any updates or hot fixes that are required before you can migrate, see the baseline requirements topic. See also baseline issues for Web Report Studio.

Messages

caution Migration of this SAS environment is not recommended. This version of BI Report Services is not at the required version and needs to be upgraded in order to use the automated migration processes. See http://support.sas.com/migration/utilitynotes support notes for more information. Details: The date in the sas.report.output.management.jar Manifest.mf file indicates that the SAS BI Report Services installation is older than 9.1.3 SP4. The version found in the sas.report.output.management.jar Manifest.mf file is: current-version
Contact SAS and request Upgrading the SAS BI Applications and Applying SAS Service Pack 4

caution Missing configuration property
Verify that the smu.properties file contains the required properties, and run the SAS Migration Utility again.

caution Configuration information for the distribution library cannot be obtained because the BI Report Services configuration file cannot be found in the install folder pathname.
This message indicates that OutputManagementConfigTemplate.xml is not located in the SASQueryAndReportingServices/3.1 folder.

caution The metadata server is down.
Start the metadata server and run the SAS Migration Utility again.

caution There was an error accessing the metadata.
Determine whether the metadata server is running. If the metadata server is stopped, then start it and run the SAS Migration Utility again. If the metadata server is running and you get this error, contact SAS Technical Support.

caution A JDOMException occurred when parsing the OutputManagementConfigTemplate.xml file. Please verify that the encoding type and the content match and if not, modify the file's encoding as needed before executing the migration. The encoding type and content must both be utf-8.
The OutputManagementConfigTemplate.xml file specifies the encoding for the file on the first line. This message indicates that the encoding and the content do not match. The file must be edited and modified so that the content and the encoding type are both UTF-8.

caution OutputManagementConfigTemplate.xml is invalid, the xml descriptor specifies utf-8 encoding but some of the content is not in the utf-8 format.
The OutputManagementConfigTemplate.xml file specifies the encoding for the file on the first line. This message indicates that the encoding and the content do not match. The file must be edited and modified so that the content and the encoding type are both UTF-8.

caution OutputManagementConfigTemplate.xml is an empty file.
Edit the OutputManagementConfigTemplate.xml and add the appropriate content, or refer to the SAS documentation to learn how to configure the product and generate the OutputManagementConfigTemplate.xml file prior to migration.

caution element-name element in OutputManagementConfigTemplate.xml is null.
Edit the file and add the correct value for the specified element.

caution Missing config file element element-name.
Edit the file and add the correct value for the specified element.

caution Unable to retrieve metadata.
Determine whether the metadata server is running. If the metadata server is stopped, then start it and run the SAS Migration Utility again. If the metadata server is running and you get this error, contact SAS Technical Support.

caution The deployed components list is null for the metadata library.
Determine whether the metadata server is running. If the metadata server is stopped, then start it and run the SAS Migration Utility again. If the metadata server is running and you get this error, contact SAS Technical Support.

caution An IOException was encountered when trying to parse the OutputManagementConfigTemplate.xml.
The format of the OutputManagementConfigTemplate.xml file, which is located in the SASQueryAndReportingServices/3.1 folder, is incorrect. Edit the file with an appropriate editor and correct the problems.

caution The file could not be found and will not be migrated.
This message probably indicates that the previous deployment's content is not stored in default locations. If the previous deployment's content is not stored in default locations, it is not migrated to the target SAS deployment.

caution BI Report Services is not installed in pathname.
In order to be migrated, the product must be installed in SASQueryAndReportingServices/3.1 under the <SASHOME> folder. SASHOME is the directory where your SAS products are installed.

caution The distribution library metadata contains a file system path for the distribution library folder which does not exist. Please verify the location of the distribution library and correct the metadata using SASMC.
With SAS Management Console, examine the definition of the library in metadata. The metadata contains a path for the library on disk. Either correct the path in the metadata to point to the correct folder, or create the folder that is specified in metadata and move the distribution library data sets to that folder.

caution Please migrate your datasets in the burst distribution library. The current machine and folder location are machine-and-location. The recommended location for the distribution library folder is on the workspace server machine in the data folder of the server context under pathname. Post migration, please use SASMC to confirm that your burst distribution library points to the correct machine and folder.
In burst mode, the Report Output Generation tool distributes a report to e-mail addresses that are defined in a recipient list. The recipient list, also known as a burst set data set, is stored in the distribution library.

caution An existing distribution library could not be found in the metadata repository with the libref of libref. This libref is defined in the OutputManagementConfigTemplate.xml file and specifies the library which contains distribution list tables for scheduled reports. A new distribution library will be created during the migration process in the metadata repository with a name like SASApp - wrsdist. If you have existing distribution list datasets and would like to use them in your 9.2 configuration, copy them into the folder location referenced by that library and register them with the metadata server. Refer to the migration documentation for more information
For information about specifying the output management library, see SAS Intelligence Platform: Migration Guide.

caution The distribution library full path can not be resolved due to the nature of the metadata.
This message indicates that the previous deployment's distribution library is not stored in the default location. In this case, the library definition is migrated to the target SAS deployment's metadata, but the physical pathname for the library might be incorrect. After migration, check the library's metadata, and correct the pathname if necessary.

caution The metadata library is null.
Determine whether the metadata server is running. If the metadata server is stopped, then start it and run the SAS Migration Utility again. If the metadata server is running and you get this error, contact SAS Technical Support.

caution The distribution library host name in metadata is null.
Determine whether the metadata server is running. If the metadata server is stopped, then start it and run the SAS Migration Utility again. If the metadata server is running and you get this error, contact SAS Technical Support.

caution The distribution library's directory path in metadata is null.
Determine whether the metadata server is running. If the metadata server is stopped, then start it and run the SAS Migration Utility again. If the metadata server is running and you get this error, contact SAS Technical Support.

okay The following Java Batch Servers will be migrated:
This informational message is followed by a list of default Java Batch Servers that can be migrated automatically.

okay Please migrate the Java Batch Servers listed below. These Java Batch Servers will not be migrated.
This message is followed by a list of nondefault Java Batch Servers that an administrator has created. The nondefault Java Batch Servers cannot be migrated automatically. An administrator can re-create these nondefault Java Batch Servers in the target deployment and define them with SAS Management Console.


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.