Installation Instructions for Hot Fix D73027

Windows


Hot fix D73027 addresses the issue(s) in SAS Financial Management 5.2_M1 on Windows as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/D73.html#D73027


D73027 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated. See the Container Hot Fixes section in the Maintenance Install Tool (MIT) Usage Guide for more information about container hot fixes.

E36007 for SAS Financial Management 5.2_M1
D74013 for SAS Financial Management Add-in for Microsoft Excel 5.2
E32010 for SAS Financial Management Mid-Tier 5.2_M1
E37009 for SAS Financial Management Studio 5.2_M1
E33010 for SAS Financial Management Web Data Entry 5.2_M1
E68003 for SAS OLAP Data and Compute Server Mid-Tier for Solutions 5.2_M1
G90001 for SAS Solutions Dimension Editor 5.2_M1
E40006 for SAS Solutions Services Add-in for Microsoft Office 5.2
E91002 for SAS Solutions Services Data Server 5.2_M1
G91001 for SAS Solutions Services Logical Types 5.2_M1
E83005 for SAS Solutions Services Mid-Tier 5.2_M1

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The software components and release numbers should match the list of software components updated by the individual hot fix installers.


INSTALLATION

Important Notes

  1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

  2. You must have Administrator Privileges on your CLIENT or SERVER machine.

  3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  4. This hot fix should be installed using the same userid who performed the initial software installation.


Downloading the hot fix

  1. This hot fix must be installed on each machine where the updated components of the product, listed above, are installed. The installation process will determine which components of SAS Financial Management 5.2_M1 are installed on each machine, and apply the appropriate updates.

  2. If the updated components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.

  3. When downloading SAS 9.2 hot fix packages, you must choose to Save the hot fix to disk, then execute the install from the saved location. Attempting to install a hot fix directly from the download page results in the error documented in SAS Note 37104.

  4. The installer downloaded is D73027wn.exe.


Prior to executing the hot fix shut down the SAS servers

  1. Log on to the WebLogic Server Administration Console at
    http://midtierservername:7501/console

  2. On the left side of the screen under Domain Structure, select Environment > Servers

  3. Select the Control tab

  4. Select SAS Servers 3, 4 and 5 and click Shutdown > Force Shutdown Now > Yes

  5. Exit out of all Microsoft Office applications.

  6. Exit out of SAS Financial Management Studio, the SAS Financial Management Add-In for Microsoft Excel and the SAS Information Delivery Portal.


Installing the hot fix

  1. Execute D73027wn.exe. This will initiate the installation wizard, which will guide you through the hot fix installation process.

    Note: If your Windows operating system is Windows Vista, Windows 7 or Windows Server 2008, it may be necessary to "right-click" D73027wn.exe and select "Run as administrator".

  2. Re-start your SAS Financial Management client application(s) and all of the changes should be in effect.

See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.


This completes the installation of D73027. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.


POST-INSTALLATION INSTRUCTIONS

Updates provided in this hot fix require that the following Web Applications be rebuilt and redeployed.

Server 3: SAS Financial Management Mid-Tier
Server 3: SAS Solutions Services Mid-Tier
Server 4: SAS OLAP Data and Compute Server Mid-Tier for Solutions
Server 5: SAS Financial Management Web Data Entry


Update config.ini files

The installation of this hot fix to SAS Solutions Dimension Editor and SAS Financial Management Studio clients assumes that the clients are installed in

C:\Program Files\SAS\
If the clients are installed in a location other than C:\Program Files\SAS, the files
<SASHOME>\SASSolutionsDimensionEditor\5.2\configuration\config.ini
<SASHOME>\SASFinancialManagementStudio\5.2\configuration\config.ini
must be manually modified. All occurences of
C:\Program Files\SAS\
must be changed to reflect the location to where the clients are installed. You should confirm that the SASVersionedJarRepository paths are correct for your installation.


Re-build Web Application

