Fix For Error 2738
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 20:57:22 GMT by s_ac15 (squid/3.5.20)
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 language. Bahasa Indonesia (Indonesian) Bahasa Melayu
Internal Error 2738 Windows 7 64 Bit
(Malay) Català (Catalan) Čeština (Czech) Dansk (Danish) Deutsch (German) English Español (Spanish) the installer has encountered an unexpected error installing this package 2738 Français (French) Italiano (Italian) Latviešu valoda (Latvian) Lietuvių kalba (Lithuanian) Magyar (Hungarian) Nederlands (Dutch) Norsk (Norwegian) Polski (Polish) error 2738 windows vista Português (Brasil) (Brazilian Portuguese) Română (Romanian) Slovenčina (Slovak) Slovenščina (Slovenian) Suomi (Finnish) Svenska (Swedish) Tiếng Việt (Vietnamese) Türkçe (Turkish) Ελληνικά (Greek) Български (Bulgarian) Русский (Russian) Українська (Ukranian) हिन्दी (Hindi) ภาษาไทย http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-2738-could-not-access-vbscript-run-time-for/0ffd532e-a3e0-4738-8601-38c46e69e238 (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, AutoCAD 2011, AutoCAD 2012, AutoCAD 2013, AutoCAD 2014, AutoCAD 2015, AutoCAD LT 2010, AutoCAD LT 2011, AutoCAD LT 2012, AutoCAD 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 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 engine can be registered by following these steps: Run Command Prompt as administrator: Start Menu -> All Programs -> Accessories Right click on Command Prompt and selectRun as administrator Navigate to the folder that contains the DLL: If
. You can quickly find out that you need to register vbscript.dll, but there is a nasty gotcha if you are too quick on the draw. 64-bit Windows also requires special care. Ever since http://csi-windows.com/blog/all/27-csi-news-general/161-fixing-windows-installer-error-2738 Windows Vista, Microsoft does not register vbscript.dll when the operating system installs. I have also found that my vbscript.dll registration can go missing (I have recently setup auditing on the relevant COM registration keys in hopes that I can find the culprit). If you are like me and you read “reregister vbscript.dll” you quickly open a command prompt and type “regsvr32.exe vbscript.dll” error 2738 If you do this on Windows Vista or Windows 7, this quick fix can make a mess. Assuming you are running with UAC turned on, a default command prompt will not be elevated. When regsvr32.exe runs it ends up registering vbscript.dll in HKCU. However, if your custom action runs in the deferred system context (noimpersonate bit turned on), you will still have error code 2738 the error. This is because Windows Vista and Windows 7 ignore HKCU based COM registrations when elevated. The problem get’s a little deeper when you attempt to unregister vbscript.dll from HKCU using “regsvr32.exe -u vbscript.dll” because it will not unregister properly. You must manually delete the registry keys and then run regsvr32.exe while elevated. A related problem is having a damaged vbscript.dll COM registration in HKCU and a proper one in HKLM. The damaged HKCU one will be used by custom actions that are NOT running as administrator. Finally, I suspect, but have not been able to prove (yet) that some setups (MSI or EXE) use manual means to attempt add or remove (on uninstall) the DLL registration keys for vbscript.dll in HKCU. Enjoying your read? Subscribe to our newsletter (without loosing your place in this article). (Please ensure that the confirmation email clears your spam filter so that you will see future mailings.) To fix both possible problems be sure to delete the HKCU com registration and re-register vbscript.dll while using an elevated command prompt. Delete these registry keys HKCU\Software\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8} HKCU\Software\Classes\CLSID\{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}For 64-bit, delete:HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{f414c260-6ac0-11cf-b6d1-00