Microsoft KB Archive/290514

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

Article ID: 290514

Article Last Modified on 5/8/2002

-

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.

Keywords: kberrmsg kbbug kbfix kbwin2000presp2fix KB290514

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.