• support.sas.com

• Knowledge Base

• Support

• Training & Bookstore

• Happenings

• Support Communities

Resources for Intelligence Platform Migration

• SAS Intelligence Platform: Migration Guide
  
  
• SAS 9.3 Guide to Software Updates
  
  
• Maintenance Release Announcement for SAS 9.2
  
  
• Special Considerations for Customers Upgrading to SAS 9.2
  
  
• Getting from SAS 9.1.3 to SAS 9.2: Migration Tools or Promotion Tools (.pdf) (SGF 2009)
  
  
• Migrating a SAS Deployment to Microsoft Windows for x64 (.pdf)
  
  
• Peaceful Coexistence: Multiple SAS Releases
  
  
• SAS Notes for metadata-based deployments
  
  
• The Lowdown on the Download: What’s Really in My SAS Software Depot and How Did It Get There? (.pdf) (SGF 2010)

Quick Links

• Install Center
• Section 508 Accessibility
• Expanded Table of Contents
• Contact Us

Analysis Report Messages

Migration

Connect Server

SAS/CONNECT® servers enable clients to execute code on a remote host, or to move data between client and server machines.

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

Messages

Conflict over port number found between server-name-1 and server-name-2.

You can ignore this message if server-name-1 and server-name-2 are the same server (for example, Connection: Connect Server and Connection: Connect Server). Contact SAS Technical Support if the two servers are different.

failed to migrate. A connect spawner must be associated with this connect server in the metadata. Note: The metadata of this connect server will migrate with the metadata repository.

When you define a SAS/CONNECT server in SAS Management Console, you can choose whether to use a spawner, script, or SASCMD method to connect to the server:

• If you want to use a spawner to connect to the SAS/CONNECT server in the target SAS deployment, then in the previous deployment, define a spawner that is associated with this SAS/CONNECT server.
• If you want to define the SAS/CONNECT server using a SASCMD or Script signon, then you can ignore this warning message.

When you use the SAS Deployment Wizard in the target SAS deployment, the configration of the SAS/CONNECT server requires the associated Connect spawner information. Without an associated spawner, the configuration will fail. Therefore, when a spawner is not associated with a SAS/CONNECT server, the SAS Migration Utility assumes you will use a SASCMD or Script signon, and omits the SAS/CONNECT server from the migration package to avoid a configuration failure.

For connect server migration, the hot fix E9BC13 needs to be applied on Windows machines that will run both a 9.1 SAS/CONNECT spawner and a 9.2 or later SAS/CONNECT spawner. The hot fix must be applied before running the SAS Deployment Wizard to deploy the 9.2 or later environment.

If your deployment is on Windows and you plan to run both a SAS 9.1 and a SAS 9.2 or later spawner on the same machine, then apply hot fix E9BC13 for Base SAS to the SAS 9.1.3 environment before you run the SAS Deployment Wizard to deploy the target SAS environment.

This warning message always appears in the analysis report, even if you have already applied the hot fix. The SAS Migration Utility cannot determine whether the hot fix has been applied.

Conflicting port values found for servers A and B. Please correct the port values before continuing with migration.

Correct the port values in the previous deployment's metadata (for example, with SAS Management Console) for the two SAS/CONNECT server definitions before you create a migration package with the SAS Migration Utility. If you do not correct the conflicting port values in the previous deployment's metadata, the configuration in the SAS Deployment Wizard will fail.

The server name contains characters not compatible with SAS 9.2. Please remove the incompatible characters from server name before migration.

For SAS/CONNECT, SAS/SHARE, and Operating System Services in migrations to early releases of SAS 9.2, some users can see this message even though no action is needed. The SAS Deployment Wizard corrects the name automatically for this server. You can disregard this error for the SAS/CONNECT, SAS/SHARE, and Operating System Services.

Be aware that you might need to correct the names of other servers before you migrate. The naming convention in the SAS Management Console has changed. In SAS 9.2 and later, the forward slash and backslash are not supported in server names. Other unsupported characters in server names include control characters (e.g., tabs, newlines) and leading or trailing blanks. The name must not be greater than 60 characters, and must be specified (non-null).

The SASCMD value is not specified with the connect server, it is required that this value be defined to successfully validate the connect server. You might need to manually define the SASCMD value; otherwise, a default value will be added during migration.

In the previous deployment's SAS Management Console, add the SASCMD value to the SAS/CONNECT server's ServerComponent's property field. This SASCMD value is required in order to validate the SAS/CONNECT server successfully in the target SAS deployment. The validation is a new feature in SAS 9.2 and later of the Server Manager plug-in in SAS Management Console. If the value is not specified in the the previous deployment, then validation is not performed, and a default SASCMD value is added to the target SAS deployment. The default value depends on the deployment.

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.