In order for this step to execute correctly, the Metadata Server must be running.

  1. Invoke the SAS Deployment Manager 9.2

    From the SASDeploymentManager directory launch config.exe.
    SAS Deployment Manager is installed in the following default location:

    <SASHOME>\SASDeploymentManager\9.2

  2. Select a language in the Choose Language box

  3. Select Rebuild Web Applications

  4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

  5. Specify Connection Information, including the sasadm User ID and Password

  6. Select the mid-tier applications listed above as the Web Applications to Rebuild

  7. Verify the information on the Summary screen and select Start

  8. Select Finish when the deployment is complete
This process will update the ears in
<SASCONFIGDIR>\Web\Staging
A backup of the original ear files will be placed in the directory
<SASCONFIGDIR>\Web\Staging\Backup


Re-deploy Web Application

  1. Remove the cache for the updated ear files under
    <drive>:\SAS\Config\Lev1\Web\SASDomain\servers\SASServer4\tmp\_WL_user
    (delete entire folder for each ear file)

  2. Re-deploy the web application using WebLogic Admin console.

    To deploy this application it is important to deploy from <SASCONFIGDIR>\Web\Staging.

    Verify that in the settings overview tab for the Financial Management Mid-Tier and Financial Management Web Data Entry ear files to be re-deployed that the deployment order is set to 110.

    Verify that in the settings overview tab for the Solutions Services Mid-Tier and OLAP Data and Compute Server Mid-Tier for Solutions ear files to be re-deployed that the deployment order is set to 100.

  3. Re-deploy WebSphere Application.

    Re-deploy the web application using WebSphere Admin console by using the Update function.

    To deploy this application it is important to deploy from /Web/Staging.

    Verify that the Deploy WebServices checkbox is selected


Re-start the Web Application Servers

  1. Re-start SAS Remote Services (which will likely require that you also re-start SASServer1 and SASServer2).

  2. Re-start SASServer3 and SASServer4 (you will likely also need to re-start SAS Server5 since the other application servers were stopped).

  3. From Weblogic Admin Console, select SASServer 3, 4, and 5 > Start > Yes


Review SAS Notes

After the installation of this hot fix, review the following SAS Notes for details on changes that are required to take advantage of the fix.

Problem Note 42001   SASŪ Financial Management forms might take a long time to render in Form Manager for 'typical' users

Be sure to assign the Form Submitter role in SAS Management Console to the non-Financial Management: Process Administrator or non- Financial Management: Form Administrator users who are accessing the large number of SAS Financial Management forms in the SAS Information Delivery Portal.
Problem Note 44139   SASŪ Financial Management 'template save failed' when adding measure to supplemental schedule if validation list is greater than 255 characters
Once this fix is applied, you should access your form(s) on a client machine that has the fix installed and then re-save your form(s) to enable the longer validation lists to be properly handled. If your form set is already published, you might want to consider re-setting, re-saving and re-publishing the form set, though this is not required.

If you then access the form(s) from a client machine that does not have the fix applied, you will find that your validation will not work; the fix must be installed on all clients that access the forms(s).


After applying a hot fix to SAS Financial Management Add-in for Microsoft Excel or SAS Solutions Services Add-in for Microsoft Office

If you encounter Visual Basic Application errors in your reports/forms after applying the hot fix, such as

("Type mismatch" error)
Compile error: Object library feature not supported
Object variable or With block variable not set
perform the following steps.

  1. Log off of the Financial Management or SAS Solutions Add-In.

  2. From the report/form, select Alt + F11 to open Visual Basic for Applications window.

  3. Select Tools > References and de-select the SASSESExcelAddin.

  4. Click OK.

  5. Select Tools > References. Notice that the previous SASSESExcelAddIn reference is now missing from the list.

  6. Select Browse, navigate to SASSESExcelAddIn.tlb and select Open

    (file location is typically C:\Program Files\SAS\SASFinancialManagementAdd-InforMicrosoftExcel\5.2\SASSESExcelAddIn.tlb).

  7. The new SASSESExcelAddIn reference will appear in the list and will be selected.

  8. Select OK.

  9. Select File > Save.

  10. Exit our of your Excel session.

  11. Open the report/form and log on to the Financial Management or SAS Solutions Add-In.

  12. The report/form should now recognize the reference to the latest SASSESExcelAddIn.tlb with no errors.


This completes the deployment of hot fix D73027 on Windows.