When you upgrade to SAS Real-Time Decision Manager 6.1, you might receive the following errors:

1. The SAS^® Decision Services Design Mid-Tier fails.
   
   
   
   

   The text of the error text is as follows:

   The following problem was encoutered while configuring SAS Decision Services Monitor:
   
   Unable to delete the metadata object(s): SASHOME/SASDecisionServicesDesignMidTier/
   5.6/Config/Deployment/Metadata/policydesign_RealTimeDecisionDesignServer.xml.orig:
   ... WARNING:No objects of type ServerComponent were found using the search criteria: 
   @Name='SASDSDesignServer ...'
   
   Configuration script:
   
   SASHOME/SASDecisionServicesDesignMidTier/5.6/Config/policydesign_config.xml
   
   For More information please see the log file:
   configuration-directory/Lev1/Logs/Configure/policydesign_updateConfigure_time-stamp.log
   ...
   Would you like to continue with the remaining configuration steps?

   To work around this issue, click Yes to continue in the SAS^® Software Deployment Wizard.
   
   

2. The SAS Decision Services Monitor fails because the database already exists.
   
   
   
   

   The text of the error is as follows:

   The following problem was encoutered while configuring SAS Decision Services Monitor:
   
   Failed creating database on sasTransactional server; host=your-host, port=your-port.
   
   Configuration script:
   
   SASHOME/SASDecisionServicesMonitor/5.6/Config/dcsvcmonitor_config.xml
   
   For more information please see the log file:
   
   configuration-directory/Lev1/Logs/Configure/dcsvcmonitor_startServer_time-stamp.log
   ...
   Would you like to continue with the remaining configuration steps?

   Click Yes to continue because the database already exists.
   
   
3. After the UIP is completed, the following issues might also occur:
   1. The engine server diagnostics for the following resources fail to connect:
      • $SAS_Activity_Resource
      • $Audit_Log_JDBCConnectionResource
      • $User_Log_JDBCConnectionResource
      • GeneralIO_Activity_Resource

      To work around this issue, use SAS^® Management Console to correct the system resources in the Engine and Design repository. Navigate to the Engine and Design repository and verify that the DSN connections are correct.

   
   
   
   2. The passwords for the following resources in the engine repository are missing:
      • $SAS_Activity_Resource
      • $Audit_Log_JDBCConnectionResource
      • $User_Log_JDBCConnectionResource
      • GeneralIO_Activity_Resource
        
        
        
        

      To work around this issue, use SAS Management Console to enter the passwords for the SAS^® Federation Server administrator in the system resources in the Engine repository. Navigate to the Engine repository and correct the passwords for the system resources.

Operating System and Release Information