Error 2738 On Vista
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 03:50:07 GMT by s_ac15 (squid/3.5.20)
2738 on Vista while running light.exe from WiX v3.0 ★★★★★★★★★★★★★★★ Aaron StebnerApril 1, 200815 0 0 0 Recently, while attempting to build a Japanese MSI using WiX v3.0, I received an error message internal error 2738 windows 7 that looked like the following: light.exe : error LGHT0217 : An unexpected external UI error 2738 windows 7 fix message was received: ????????????????????????????????????????????????????????????? ???? 2738 ??? I wanted to see the full text of this error message, so I temporarily
Error 2738 Citrix Receiver
changed the product language setting in my WXS file from 1041 (the LCID for Japanese) to 1033 (the LCID for English) and re-ran the build. When I did that, the error message was more readable: http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/windows-vista-error-2738-not-axcess-vbscript/d8249289-50e4-4e1d-bf9b-5d8a46653083 light.exe : error LGHT0217 : An unexpected external UI message was received: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738. This message made more sense to me, so from there, I looked at the Windows Installer Error Messages reference for error code 2738 and found the following: Could not access VBScript run time for custom https://blogs.msdn.microsoft.com/astebner/2008/04/01/how-i-resolved-windows-installer-error-code-2738-on-vista-while-running-light-exe-from-wix-v3-0/ action [2]. While attempting to narrow down this error further, I found a couple of useful blog posts. As described in this blog post by Heath Stewart, error code 2738 can occur on Windows Vista systems (like the one I was using in the above scenario) if an MSI contains a script-based custom action and the VBScript runtime is registered in the HKEY_CURRENT_USER hive instead of or in addition to the HKEY_LOCAL_MACHINE hive. Also, as described in this blog post by Bob Arnson, four of the Windows Installer Internal Consistency Evaluators (ICEs) are implemented in VBScript. The offending ICEs are ICE08, ICE09, ICE32 and ICE61. In my build output, I noticed that light.exe had reported some warnings for ICE03 before displaying this 2738 error. From this, I made an educated guess that it was probably failing while running one of these four ICEs. Then, I used some of the advice that I listed in one of my previous blog poststo unregister vbscript.dll and jscript.dll from HKEY_CURRENT_USER to resolve this error: Click on the Start menu, choose Run, type cmd and click OK To unregister the VBScript engine, run this command: reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f To unregister the VBScript engine on a 64-bit OS, run this command: reg dele
Could not access VBScript run time for custom action. This error appears when http://www.sorcim.com/knowledgebase/error-2738.html the VBScript engine is not properly registered. Follow the tips below to fix the problem. Follow the steps below to fix this problem: Step 1 Error 2738? Download Error Scanner Reginout System Utilities (w/ Verisign Digital Certificate) Compatible w/ Windows 10/8.1/8, Windows 7, Vista/XP. By clicking to download, you agree to error 2738 these Terms See Features & Functions Re-Register VBScript Engine In order to fix error 2738 in Windows 7/8, Vista and XP you need to re-register VBScript engine properly. To do so follow the steps below: Click Start Type CMD in search box and press Enter Type this command (32-bit version) cd %windir%\system32 error 2738 windows Press Enter key Type this command (64-bit version) cd %windir%\syswow64 Press Enter key Now type this command regsvr32 vbscript.dll Hit Enter Close the command prompt Repair Registry Errors Registry errors can also result in error 2738 in Windows 7/8, Vista and XP. Automatically Fix Registry Errors Here or fix these errors by following the steps below: Click Start Type CMD in the search box Righ click on CMD and click Run as Administrator 32-Bit Windows users type the following command: reg delete "HKCU\SOFTWARE \Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f Press Enter Next enter this command and hit Enter: c:\windows\system32\regsvr32 vbscript.dll 64-Bit Windows users type the following command: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f Press Enter Next enter this command and hit Enter: c:\windows\syswow64\regsvr32 vbscript.dll Now start installation of the program Note: We don�t recommend you to do this step manually because any wrong action may result in data loss or crashing of operating system. Install a registry repairing t