Error 2738 Vbscript Server 2008
Contents |
Setup & Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team error 2738 vbscript runtime for custom action Foundation Server Testing Visual Studio Team Services All Languages Visual
Error 2738 Vbscript Windows Vista
C++ Visual F# JavaScript TypeScript Python .NET .NET .NET with Beth Massi ASP.NET by Scott
Error 2738 Vbscript Vodafone
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
Error 2738 Vbscript Windows 7
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 0 0 0 Windows Script custom actions should be avoided. They are difficult to debug, error 2738 could not access vbscript 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, E
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company error 2738 could not access vbscript runtime for custom action uninstall Business Learn more about hiring developers or posting ads with us Server Fault Questions error 2738 could not access vbscript runtime for custom action xp Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it error 2738 could not access vbscript runtime for custom action windows 7 only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Install Error: Could not access VBScript run time https://blogs.msdn.microsoft.com/heaths/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions/ for custom action up vote 0 down vote favorite I'm trying to install a package on a Windows 2008 server. The package is refusing to install. I have run the install with the following command line switched to get a log file: /lxv InstallLog.txt This is the error that I see in the file: Error 2738.Could not access VBScript run time for custom action I have looked around and found some people saying that this http://serverfault.com/questions/34099/install-error-could-not-access-vbscript-run-time-for-custom-action is needed: Regsvr32 vbscript.dll This because on a Windows Server 2008 system, the VBScript.dll is not registered for the HKeyCurrent_User only the HKeyLocal_Machine due to security issues. This doesn't quite "smell" right. I initially tried running the install as an administrator but no luck. I have written a small VBScript program that displays a message box and it appears to run properly. In the file: Test.VBS I have this: msgbox("Hello world") When I double click on it I get a message box appearing implying that VBScript is indeed functional. I have disabled UAC on the machine and I still get the error. As suggested by Evan I have verified the following registration: HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8} It does exist and looks fine. As another test, I ran the Regsvr32 vbscript.dll from an Administrator console and tried again. Still no luck, I get the same errors as before. windows-server-2008 vbscript windows-installer share|improve this question edited Jul 1 '09 at 13:56 asked Jun 30 '09 at 20:45 John Dyer 4181810 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote VBScript for custom actions is bad form. You should slap around whoever made that installer package. Have you double-checked that the following registry key doesn't exist: HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8} Secondly, when you ran the "REGSVR32 vbscript.dll" command, did you do so from an elevated command-prom
Michael P.) » Error 2738 - W2K8 R2 x64 « previous next » Print Pages: [1] Go Down Author Topic: Error 2738 - W2K8 R2 x64 (Read 5484 times) 0 Members and 1 Guest are viewing this topic. rafaelsantiago Newbie Posts: https://forum.avast.com/index.php?topic=89354.0 4 Error 2738 - W2K8 R2 x64 « on: November 29, 2011, 06:30:47 PM http://yetanothercomputingblog.blogspot.com/2011/12/error-2738-occurs-when-installing-msi.html » Hello friends,I was using the Avast Pro 4.8 (Business Protection), and i'm trying to migrate to the new version (Avast Business Protection 6). I removed: Avast Manager & Avast Management Tools from my Control Panel.I've received my new license file. And i'm trying to install the new BP.I ran the setup wizard "setup_console_bp.exe", and check that i error 2738 have all the prerequisites mentioned in the Wizard. Ok, everything's right.Continuing the instalation, the wizard show a error "Error 2738 - Could not access VBScript run time for custom action.". And it ends here. I just cant install it!I need to install it very urgent, cuz i removed my Avast Console 4. And now i just can't manage my Avast Clients.I search for some help in Google, but everything that is mentioned error 2738 vbscript in every topic is:QuoteIf you are using 64-bit version of Windows:Run Command Prompt as administrator:Start Menu -> All Programs -> AccessoriesRight click on Command Prompt and select Run as administratorType the following command in the prompt: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f, then hit Enter.Next, you must also type the following command: c:\windows\syswow64\regsvr32 vbscript.dll, then hit Enter.This doesn't work to me. I'm using a Windows Server 2008 R2, 64 bit version.What can i do about this?Thank you so much! « Last Edit: November 29, 2011, 06:34:39 PM by rafaelsantiago » Logged giogio Avast Evangelist Massive Poster Posts: 3996 Re: Error 2738 - W2K8 R2 x64 « Reply #1 on: November 29, 2011, 07:58:32 PM » Try also this Go to the Start Menu and click on Run. Type CMD on Run Search Bar to start Command prompt. Type cd %windir%\system32 and press Enter. Type regsvr32 vbscript.dll and press Enter. Type regsvr32 jscript.dll and press Enter.or try with thishttp://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=15102758&linkID=9240617in particolar try toRun the command that unregisters the DLL: Type regsvr32 /u vbscript.dll into the Command Prompt and press ENTER.and register againand if the problem is still Go to the Start Menu and click on Run. SFC /SCANNOW Logged Prima di scrivere sul forum per favore le
with elevated permissions. To confirm that its the problem run the MSI installer from the command line (with administrator permissions - right click on the command prompt link in the start menu and select run as administrator) like this: MSIEXEC /i