Microsoft KB Archive/192731

= BUG: Hang or Application Error in Setup (VS60wiz.exe) =

Article ID: 192731

Article Last Modified on 8/11/2005

-

APPLIES TO


 * Microsoft Visual Studio 6.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Professional Edition
 * Microsoft Visual C++ 6.0 Standard Edition
 * Microsoft Visual Basic 6.0 Learning Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition
 * Microsoft Visual J++ 6.0 Standard Edition
 * Microsoft Visual InterDev 6.0 Standard Edition
 * Microsoft Visual FoxPro 6.0 Professional Edition
 * Microsoft Visual SourceSafe 6.0 Standard Edition

-



This article was previously published under Q192731



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
When install one of the Visual Studio products listed at the top of this article, the following error messages might appear:

Application Error in VS60wiz.exe

The ordinal 2 could not be found in the dynamic link library oraspawn.dll.

-or-

Application Error in VS60wiz.exe.

-or-

The ordinal 2 could not be found in the dynamic link library oraspawn.dll.

-or-

Process has already been executed. Generated error will be closed by windows. Needs to restart program. An error log has been generated.

NOTE: that the actual exception and location listed depends on the system.

The workaround described in the "Resolution" section of this article is also likely to resolve problems in which Setup stops responding.

None of the information in this article applies to failures that occur later in Setup, after ACMSETUP has started.



CAUSE
One possible cause is an exception triggered by a performance counter DLL.



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.

To allow setup to proceed, you need to temporarily prevent the loading of all performance counter DLLs. While these extensions are services, you can not control the loading of them through the Services utility in the Control Panel. You can identify performance counters by searching the services for a subkey named Performance in the system registry.  Start a registry editor such as RegEdt32.exe. Select the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

 Search for a key named Performance.

To do this in RegEdit: From the Edit menu, select Find and make sure only "Keys" is checked.

To do this in RegEdt32: From the View menu, select Find Key. Edit the Library value to change the name of the DLL to an invalid name. Rename it in such a way that you can rename it back to the original name after setup has finished.

To do this in RegEdit or RegEdt32: Double-click on the word Library. Place an X in front of the extension such as Xyz.xdll Repeat steps 3 and 4 until you have searched through all of the services. Restart the workstation.</li> Run Visual Studio Setup.</li> If the error continues to occur, rename the file \WINNT\System32\Perfc009.dat as Perfc009.xat.</li> Restart the workstation.</li> Run Visual Studio Setup.</li> Reverse steps 1-5 to rename the performance counter library names to their original values.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

<div class="references_section">