Error 2738 Vbscript Verizon Vista
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 04:36:36 GMT by s_ac15 (squid/3.5.20)
CompatibilityCustomer ServiceInstallation, Activation & LicensingNetwork License AdministrationAccount ManagementContact UsCommunityForumsBlogsIdeasContributionArticle ContributionsScreencastFree Learning Resources You are
Error 2738. Could Not Access Vbscript Runtime For Custom Action Windows 10
hereHomeSupport & LearningAutoCADTroubleshooting OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting error 2738 windows vista OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting To translate this article, select a language.
Microsoft Fix It 50842
Bahasa Indonesia (Indonesian) Bahasa Melayu (Malay) Català (Catalan) Čeština (Czech) Dansk (Danish) Deutsch (German) English Español (Spanish) Français (French) 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 Italiano (Italian) Latviešu valoda (Latvian) Lietuvių kalba (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) Türkçe (Turkish) Ελληνικά (Greek) 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 Български (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, 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,
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 http://www.jakeludington.com/windows_7/20091115_error_2738_could_not_access_vbscript_run_time_for_custom_action.html the error message: 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 https://notgartner.wordpress.com/2008/07/12/the-error-code-is-2738/ 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 error 2738 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 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 error 2738 vbscript 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 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
one setup package that I was dealing with, but it might work with yours as well (this is a general problem with some installers). Yesterday I was trying to install the PowerTools for Visual Studio Team System 2008 Database Edition (what a mouthful). This is a set of tools that extend the Database Edition of Visual Studio, and I was specifically interested in the MSBuild extensions for doing schema comparisons. Unfortunately, when I attempted to install the package on my Windows Vista 64-bit machine I got the following error: “The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738.” Bummer! My heart sank because I really needed those components and I was worried that I might be seeing some weird 64-bit Vista issue with the way that the setup package had been built – but as I found out, this also effects 32-bit installations as well. To diagnose the problem I ran the setup package again, but this time I used the MSIEXEC command-line interface to tell it to provide some verbose logging details: MSIEXEC /i VSTSDB2008PT.MSI /lv LOG.TXT This executes the setup package as normal, but it takes all the output generated by Windows Installer for diagnostic purposes and stuffs it into a file called LOG.TXT. These files can sometimes be quite large but I found this error (in red) buried away towards the end of the file. Action start 22:19:04: INSTALL. MSI (s) (D0:14) [22:19:04:442]: Running ExecuteSequence MSI (s) (D0:14) [22:19:04:442]: Doing action: DevEnvProcessCheck MSI (s) (D0:14) [22:19:04:442]: Note: 1: 2205 2: 3: ActionText Action start 22:19:04: DevEnvProcessCheck. MSI (s) (D0:DC) [22:19:04:445]: Generating random cookie. MSI (s) (D0:DC) [22:19:04:452]: Created Custom Action Server with PID 13584 (0x3510). MSI (s) (D0:D4) [22:19:06:320]: Running as a service. MSI (s) (D0:D4) [22:19:06:322]: Hello, I'm your 32bit Impersonated custom action server. MSI (s) (D0:60) [22:19:06:324]: Note: 1: 2205 2: 3: Error