Microsoft KB Archive/249812

= BUG: Uninstalling a COM+ Application that Uses .wsc Breaks Windows Scripting =

Article ID: 249812

Article Last Modified on 6/11/2002

-

APPLIES TO


 * Microsoft COM+ 1.0

-



This article was previously published under Q249812



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
COM+ is an evolutionary extension to the Component Object Model (COM). When you uninstall a COM+ application that has a Microsoft Windows Script Component (.wsc), which was exported as a Server application or application proxy, Windows scripting may no longer be functional on that computer.



CAUSE
Uninstalling the exported application also uninstalls the Scrobj.dll file, which is a Windows scripting system dynamic-link library (DLL), as part of the component.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Follow the steps below to correctly install and export the Server application that contains a .wsc component:  Register the .wsc file (right-click the file icon in Explorer and click Register). Generate the .tlb file (right-click Generate Type Library). Create the COM+ application in COM+ Explorer. Drag and drop the .tlb file that was generated in step 2 to the COM+ application in COM+ Explorer. In the registry, insert "Implemented Categories" under CLSID\{GUID}, as follows:

[HKEY_CLASSES_ROOT\CLSID\{}\Implemented Categories\{87D49532-B7b6-11d0-8d1e-00c04fc2e0c7}] @=""

</li> Export the COM+ application as a Server application.</li></ol>

Follow the steps below to install the Server application on a remote computer:
 * 1) Copy the application server (.msi) and script file (.wsc) to the remote computer.
 * 2) Register the .wsc file on the remote computer (right-click the file).
 * 3) Import the application server.

<div class="status_section">

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

<div class="moreinformation_section">

MORE INFORMATION
The workaround described in the "Resolution" section works only if the COM+ application is exported as a Server application. Exporting as an application proxy still causes the problem.

Steps to Reproduce Behavior

 * 1) Create a COM+ application with a script (.wsc) component.
 * 2) Export the COM+ application as a Server application or application proxy.
 * 3) Copy the .msi file to another computer and install the application.
 * 4) Now uninstall the application that was created from .msi.
 * 5) Try to run any Windows Scripting files (.wsc, .wsf).

You must manually reinstall Scrobj.dll ( regsvr32 scrobj.dll ) on that system to again make scripting functional on that computer.

Keywords: kbbug kbscript kbsysadmin kbpending KB249812

-

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

© Microsoft Corporation. All rights reserved.