FIX: WSC File Is Not Integrated in the MSI File When You Export COM+ Application as a Server Application (290514)


The information in this article applies to:

  • Microsoft COM+ 1.0
This article was previously published under Q290514

SYMPTOMS

When a COM+ application contains a Windows Scripting Component (WSC) component, and you export the COM+ application as a Server Application (not as an Application Proxy), the .wsc file is not integrated in the resultant Microsoft Installer Package (.msi) file. As a result, the installer program does not copy or register the .wsc file on the target computer, and the installation on the new server does not function correctly.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

Windows Script Components are designed to be used from scripting environments such as Active Server Pages (ASP). You can also use Component Services to register .wsc files in a COM+ application. This problem occurs when .wsc files are installed in an application that is exported as a Server Application.
Modification Type:MajorLast Reviewed:5/8/2002
Keywords:kbbug kbDSupport kberrmsg kbWin2000PreSP2Fix kbWin2000SP2Fix KB290514
©2002 Microsoft Corporation. All rights reserved.