Article ID: 306491 - View products that this article applies to.
This article was previously published under Q306491
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 355248 (SHILOH_BUGS)
You can embed SQL Server 2000 Desktop Engine merge modules (.msm files) can into a Windows Installer based setup application by creating your own .msi file.
After you install SQL Server 2000 Service Pack 1 (SP1), if you run the Setup program to modify the application, the SQL Desktop Engine merge module may incorrectly attempt to run an action to update system stored procedures when this is not necessary. If that occurs, a dialog box may display with the following error message:
Unable to run the script files.
The merge module failed to specify that the scripts only need to run when a change is made to the Desktop Engine configuration.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
HotfixNOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.
The English version of this fix should have the following file attributes or later:
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
Date File name --------------------------- 21-Aug-2001 Sqlbase.msm
Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
The dialog box displays as part of the custom setup action ExecuteSPScripts.
This problem only occurs if SQL Server 2000 SP1 has previously been applied to the Desktop Engine.
Article ID: 306491 - Last Review: October 24, 2013 - Revision: 1.1