Installation V8i SS2 error 2738

Applies To

Product(s): MicroStation
Version(s): 08.11.07.443
Environment: N\A
Area: Installation
Subarea: N\A
Original Author: Jin Long Yuan, Bentley Technical Support Group

Problem
Installation V8i SS2 error 2738; 1603

Unable to install MicroStation on Windows 7 machine. Receive an error:

The installer has encountered a unexpected error installing this package.
This may indicate a problem with this package. The error code is 2738. This is accompanied with
a 1603 error in the installation dialog, "A fatal error occurred during installation."

Solution
1. Start Command Prompt (run as administrator)
2. Type: CD C:\Windows\System32
3. Regsvr32 vbscript.dll

If this Windows 7 64-bit platform,also:

 4. Type CD C:\Windows\Syswow64\
5. Regsvr32 vbscript.dll

If this does not resolve issue remove registration for VBSscript engine
under HKEY_LOCAL_MACHINE registry and then repeat steps 1 through 5
above. To do this:

1.Click on the Start menu, choose Run, type cmd and click OK
2.To unregister the VBScript engine, run this command: reg delete
"HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
3.To unregister the VBScript engine on a 64-bit OS, run this command:
reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741
-5B07-11CF-A4B0-00AA004A55E8}" /f
4.To unregister the JScript engine, run this command: reg delete
"HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
5.To unregister the JScript engine on a 64-bit OS, run this command: reg
delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{F414C260-6
AC0-11CF-B6D1-00AA00BBBB58}" /f

Retry installation

See following link for more information:http://blogs.msdn.com/b/astebner

/archive/2007/06/07/3151752.aspx

 instead of HKEY_CURRENT_MACHINE (correct), from security reasons the installation script

has no access to VBscript engine. The solution is to remove the library registration from
HKEY_CURRENT_USER tree.

In regedit application:

Find {B54F3741-5B07-11CF-A4B0-00AA004A55E8} key in HKCU

(HKEY_CURRENT_MACHINE) tree and delete it. There should be only one such key.

From command prompt:

Start command prompt (cmd) as administrator. Key in:

o (32bit OS) reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-

00AA004A55E8}" /f
o (64bit OS) reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-
11CF-A4B0-00AA004A55E8}" /f

Now the installation should be OK, I am not quite sure if under some circumstances the new
reregistration of vbscript.dll isn't required

Error 2738 Installation, could not access

VBScript run time for custom action
07/19/2011
If the Technical Solution below didn't fix the issue, you can delete the relevant registry entries and
re-register the dll.
http://usa.autodesk.com/getdoc/id=TS15102758

Please make sure you backup the registry/system before you make any changes to the registry.
To delete the registry keys, please run following commands in a command prompt with elevated
privileges. Please check out this reference post as well:
http://upandready.typepad.com/up_and_ready/2012/03/general-systems-windows-7-administrator-tips-tricks.html

On Windows 7 64 bit System

reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

On Windows 7 32 bit
reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

To re-register the DLL, please run following commands with elevated privileges:
On Windows 7 ~ 64 bit system
c:\windows\syswow64\regsvr32 vbscript.dll

c:\windows\system32\regsvr32 vbscript.dll

On Windows 7 ~32 bit system

c:\windows\system32\regsvr32 vbscript.dll

Certain Anti-Virus programs have been known to affect the registration of the dll. Please check out
the the notes below:
If you had McAfee Anti-Virus in the past (even if you have unistalled it will leave some trace
components on the computer), please use this tool to remove it completely:
http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

If you had Avast Anti-Vvirus program in the past (and you have installed it), please read the
instructions to completely uninstall it here.
______________________________________________________
Epilogue
 1. Search in the registry for the following value: {B54F3741-5B07-11cf-A4B0-00AA004A55E8}
2. Back up any key with that value then delete it. i.e. Backup: File > Export. When deleting the key,
there maybe an error and the key will not delete. You will need to go into each folder to ensure that
the folder is empty and hit F3 to search again.

3. Repeat steps 1 & 2 until there are no more entries for {B54F3741-5B07-11cf-A4B0-
00AA004A55E8}.
4. We needed to completely uninstall McAfee Anti-Virus using the MCPR.exe because the
InprocServer32 value for (Default) was set to "McAfee'. i.e. C:\Program Files\Common
Files\McAfee\. The default value for InprocServer32 is below:

NOTE: You may need to research how to cleanly uninstall your flavour of Anti-Virus
software.
5. Re-register the DLL:
On Windows 7 ~ 64 bit system

c:\windows\syswow64\regsvr32 vbscript.dll

c:\windows\system32\regsvr32 vbscript.dll

On Windows 7 ~32 bit system

