Msi Error 2738
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 21:07:55 GMT by s_wx1196 (squid/3.5.20)
& Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual Studio Team Services All Languages Visual C++ Visual F# JavaScript TypeScript error 2738. could not access vbscript runtime for custom action windows 10 Python .NET .NET .NET with Beth Massi ASP.NET by Scott Hanselman OData internal error 2738 windows 7 64 bit Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL
Error 2738 Windows Vista
Server Data Tools DocumentDB Setup & Install by Heath Stewart About Windows Installer, the .NET Framework, and Visual Studio. Windows Installer Errors 2738 and 2739 with Script Custom Actions ★★★★★★★★★★★★★★★ May 31, http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-2738-could-not-access-vbscript-run-time-for/1a4499ae-8bc1-4534-9c6f-4d399ac70d9a 2007 by Heath Stewart (MSFT) // 28 Comments Share 0 0 Windows Script custom actions should be avoided. They are difficult to debug, get blocked by virus scanners, and are far more susceptible to machine state than native custom actions. That is indicated by Windows Installer error messages 2738 and 2739, which read: 2738, Could not access VBScript run time for custom action [2]. 2739, https://blogs.msdn.microsoft.com/heaths/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions/ Could not access JScript run time for custom action [2]. As some people have found, re-registering the runtime libraries vbscript.dll and jscript.dll will fix the errors, but that isn't always the solution. As a security measure, Windows Installer will not load script engines registered in HKEY_CURRENT_USER. As a user-writable store, a normal user could get an elevated install to run their library masking as a script engine if the custom action was not explicitly attributed with msidbCustomActionTypeNoImpersonate (0x0800). This is an elevation of privileges attack; thus, Windows Installer returns error message 2738 or 2739 for custom actions type 6 and type 5, respectively, and returns Windows error 1603, ERROR_INSTALL_FAILURE. Check that vbscript.dll and jscript.dll aren't registered in HKEY_CURRENT_USER (HKCU), checking for the registry keys below. VBScript, HKCUSOFTWAREClassesCLSID{ B54F3741-5B07-11CF-A4B0-00AA004A55E8} JScript, HKCUSOFTWAREClassesCLSID{ F414C260-6AC0-11CF-B6D1-00AA00BBBB58} Remove these keys if they exist in HKEY_CURRENT_USER. Also be sure that if you need to re-register vbscript.dll or jscript.dll, you run regsvr32.exe in an elevated console on Windows Vista and newer with UAC enabled; otherwise, you'll end up registering the runtimes in HKCU.
Back totop Search this blog Search all blogs Share This PostShareShareShareShareShare Recent Posts Changes to Visual Styour next steps? .Net Framework Errors and Windows 7 Autodesk 2011 products. Error 2738 Installation, could not access VBScript run time for custom action 07/19/2011 If the http://upandready.typepad.com/up_and_ready/2011/07/error-2738-installation-could-not-access-vbscript-run-time-for-custom-action.html Technical Solution below didn't fix the issue, you can delete the https://community.spiceworks.com/how_to/1577-solving-the-error-code-is-2738 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 error 2738 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 internal error 2738 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
an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738.” This installer error is not just for Skype. Steps (5 total) 1 Take a look in Event Viewer I looked in Event Viewer to find out what MSI-file that generated the error message and found: Log Name: Application Source: MsiInstaller Date: 23.09.2010 21:58:26 Event ID: 1040 … … Description: Beginning a Windows Installer transaction: C:\ProgramData\Skype\{D103C4BA-F905-437A-8049-DB24763BBE36}\SkypeToolbars.msi. Client Process Id: 6564. 2 Running MSIEXEC with logging options I started a “Command Promt” and used the command: “cd C:\ProgramData\Skype\{D103C4BA-F905-437A-8049-DB24763BBE36}” to navigate into the folder containing the MSI-file. Now using the command: “msiexec /i SkypeToolbars.msi /lv log.txt” (msiexec options: /i = Install, /lv = Log + Verbose output). After clicking away the error message I just wrote “log.txt” in my “Command Promt” to open the log-file. Near the bottom of the log-file I found this line: DEBUG: Error 2738: Could not access VBScript runtime for custom action 3 DEBUG: Error 2738 After a quick search at Google I found out this error indicates that the VBScript engine is not registered on the computer. The solution for a Windows Vista or Windows 7 32bit: - Click Start -> All Programs -> Accessories - Right click “Command Promt” and click on “Run as administrator” - Write “cd %windir%\system32” and hit Enter - Write “regsvr32.exe vbscript.dll” and hit Enter - You should now get a message that says: “DllRegisterServer in vbscript.dll succeeded.” - Click “OK” The solution for a Windows Vista or Windows 7 64bit: - Click Start -> All Programs -> Accessories - Right click “Command Promt” and click on “Run as administrator” - Write “cd %windir%\syswow64” and hit Enter - Write “regsvr32.exe vbscript.dll” and hit Enter - You should now get a message that says: “DllRegisterServer in vbscript.dll succeeded.” - Click “OK” 4 Try again... Now I tried once more to run “msiexec /i SkypeToolbars.msi /lv log.txt” (I kept the /lv log.txt option to look for changes if the installer would fail again). If you still get the same Error than continue to step 5. 5 Cleanup registry first, then re-reg My installation still gave me the same error, so after some more searching and reading on Google