Microsoft Download Center Archive

Microsoft Forecaster 7.0 Service Pack 3

  • Published:
  • Version: 7.0 SP3
  • Category: Service Pack
  • Language: English

Microsoft Forecaster 7.0 is a financial budgeting and planning product focused on the needs of the middle market.

  • Microsoft Forecaster works with a variety of general ledgers—including Microsoft Dynamics products—to automate and simplify the budgeting and planning process. In addition, this intuitive budgeting software looks like and integrates with the productivity software your people already use, making the budgeting and planning process accessible to more key players in your organization.
    For more information, go to: Microsoft Forecaster 7.0.

Files

Status: Deleted

This download is no longer available on microsoft.com. The downloads below are archives provided by the Internet Archive Wayback Machine from the Microsoft Download Center prior to August 2020.

FileSHA1 HashSize
Forecaster7_SP3.exe59291824581cf6857ff06940560864427fb77fab28.07 MB

System Requirements

Operating Systems: Windows Server 2003, Windows Vista, Windows XP

  • SERVER REQUIREMENTS
    Operating systems compatible with Oracle: Windows Server 2008, Windows Server 2003 R2, or Windows 2000 Server Service Pack 4 (SP4). Both x86-64 and x86-32 are supported.

    DATABASE
    Microsoft SQL Server 2005 Service Pack 2 (SP2), x86-64 and x86-32
    Microsoft SQL Server 2005 Express Edition, x86-64 and x86-32
    Microsoft SQL Server 2000 Service Pack 3 (SP3) preferred

    Oracle 10g Standard Edition and Enterprise Edition
    Note: Microsoft Forecaster ExpressLink and Microsoft FRx DirectLink are not supported on Oracle platforms.
    Oracle 9i Standard Edition and Enterprise Edition
    Note: Microsoft Forecaster ExpressLink and Microsoft FRx DirectLink are not supported on Oracle platforms.

    For more details, please see: Microsoft Forecaster 7.0 Requirements.

Installation Instructions

  • Install the Service Pack on the servers and workstations where Microsoft Forecaster is currently installed. Administrative rights are required to update the Microsoft Forecaster program. It is strongly advised that a database backup is made before completing the steps below.
    Microsoft Forecaster Desktop Client Installation Steps:

    1) Download the service pack by clicking the Download button (above) and then save the file to your hard disk.
    2) Double-click Forecaster7_SP3.exe to run the extraction process. You will be prompted to choose a location for your files.
    3) To start the extraction, click Unzip.
    4) After the extraction has completed, click OK.
    5) Go to the location of the service pack files.
    1. Close all running instances of Microsoft Forecaster.
    2. Launch the FC70SP3.msi file on the client machine for which you want to apply the updates.
    3. If prompted, click Run on the Security Window that opens to begin to apply the updates.
    4. Follow the prompts in the Setup Wizard to install the Service Pack.
    5. Click Finish once the installation completes.


    Microsoft Forecaster Web Access Installation Steps:

    Service Pack updates for Microsoft Forecaster Web Access client machines are deployed from the Web server when the user makes their initial connection to Microsoft Forecaster.

    1. Close all running instances of Microsoft Forecaster and stop the Web server instance.
    Caution: A reboot may be required if you do not stop the Internet Information Server service prior to installing this service pack on the web server.
    2. Launch the FC70SP3.msi file on the Web server for which you want to apply the updates.
    3. If prompted, click Run on the Security Window that opens to begin to apply the updates.
    4. Follow the prompts in the Setup Wizard to install the Service Pack.
    5. Click Finish once the installation completes.
    6. The next time the user connects to Microsoft Forecaster Web Access from their Web browser they will be prompted to install the updated components.
    Note: To update the web components on the user’s workstations be sure that the shortcut they use does not have a specific ASP page in the URL. For example, the URL should be https://servername/Forecaster7 not https://servername/Forecaster7/Forecaster.asp.