FIX: "Error Reporting" Dialog Box Remains Open During Analysis Services 2000 Service Pack 3 Silent Installation

When you use the -s switch with an .iss file to install SQL Server 2000 Analysis Services Service Pack 3 (SP3) in Silent mode, the Error reporting dialog box remains open.

A problem with the installation script, Setup.ins, in SQL Server 2000 Analysis Services SP3.

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

The following file is available for download from the Microsoft Download Center:
Setup.exe (http://download.microsoft.com/download/3/8/f/38f2a2eb-9105-4281-befe-ee67c04b7627/setup.exe)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Setup.exe is a self-extracting executable that includes the updated Setup installation script file, Setup.ins.

To use the updated install script, follow these steps:

1. Make a backup copy of the existing Setup.ins file that is provided with SQL Server 2000 Analysis Services SP3.
2. Replace this file with the new file from the download link in this article.
3. To re-create the Setup.iss file for Analysis Services SP3, run Setup.exe with the -r switch. This starts Setup in GUI mode, and records the responses during the set up. You can then use the new Setup.ins and Setup.iss files to perform a silent installation.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.