Error 2738 Vista 64
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 16:21:47 GMT by s_ac5 (squid/3.5.20)
2738 on Vista while running light.exe from WiX v3.0 ★★★★★★★★★★★★★★★ Aaron StebnerApril 1, 200815 0 0 0 Recently, while
Internal Error 2738 Windows 7
attempting to build a Japanese MSI using WiX v3.0, I received error 2738 windows 7 fix an error message that looked like the following: light.exe : error LGHT0217 : An unexpected external UI error 2738 citrix receiver message was received: ????????????????????????????????????????????????????????????? ???? 2738 ??? I wanted to see the full text of this error message, so I temporarily changed the product language setting in my 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 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: 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 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/ 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 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 thi
by Jake Ludington on October 18, 2014 Windows 7 "I got an error while trying to install software on my Windows 7 computer. This is the error message: Error 2738. Could not access VBScript run time for custom http://www.jakeludington.com/windows_7/20091115_error_2738_could_not_access_vbscript_run_time_for_custom_action.html action. How can I fix error 2738?" This error is common to software applications that use VBScript for some portion of the install process. Error 2738 is an error that means VBScript is not properly configured to http://upandready.typepad.com/up_and_ready/2011/07/error-2738-installation-could-not-access-vbscript-run-time-for-custom-action.html run on your computer. I encountered Error 2738 when I installed Verizon Access Manager, but there are many other times it can occur. To fix Error 2738 you may need to follow slightly different steps depending on your error 2738 computer configuration. No matter what configuration you have for your Windows PC, the solution to this problem is incredibly geeky. It requires making some changes from the Windows command line, which is something most of us never have a reason to see. The first thing to figure out is whether you have a 64-bit or 32-bit version of Windows installed, because the solution will be different for each. This is listed in the System Control error 2738 windows Panel, which you can access by either clicking Window key+Pause or by clicking Start and then right-clicking computer and choosing Properties. In either case, you will get a list of System features. The one you are looking for is System type: 64-bit Operating System or System type: 32-bit Operating System. Note: These same steps also apply to Windows Vista. Fixing Error 2738 on Windows 7 64-bit If you have a 64-bit operating system, you will need to follow these steps: Open a command line window as Administrator, which requires clicking Start typing cmd in the search box, then right-clicking on the cmd.exe program and choosing Run as Administrator. Next paste the following in the command line and hit enter. reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f That previous command removes the incorrect entry for VBScript support on 64-bit Windows 7. Next you need to make sure VBScript is properly registered by typing: c:\windows\syswow64\regsvr32 vbscript.dll or simply regsvr32 vbscript.dll if you are already in the syswow64 directory. After following these steps you should be able to install your program without issue. Fixing Error 2738 on Windows 7 32-bit For a 32-bit operating system, the steps are similar, but slightly different: Open a command line window as Administrator, by clicking Start, typing cmd in the search box, then right-clicking on the cmd.exe program and choosing Run as Admi
your 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 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.