Error 1603 (Internal error 2738) when installing SQL Optimizer (4310877)

Error 1603 (Internal error 2738) when installing SQL Optimizer

Getting error 1603 when installing SQL Optimizer as part of Toad bundle. The following error is displayed in the msi log:

"Error 2738: Could not access VBScript runtime for custom action
MSI (s) (AC:84) [14:37:52:749]: Product: Quest SQL Optimizer for Oracle -- Internal Error 2738"

1. vbscript.dll has not been registered.

2. Previous install of SQL Optimizer (i.e. old or same version) is being detected.

RESOLUTION 1:

Microsoft has created a Fix-It this issue for 64bit Windows:

What this Fix it does is to automatically remove any incorrect or corrupt registry entries that interfere with VB support in windows and then re-registers the DLL ensuring that the correct registry setting are there. After running the Fix it solution, it is recommended to reboot your PC first then run the SQL Optimizer installation.

The link to the FixIt for installation issues is: https://support.microsoft.com/en-us/mats/program_install_and_uninstall 

After running the FixIt, try installing again. 



RESOLUTION 2:

Re-register the vbscript.dll.

Target Directory: 

32 bit windows: %windir%/system32 (usually something like C:\windows\system32) 
or
64 bit Windows : %windir%/syswow64 (usually something like C:\windows\syswow64) 

1. Verify that you have vbscript.dll in your Target directory as stated above 

2. Run command prompt as administrator (specifically). Start > Accessories > right-click Command Prompt and select Run as Administrator. 

3. The command prompt should open to something like C:\Windows\system32 (your path might be different, but you want the system32 folder underneath your windows directory. Change directory to that location if needed). 

4. Make sure to Unregister vbscript dll first: 
Type everything that appears in the quotes on the command line, but you do not need to use quotes, you should see a message popup verifying that vbscript.dll unregistered correctly. 

32bit type:   "regsvr32 /U %windir%/system32/vbscript.dll" 
or 
64bit type:   "regsvr32 /U %windir%/syswow64/vbscript.dll" 

5. Now register vbscript.dll 
You should see a message about successful registration popup 

32bit type:   "regsvr32 %windir%/system32/vbscript.dll" 
or 
64bit type:   "regsvr32 %windir%/syswow64/vbscript.dll" 

Try the installation again.



RESOLUTION 3:
Removing dlls from HKEY_CURRENT_USER registry. 

Manually check if the vbscript.dll and jscript.dll are still registered in HKEY_CURRENT_USER (HKCU) by checking for the registry keys below. Go to Windows Start, type in regedit to get to the registry. Navigate to the following:

VBScript:  HKCU\SOFTWARE\Classes\CLSID\{ B54F3741-5B07-11CF-A4B0-00AA004A55E8}
JScript:     HKCU\SOFTWARE\Classes\CLSID\{ F414C260-6AC0-11CF-B6D1-00AA00BBBB58}

If they are still there, backup your registry*, then rename these keys (i.e. {B54F3741-5B07-11CF-A4B0-00AA004A55E8_OLD}). Run step 5 from above again to re-register the dlls. Be sure to re-register the dlls by running regsvr32.exe in an elevated console if working on Windows Vista and newer with UAC enabled; otherwise, you'll end up registering the runtimes in HKCU again. 

Then test the installation again. 

*To backup your registry, highlight the HKEY_CURRENT_USER node then go to File | Export. Save as a .reg file into a directory you have access to. If needed, after the test, you can roll back the change by naming back the registry keys or rolling back the whole registry with the backup saved. 

register_VBScripts

The instructions for registering and the tool is also attached if the links cannot be accessed. Here is the following link that gives instructions to delete the vbscript.dll and the jscript.dll files and then re-register both files: http://www.instant-registry-fixes.org/how-to-resolve-error-2738/ If Benchmark Factory is also installed on the machine, please uninstall this aswell, then re-register vbscript.dll and then run the installer again.