FIX: WSC File Is Missing from MSI File When You Export a COM+ Application as a "Server Application" (277818)

The information in this article applies to:

Microsoft Windows 2000 Server SP1
Microsoft Windows 2000 Advanced Server SP1
Microsoft Windows 2000 Professional SP1

This article was previously published under Q277818

SYMPTOMS

Windows Script Components (WSC) are designed to be used from scripting environments such as Active Server Pages (ASP) and can be registered in Component Services in a COM+ application. However, when a COM+ application that contains a .wsc file is exported as a "Server Application", the .wsc file is not integrated into the Installer Package (.msi) file, unlike the .tlb and .dll files. As a result, the Installer engine does not copy or register the .wsc file on the target computer.

CAUSE

When you export an application that contains a .wsc file, Scrobj.dll is used and referenced in the .msi file instead of the actual script implementation because the component lists that it is hosted by Scrobj.dll.

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 Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

To implement these changes, the COM+ catalog components search the entry that is listed under ScriptletURL. If the entry exists, it is used as the actual export file instead of Scrobj.dll. If it is a local file, this file gets packaged into the Installer Package (and installed automatically). If it is a URL, the URL is referenced in the MSI file. On the import side, Regsvr32 registers each of these files, whether URL or local.

Modification Type:	Major	Last Reviewed:	11/17/2003
Keywords:	kbbug kbfix kbSysAdmin kbWin2000PreSP2Fix KB277818