Internal Error 2738 On
Contents |
CompatibilityCustomer ServiceInstallation, Activation & LicensingNetwork License AdministrationAccount ManagementContact UsCommunityForumsBlogsIdeasContributionArticle ContributionsScreencastFree Learning Resources You are hereHomeSupport & LearningAutoCADTroubleshooting OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting
Internal Error 2738 Windows 7
OverviewGetting StartedLearn & ExploreDownloadsTroubleshooting To translate this article, select error 2738 vbscript windows 7 a language. Bahasa Indonesia (Indonesian) Bahasa Melayu (Malay) Català (Catalan) Čeština (Czech) Dansk
Internal Error 2738 Windows 7 64 Bit
(Danish) Deutsch (German) English Español (Spanish) Français (French) Italiano (Italian) Latviešu valoda (Latvian) Lietuvių kalba (Lithuanian) Magyar (Hungarian) Nederlands (Dutch) Norsk (Norwegian) software installation problem internal error 2738 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) Български (Bulgarian) Русский (Russian) Українська (Ukranian) हिन्दी (Hindi) ภาษาไทย (Thai) 한국어 (Korean) 日本語 (Japanese) 简体 (Chinese Simplified) 繁體 (Chinese Traditional) View error 2738 microsoft fix it 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, 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 T
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 18 Oct 2016 22:27:19 GMT by s_nt6 (squid/3.5.20)
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs https://www.veritas.com/support/en_US/article.TECH64025 Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Internal Error 2738 during the installation of the Symantec Private Branch Exchange Component MSI Error 2738: Could not access VBScript error 2738 runtime for custom action Article:000035528 Publish: Article URL:http://www.veritas.com/docs/000035528 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products internal error 2738 Article Languages Subscribe to this Article Manage your Subscriptions Problem Internal Error 2738 during the installation of the Symantec Private Branch Exchange Component MSI Error 2738: Could not access VBScript runtime for custom action Error Message Error 2738: Could not access VBScript runtime for custom action Solution Cause This error message indicates that the VBScript engine is not currently registered on the machine where the install/uninstall is taking place. Resolution The VBScript engine can be quickly registered by following these steps: 1. Run Command Prompt as administrator A. Start Menu -> All Programs -> Accessories B. Right click on Command Prompt and select Run as administrator 2. Type cd %windir%\system32 into the Command Prompt and hit Enter 3. Type regsvr32 vbscript.dll into the Command Prompt and hit Enter 4. Proceed with reinstalling the .msi application Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Trans