While performing an Upgrade in Place from ship event 10w46 to 10w50, a failure might occur on the mid-tier server at stage 7 while Updating the Content. The process will typically fail with SAS BI Dashboard trying to look for a NON EXISTANT DIRECTORY.

You might encounter an error similar to the following:

     [echo] bid.updateoldconfigfiles
     [echo] bid.updconfigfiles.bid
[propertyfile] Updating property file:
C:\SAS\Config\Lev1\Logs\Configure\bidashmid_config_status.properties
[propertyfile] Updating property file:
C:\SAS\Config\Lev1\Logs\Configure\bidashmid_config_status.properties
     [echo] dir=C:\SAS\Config\Lev1\AppData\SASBIDashboard4.2
     [java] Executing 'C:\Program Files (x86)\Java\jre1.5.0_12\bin\java.exe'
with arguments:
     [java] '-Djava.system.class.loader=com.sas.app.AppClassLoader'
     [java] '-Dsas.ext.config=C:\Program
Files\SAS\SASPlatformObjectFramework\9.2\sas.java.ext.config'
     [java] '-Dsas.app.launch.config=C:\Program
Files\SAS\SASBIDashboard\4.3\Picklists\utilities\picklist'
     [java] '-Dsas.app.repository.path=C:\Program
Files\SAS\SASVersionedJarRepository\9.2\eclipse'
     [java] '-Dsas.services.information.types.path=C:\Program
Files\SAS\SASPlatformObjectFramework\9.2\plugins'
     [java] '-classpath'
     [java] 'C:\Program
Files\SAS\SASVersionedJarRepository\9.2\eclipse\plugins\sas.launcher.jar'
     [java] 'com.sas.bi.dashboard.config.ConfigUtil'
     [java] 'config.type=updatebid'
     [java] 'config.charEncoding=UTF-8'
     [java] 'config.update.source=C:\SAS\Config\Lev1\AppData\SASBIDashboard4.2'
     [java] 'config.update.system.target=report=/System/Applications/SAS BI
Dashboard/BI Dashboard 4.3'
     [java] 'config.update.product.target=report=/Products/BI Dashboard 4.3'
     [java] 'config.update.user.target=report=/{USER_HOME_APP}/BI Dashboard 4.3'
     [java] 'config.omr.host=rio.trc.sas.com'
     [java] 'config.omr.port=8561'
     [java] 'config.omr.domain=DefaultAuth'
     [java] 'config.userid=sasadm@saspw'
     [java] 'config.userpwd={sas002}1D3211221C1104E218FEC4002945FBA308AB65D4'
     [java] 'config.trusted.userid=sastrust@saspw'
     [java] 'config.trusted.userpwd={sas002}20879A3C3A55523627F247D64CB52D05'
     [java] 'config.repository=Foundation'
     [java]
     [java] The ' characters around the executable and arguments are
     [java] not part of the command.
     [java] INFOFri Nov 19 15:08:19 EST 2010 [main] ***** upgradein-place
starting *****
     [java] ERRORFri Nov 19 15:08:22 EST 2010 [main] Directory
C:\SAS\Config\Lev1\AppData\SASBIDashboard4.2\rangeDefs for upgrade-in-place
cannot be found.
     [java] Java Result: 1
      [ant] Exiting C:\Program
Files\SAS\SASBIDashboard\4.3\Config\loadcontent.xml.

The problem is caused by a properties file left over from the upgrade from release 4.2 to 4.3, which causes the loadContent process to interpret the version as 4.2.

The leftover file is

${bidashmid.content.dir}/bidashmid.old.properties.

The workaround is to rename the file <bidashmid.old.properties>

This file is typically located at:

$SASCONFIGDIRECTORY\Lev1\Appdata\SASBIDashboard4.3

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS BI Dashboard	Microsoft® Windows® for x64	4.3		9.2 TS2M3
		Microsoft Windows Server 2003 Datacenter Edition	4.3		9.2 TS2M3
		Microsoft Windows Server 2003 Enterprise Edition	4.3		9.2 TS2M3
		Microsoft Windows Server 2003 Standard Edition	4.3		9.2 TS2M3
		Microsoft Windows Server 2003 for x64	4.3		9.2 TS2M3
		Microsoft Windows Server 2008	4.3		9.2 TS2M3
		Microsoft Windows Server 2008 for x64	4.3		9.2 TS2M3
		Microsoft Windows XP Professional	4.3		9.2 TS2M3
		Windows 7 Enterprise 32 bit	4.3		9.2 TS2M3
		Windows 7 Enterprise x64	4.3		9.2 TS2M3
		Windows 7 Professional 32 bit	4.3		9.2 TS2M3
		Windows 7 Professional x64	4.3		9.2 TS2M3
		Windows 7 Ultimate 32 bit	4.3		9.2 TS2M3
		Windows 7 Ultimate x64	4.3		9.2 TS2M3
		Windows Vista	4.3		9.2 TS2M3
		Windows Vista for x64	4.3		9.2 TS2M3

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

An UIP for 10w50 from 10w46 configuration will fail at stage 7 while loading the content.

Type:	Installation Note
Priority:	high

Date Modified:	2011-02-08 12:35:08
Date Created:	2010-11-22 12:03:37