Installer Error Code 2739
& 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 Python .NET .NET .NET with Beth Massi ASP.NET by Scott Hanselman OData Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365 Development Web Data Development SQL Server SQL 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, 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, 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 totopProfessional Illustrator InDesign Photoshop Photoshop Extended Soundbooth Issue When you install Adobe Creative Suite 3 or a standalone Adobe Creative Suite 3 application in Windows Vista, one or more of the following occur:After you launch the Setup.exe file, the application returns the error message "This software cannot be installed because JScript is not properly registered. Please repair JScript and then restart the installer."The installer quits without an error message, though Setup.exe appears in the Task Manager.You receive the error message "Setup has encountered an error and needs to close. Error Code: 2739."The installer log displays https://blogs.msdn.microsoft.com/heaths/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions/ the error message "Error 2739: Could not access JavaScript runtime for custom action." Solution Manually register the jscript.dll file.Begin by determining whether your Windows Vista system is 32-bit or 64-bit: Click Start. Right-click Computer and select Properties. Look for "32-bit" or "64-bit" next to System Type. Then follow the instructions in the section below for your system type.Disclaimer: The procedures below involve editing the Windows registry. Adobe doesn't https://helpx.adobe.com/creative-suite/kb/error-2739-installer-closes-cs3.html support editing the registry, which contains critical system and application information. For information on the Windows Registry Editor, see the documentation for Windows or contact Microsoft Technical Support.On a 32-bit Windows Vista system: Choose Start > All Programs > Accessories. Right-click on Command Prompt, select Run As Administrator, and authenticate. If the prompt reads C:\Windows\System32>, proceed to Step 4. If not, type the following command exactly as it appears below, including the quotation marks, and then press Enter:cd "%systemroot%\System32" At the prompt, type regsvr32 jscript.dll and press Enter. When a dialog box with the message "DllRegisterServer in jscript.dll succeeded" appears, click OK. On a 64-bit Windows Vista system: Choose Start > All Programs > Accessories. Right-click on Command Prompt, select Run As Administrator, and authenticate. If the prompt reads C:\Windows\SysWow64>, proceed to Step 4. If not, type the following command exactly as it appears below, including the quotation marks, and then press Enter:cd "%systemroot%\SysWow64" At the prompt, type regsvr32 jscript.dll and press Enter. When a dialog box with the message "DllRegisterServer in jscript.dll succeeded" appears, click OK. The Adobe Captivate demonstration below illustrates how to manually register the jscript.dll file. For more information about viewing this demo, see Viewing Captivate Demo
Adobe software products on your PC. The error is most commonly the result of the "Jscript.dll" file not being correctly registered on your http://www.personalcomputerfixes.com/general-errors/how-to-repair-the-2739-error-on-your-pc-adobe-software-error/ system - making it impossible for your PC to read this file, which it needs so much to run. If you're seeing these errors, the good news is that you can fix the problems you're seeing with the tutorial on this page. What Causes The 2739 Error? This error will typically show in this format: “Setup has encountered an error installer error and needs to close. Error Code: 2739.” “Error 2739: Could not access JavaScript runtime for custom action” “Setup has encountered an error and cannot continue. Contact Adobe” The error you have is caused by your computer being unable to correctly process a particular file & settings needed to help it perform an installation of Adobe software on your system. This can installer error code be fixed by re-registering a particular file which could be damaged on your system. How To Fix The 2739 Error Step 1 - Re-Register "JScript.dll" On Your PC The main problem you have is that the "jscript.dll" (Javascript runtime file) is not running correctly, and consequently needs to be re-registered on your PC to help your computer to read it correctly again. This will allow your computer to read all the settings it requires to run the installer. Here's what you need to do: Click "Start > Run" (alternatively press the Windows Key + R) Type "CMD" into the box that appears On the black screen that appears, type "regsvr32 -u jscript.dll" Press Enter Next, type "regsvr32 jscript.dll" Press Enter Try installing again Step 2 - Clean Out The Registry Download This Registry Cleaner The 2739 error can often be caused by the settings inside the "registry database" of your computer not working correctly. This is a huge database of all the settings your PC requires to run, and is where Windows keeps a large number of important settings whi