c:\windows\system32\regsvr32 vbscript.dll

6. Once you have cleared the registry settings and uninstalled the Anti-Virus software cleanly, then
you will be able to install the software without a 2738 error.

 Well, next try, a bit more sophisticated and confirmed by Filip that it works :-)

It seems the whole problem is where in Windows registry vbscript dll library is registered. If it is
registered in HKEY_CURRENT_USER (wrong) instead of HKEY_CURRENT_MACHINE
 (correct), from security reasons the installation script has no access to VBscript engine. The
solution is to remove the library registration from HKEY_CURRENT_USER tree.

In regedit application:

Find {B54F3741-5B07-11CF-A4B0-00AA004A55E8} key in HKCU

(HKEY_CURRENT_MACHINE) tree and delete it. There should be only one such key.

From command prompt:

Start command prompt (cmd) as administrator. Key in:

o (32bit OS) reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-

00AA004A55E8}" /f

This 64 bit os option works for windows 8.1 (tested by MHH)

o (64bit OS)
o
o reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-
A4B0-00AA004A55E8}" /f

Now the installation should be OK, I am not quite sure if under some circumstances the new
reregistration of vbscript.dll isn't required.

Problem
Where can I find installation log file after installing MicroStation?

Solution
The name of this file is called BentleyInstallationlLog.log.

This log file contains information about all the actions and analysis performed by the installation
 setup wizard. It also saves the installation commands used to install the application. In case of
any error in the installation, it stores the error code. This file is common for all the Bentley
products. Each time a Bentley application is installed, this log file is appended with the content
of the application.

When you install the application, its installation log is created. This log is saved in a new folder
created inside C:\Users\User.Name\AppData\Local\Temp. The name of the new folder is
randomly generated, such as E32830B5-3516-489D-AE49-EB1BD8A10867. If you execute the
installation multiple times, the latest log can be taken from the last modified/created folder.

Providing these logs to Bentley can be helpful to troubleshoot installation errors and issues

INSTALLATION FAILS WITH MESSAGE

ERROR 2738. COULD NOT ACCESS
VBSCRIPT RUN TIME FOR CUSTOM
ACTION.
Sep 24 2015
Support
Applies to AutoCAD 2010, AutoCAD 2011, AutoCAD 2012, AutoCAD 2013, AutoCAD 2014, AutoCAD
2015, AutoCAD LT 2010, AutoCAD LT 2011, AutoCAD LT 2012, AutoCAD LT 2013, AutoCAD LT 2014,
AutoCAD LT 2015, DWG TrueView 2010, DWG TrueView 2011, DWG TrueView 2012, ...
See More

Like (0) Login to like this Article

Share
FacebookStumbleUponGoogle+DeliciousTumblrTwitterLinkedinEmail
Add To
Issue:
When you attempted to install or uninstall your product on Windows Vista or Windows 7,
the following error appeared and the installation or deinstallation did not continue:

Error 2738. Could not access VBScript run time for custom action.
Solution:
This error message indicates that the VBScript engine is not correctly registered on the affected
machine.
The VBScript engine can be registered by following these steps:
1. Run Command Prompt as administrator:
1. Start Menu -> All Programs -> Accessories
2. Right click on Command Prompt and select Run as administrator
2. Navigate to the folder that contains the DLL:
o If you are using 32-bit version of Windows:
 Type cd %windir%\system32 into the Command Prompt and press ENTER
o If you are using 64-bit version of Windows:
 Type cd %windir%\syswow64 into the Command Prompt and press ENTER
3. Run the command that registers the DLL:
o Type regsvr32 vbscript.dll into the Command Prompt and press ENTER.
If the problem still persists even after successfully registering the DLL as described above, the
most likely cause is that the DLL was already registered by a non-administrative user.
In this case you will need to first log onto machine as the user who registered the DLL
previously and unregister the DLL as follows:
1. Run Command Prompt:
1. Start Menu -> All Programs -> Accessories
2. Double-Click on Command Prompt
2. Navigate to the folder that contains the DLL:
o If you are using 32-bit version of Windows:
 Type cd %windir%\system32 into the Command Prompt and press ENTER
o If you are using 64-bit version of Windows:
 Type cd %windir%\syswow64 into the Command Prompt and press ENTER
3. Run the command that unregisters the DLL:
o Type regsvr32 /u vbscript.dll into the Command Prompt and press ENTER.
Next, register the DLL again while running Command Prompt as Administrator, as described in
the first set of instructions.

In some cases, this error can also be caused by a conflict with McAfee Antivirus. Refer to When
I try to install I get an Internal Error 2738 for more details.
For more advanced users, please also check out the following Up and Ready blog post for an
additional solution to this issue: