Error 2738 For Vista
Contents |
CompatibilityCustomer ServiceInstallation, Activation & LicensingNetwork License AdministrationAccount ManagementContact UsCommunityForumsBlogsIdeasContributionArticle ContributionsScreencastFree Learning Resources You are hereHomeSupport & LearningAutoCADTroubleshooting OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting To translate this article, select a microsoft windows error 2738 language. Bahasa Indonesia (Indonesian) Bahasa Melayu (Malay) Català (Catalan) Čeština error 2738 vbscript (Czech) Dansk (Danish) Deutsch (German) English Español (Spanish) Français (French) Italiano (Italian) Latviešu valoda (Latvian) Lietuvių kalba error 2738 could not access vbscript runtime for custom action vista (Lithuanian) Magyar (Hungarian) Nederlands (Dutch) Norsk (Norwegian) Polski (Polish) Português (Brasil) (Brazilian Portuguese) Română (Romanian) Slovenčina (Slovak) Slovenščina (Slovenian) Suomi (Finnish) Svenska (Swedish) Tiếng Việt (Vietnamese)
Erreur 2738 Vista
Türkçe (Turkish) Ελληνικά (Greek) Български (Bulgarian) Русский (Russian) Українська (Ukranian) हिन्दी (Hindi) ภาษาไทย (Thai) 한국어 (Korean) 日本語 (Japanese) 简体 (Chinese Simplified) 繁體 (Chinese Traditional) View Original Translate English Original X View Original X Installation fails with message Error 2738. Could not access VBScript run time for custom action. Sep 24 2015SupportApplies to AutoCAD 2010, skype error 2738 AutoCAD 2011, AutoCAD 2012, AutoCAD 2013, AutoCAD 2014, AutoCAD 2015, AutoCAD LT 2010, AutoCAD LT 2011, AutoCAD LT 2012, AutoCAD LT 2013, AutoCAD LT 2014, AutoCAD LT 2015, DWG TrueView 2010, DWG TrueView 2011, DWG TrueView 2012, ... Applies to AutoCAD 2010, AutoCAD 2011, AutoCAD 2012, AutoCAD 2013, AutoCAD 2014, AutoCAD 2015, AutoCAD LT 2010, AutoCAD LT 2011, AutoCAD LT 2012, AutoCAD LT 2013, AutoCAD LT 2014, AutoCAD LT 2015, DWG TrueView 2010, DWG TrueView 2011, DWG TrueView 2012, DWG TrueView 2013, Design Review 2010, Design Review 2011, Design Review 2012, Design Review 2013, and Design Review 2014See More Share Add To Issue: When you attempted to install or uninstall your product on Windows Vista or Windows 7, the following error appeared and the installation or deinstallation did not continue: Error 2738. Could not access VBScript run time for custom action. Solution: This error message indicates that the VBScript engine is not correctly registered on the affected machine. The VBScript
2738 on Vista while running light.exe from WiX v3.0 ★★★★★★★★★★★★★★★ Aaron StebnerApril 1, 200815 0 0 0 Recently, while attempting to build internal error 2738 windows 7 a Japanese MSI using WiX v3.0, I received an error message that
Error 2738 Windows 7 Fix
looked like the following: light.exe : error LGHT0217 : An unexpected external UI message was received: ????????????????????????????????????????????????????????????? ????
Error 2738 Citrix Receiver
2738 ??? I wanted to see the full text of this error message, so I temporarily changed the product language setting in my WXS file from 1041 (the LCID https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Installation-fails-with-message-Error-2738-Could-not-access-VBScript-run-time-for-custom-action-s.html 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 package. The error code is 2738. This message made 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/ 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 this, I made an educated guess that it was probably failing while running one of these four ICEs. Th
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: http://www.jakeludington.com/windows_7/20091115_error_2738_could_not_access_vbscript_run_time_for_custom_action.html Error 2738. Could not access VBScript run time for custom 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 run on your computer. I encountered Error 2738 when I installed Verizon Access Manager, but there are many error 2738 other times it can occur. To fix Error 2738 you may need to follow slightly different steps depending on your 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 error 2738 windows 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 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 f