Usage Note 38399: Errors occur when you run the configuration process using the SAS® Deployment Wizard more than once and do not remove previous configuration attempts
 |  |  |  |
Errors occur when you run the configuration process using the SAS Deployment Wizard more than once and do not remove the previous configurations. Below are examples of the types of errors that write to the log file for a particular product in this instance. The syntax of the log files' names includes the date and time, represented as yyyy-mm-dd-hh.mm.ss
For SAS® BI Report Services, the following errors write to the birepserv_configure_yyyy-mm-dd-hh.mm.ss.log file:
[SetObjectProperties] Error finding software component: Repository ${bireps is not registered.
[SetObjectProperties] fqid: ${birepserv.configobj.fqid}
[SetObjectProperties] m_mdFactory:
com.sas.metadata.remote.MdFactoryImpl@da9ea4
[SetObjectProperties] m_mdObjectStore: [SDW:
ConfigurationStore]com.sas.metadata.remote.MdObjectStoreImpl@1758cd1
[SetObjectProperties] m_repositoryFQID: A0000001.${bireps
[SetObjectProperties] Error getting text store: null
[SetObjectProperties] SoftwareComponent: null
[SetObjectProperties] Error getting text store: null
[SetObjectProperties] SoftwareComponent: null
[SetObjectProperties] Error setting object properties:
[SetObjectProperties] connected:true
[SetObjectProperties] SoftwareComponent:null
[antcall] Exiting
/data1/install/MLB_92migration/SAS/SASBIReportServices/4.2/Config/birepserv_config.xml.
[antcall] Exiting
/data1/install/MLB_92migration/SAS/SASBIReportServices/4.2/Config/birepserv_config.xml.
[antcall] Exiting
/data1/install/MLB_92migration/SAS/SASBIReportServices/4.2/Config/birepserv_config.xml.
BUILD FAILED
/data1/install/MLB_92migration/SAS/SASBIReportServices/4.2/Config/birepserv_config.xml:483: null
at com.sas.tools.webappconfig.tasks.TaskImpl.execute(TaskImpl.java:75)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)For SAS® Foundation Services, the following errors write to the jps_configure_yyyy-mm-dd-hh.mm.ss.log file:
[SetObjectProperties] Error finding software component: Repository ${jps.co is not registered.
[SetObjectProperties] fqid: ${jps.configobj.fqid}
[SetObjectProperties] m_mdFactory:
com.sas.metadata.remote.MdFactoryImpl@2f356f
[SetObjectProperties] m_mdObjectStore: [SDW:
ConfigurationStore]com.sas.metadata.remote.MdObjectStoreImpl@4ed904
[SetObjectProperties] m_repositoryFQID: A0000001.${jps.co
[SetObjectProperties] Error getting text store: null
[SetObjectProperties] SoftwareComponent: null
[SetObjectProperties] Error getting text store: null
[SetObjectProperties] SoftwareComponent: null
[SetObjectProperties] Error setting object properties:
[SetObjectProperties] connected:true
[SetObjectProperties] SoftwareComponent:null
[antcall] Exiting
/data1/install/MLB_92migration/SAS/SASFoundationServices/9.2/Config/jps_config.xml.
BUILD FAILED
/data1/install/MLB_92migration/SAS/SASFoundationServices/9.2/Config/jps_config.xml:770: null
at com.sas.tools.webappconfig.tasks.TaskImpl.execute(TaskImpl.java:75)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tools.ant.dispatch.DispatchUtils.execute
(DispatchUtils.java:105)For IBM WebSphere Application Server Network Deployment, the following errors write to the webspherend_configure_yyyy-mm-dd-hh.mm.ss.log file:
webspherend.init:
[echo] ===> webspherend_config.xml (webspherend.init): Initialization for
webspherend product
[echo] webspherend.init: Obtain JPS ObjectProperties because we need the
Multicast information.
Property "webappsrv.dependson.jps.fqid" has not been set
[GetObjectProperties] Using FQID: ${webappsrv.dependson.jps.fqid}
[GetObjectProperties] *************** ERROR ****************
[GetObjectProperties] *************** ERROR ****************
[GetObjectProperties] *************** ERROR ****************
[GetObjectProperties] Object property retrieval failed since requested fqid is
an unexpanded property: ${webappsrv.dependson.jps.fqid}
[GetObjectProperties] No configured instance was found using the given fqid for:
SAS Foundation Services
BUILD FAILED
/data1/install/MLB_92migration/SAS/SASDeploymentManager/9.2/products/cfgwizard__
92210__prt__xx__sp0__1/webspherend/Config/webspherend_config.xml:43: null
at com.sas.tools.webappconfig.tasks.TaskImpl.execute(TaskImpl.java:75)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)To work around this issue when you encounter errors after a metadata server deployment, you should restore your metadata server back to its original state before you run another configuration. You should also back up your metadata server between each tier.
If you cannot back up the metadata server between each tier, use the SAS® Deployment Manager to remove the failed configuration. This tool is located in SASHOME\sasdeploymentmanager\9.2\. The tool is launched with the config.exe, config.sh, or config.rexx file depending on your operating environment. When you remove a configuration, any metadata deployed is removed; services are stopped and deleted; and files are removed from the configuration directory.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Enterprise BI Server | z/OS | 4.2 | |||
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 4.2 | |||||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 4.2 | |||||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 4.2 | |||||
| Microsoft Windows XP 64-bit Edition | 4.2 | |||||
| Microsoft® Windows® for x64 | 4.2 | |||||
| Microsoft Windows 95/98 | 4.2 | |||||
| Microsoft Windows 2000 Advanced Server | 4.2 | |||||
| Microsoft Windows 2000 Datacenter Server | 4.2 | |||||
| Microsoft Windows 2000 Server | 4.2 | |||||
| Microsoft Windows 2000 Professional | 4.2 | |||||
| Microsoft Windows NT Workstation | 4.2 | |||||
| Microsoft Windows Server 2003 Datacenter Edition | 4.2 | |||||
| Microsoft Windows Server 2003 Enterprise Edition | 4.2 | |||||
| Microsoft Windows Server 2003 Standard Edition | 4.2 | |||||
| Microsoft Windows Server 2008 | 4.2 | |||||
| Microsoft Windows XP Professional | 4.2 | |||||
| Windows 7 Enterprise 32 bit | 4.2 | |||||
| Windows 7 Enterprise x64 | 4.2 | |||||
| Windows 7 Home Premium 32 bit | 4.2 | |||||
| Windows 7 Home Premium x64 | 4.2 | |||||
| Windows 7 Professional 32 bit | 4.2 | |||||
| Windows 7 Professional x64 | 4.2 | |||||
| Windows 7 Ultimate 32 bit | 4.2 | |||||
| Windows 7 Ultimate x64 | 4.2 | |||||
| Windows Millennium Edition (Me) | 4.2 | |||||
| Windows Vista | 4.2 | |||||
| 64-bit Enabled AIX | 4.2 | |||||
| 64-bit Enabled HP-UX | 4.2 | |||||
| 64-bit Enabled Solaris | 4.2 | |||||
| HP-UX IPF | 4.2 | |||||
| Linux | 4.2 | |||||
| Linux for x64 | 4.2 | |||||
| Solaris for x64 | 4.2 | |||||
If you encounter problems during the configuration process and need to re-run the SAS® Deployment Wizard, you should remove the changes created by the first attempt by using the SAS® Deployment Manager.
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2010-10-04 14:35:20 |
| Date Created: | 2010-01-14 11:57:17 |