• support.sas.com

• Knowledge Base

• Support

• Training & Bookstore

• Community

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

SAS® Content Server

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

Messages

The content repository is locked. Before running the SAS Migration Utility, the SAS Content Server needs to be stopped. Setting the property SMU.scs.allow.sync to true will allow the utility to pause so it can be stopped.

This message is seen in migrations from SAS 9.2 only. The message indicates that the property SMU.scs.allow.sync is unset or false, and that a lock file was found. You must either stop the SAS Content Server or set the property SMU.scs.allow.sync to true, and then run SAS Migration Utility again. The property SMU.scs.allow.sync is useful if you need to minimize the amount of time that the Content Server is offline. When SMU.scs.allow.sync is true, the SAS Migration Utility prompts you to stop and restart the Content Server. For more information about SAS Migration Utility properties, see SAS Intelligence Platform: Migration Guide.

Content Repository is locked, but content server is not accessible.

This message is seen in migrations from SAS 9.3 and later. The message indicates that a lock file was found, and the SAS Migration Utility is able to copy the content without you stopping the Content Server, but the copy failed because the connection information is incorrect. By default, the connection information is taken from the metadata that is set with SAS Management Console. Usually this connection information is correct. Alternatively, you can use the following SAS Migration Utility properties to specify connection information: SMU.sas.url, SMU.scs.user, and SMU.scs.password. For more information about SAS Migration Utility properties, see SAS Intelligence Platform: Migration Guide.

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.