Microsoft Error 1402
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 16:14:17 GMT by s_wx1126 (squid/3.5.20)
Modules Notable Users Brochures Testimonials Supported Platforms NuGraf PolyTrans-for-Cinema-4D PolyTrans-for-3ds Max PolyTrans-for-Maya NuGraf 3D Toolkit Specialized Sections Image Galleries Download Demos Sales/Ordering Support & Updates Developer Info Press Info Contact Okino
Error 1402 Windows 10
Links Sales: 1-888-3D-OKINOSupport: 905-672-9328Copyright © 2016 OkinoToronto, Ontario, Canada. How to fix error 1402 office 2010 uninstall 'Error 1402. Could not open key: UNKNOWN...' Step-by-Step Instructions for Windows Vista/Seven/Win2K8-Server Users Microsoft Windows users will error 1402 could not open key hkey_local_machine32 find the following short tutorial useful for solving the 'How to fix 'Error 1402. Could not open key: UNKNOWN...' problem which is becoming prevalent in online forum postings. Please use http://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/error-1402-could-not-open-key/1aff58b8-37f9-4d41-824e-9f4ca11b442f this information at your own discretion. A Quick Overview When installing or un-installing Microsoft Windows component technologies on Windows Vista/Seven/Win2K8-Server (or newer) you may encounter a message box similar to "Error 1402. Could not open key: UNKNOWN\Components\C9AE13788D0B61F80AF18C3B9B1A1EE8\...", This long number is not an "address" as many believe but rather a registry parent container key name (as a GUID) and its child http://www.okino.com/conv/changing_windows_registry_permissions.htm name (as a GUID). The last "\" character separates the two parent/child GUIDs. This is not related to Okino software, but rather to components which are usually provided by Microsoft Corp. The following tutorial will outline our own personal experiences at Okino Computer Graphics of dealing with this problem. We have seen this problem posted in many forums but the simple solution we outline below which has not been properly documented as we have done so here. Windows Vista/Seven/2K8: How to fix 'Error 1402. Could not open key: UNKNOWN...' The error is generally caused by insufficient or incorrect permissions on the named registry keys, or parent container of such registry keys. For Okino, it occurred on multiple occasions after upgrading some of our machines from Windows 2K3 to 2K8 server or from XP to Windows 7, and then upgrading/re-installing Microsoft products or components (Visual Studio and MSXML4 in our case). It is generally a simple matter to fix, once you know how. We recommended that you back-up your computer or at least the registry before taking this action. Microso
by CloudFlare Ray ID: 2f4d13485ff73720
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 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 Error 1402. Could not open key UNKNOWN\Components\.... Verify that you have sufficient access to that key or contact your support personnel when installing Symantec System Recovery (SSR) Article:000007961 Publish: Article URL:http://www.veritas.com/docs/000007961 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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Error 1402. Could not open key UNKNOWN\Components\ DA42BC89BF25F5BD0AF18C3B9B1A1EE8 Verify that you have sufficient access to that key or contact your support personnel.  Error Message Error 1402. Could not open key UNKNOWN\Components\ DA42BC89BF25F5BD0AF18C3B9B1A1EE8 Verify that you have sufficient access to that key or contact your support personnel.  Solution To resolve the issue, perform the following steps:  1)  Resolve permission issues per:  http://support.microsoft.com/kb/313222 . Once done, run the installer again.  2) If step 1 is unsuccessful, open the registry. Create a backup of the registry!! Then, locate the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-