Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Install Failure - VS R2 Enterprise

18 views
Skip to first unread message

CharlieR

unread,
Jan 22, 2006, 6:43:46 PM1/22/06
to
I'm getting an install failure on Windows XP Professional x64 Edition of
the Virtual Server 2005 R2 Enterprise Edition. The error message is:

Error 1402. Could not open key:
HKEY_LOCAL_MACHINE32\Software\Classes\Msxml2.DOMDocument.4.0\CLSID.
System error 5. Verify that you have sufficient access to that key, or
contact your
support personnel.


I have verified that I, and in fact all users on the system, have full
control of that key.

any suggestions?

--
Charlie.
http://msmvps.com/xperts64


Richard Cardona

unread,
Jan 22, 2006, 8:47:14 PM1/22/06
to
CharlieR wrote:
> I'm getting an install failure on Windows XP Professional x64 Edition of
> the Virtual Server 2005 R2 Enterprise Edition. The error message is:
>
> Error 1402. Could not open key:
> HKEY_LOCAL_MACHINE32\Software\Classes\Msxml2.DOMDocument.4.0\CLSID.
> System error 5. Verify that you have sufficient access to that key, or
> contact your support personnel.

It's interesting that this problem occurs on XP x64 too. I re-posted a
solution from the last beta program for this problem.

John Ryan writes:
"... Error 1402. Could not open key:
HKEY_LOCAL_MACHINE\Software\Classes\Msxml2.DOMDocument.4.0\CLSID. Verify

that you have sufficient access to that key, or contact your support
personnel.

Finally tracked the error down and I thought I'd document the solution
in case anyone else runs into it too.

The Virtual Server install/uninstall problem is secondary to MSXML 4.0
registry problems.

From the Control Panel Add and Remove applet, uninstall all versions
(if more than one) of MSXML 4 .0. You may need to download and run
the Windows Installer CleanUp Utility
(http://support.microsoft.com/default.aspx?scid=kb;en-us;290301) to
remove some entries.

From a command prompt, run:
msiexec /qn /x 2AEBE10C-D819-4EBF-BC60-03BF2327D340
msiexec /qn /x 35343FF7-939B-401A-87B3-FF90A5123D88

In the registry, manually delete the following keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.DOMDocument.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.DSOControl.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.FreeThreadedDOMDocument.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.MXHTMLWriter.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.MXNamespaceManager.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.MXXMLWriter.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.SAXAttributes.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.SAXXMLReader.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.ServerXMLHTTP.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.XMLHTTP.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.XMLSchemaCache.4.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Msxml2.XSLTemplate.4.0

While logged in as local administrator (not sufficient to be a member of
the local administrator's group) install MSXML 4.0 SP2. I used the
msxml.msi available at
http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en.

Reinstall Virtual Server 2005.

You may need to re-enable Virtual Machine Remote Control from the Server
Properties page.

I don't know how my XML 4.0 got so messed up, but I had the same problem
earlier when I upgraded to Win2K3 EE from standard. I didn't find the
error then though, and just restored a backup (prior posts). Hopefully,
this will help someone.

Cheers,
John Ryan"

CharlieR

unread,
Jan 23, 2006, 4:00:56 PM1/23/06
to
Now THAT is seriously UGLY. And clearly calls for a KB all its own.

--
Charlie.
http://msmvps.com/xperts64

CharlieR

unread,
Jan 23, 2006, 5:47:23 PM1/23/06
to
Hmmm, from another venue, a simpler, if more far reaching change: Grant full
control to System on the entire HKEY_LOCAL_MACHINE32\Software\Classes hive.
I did, and it worked.

--
Charlie.
http://msmvps.com/xperts64

Richard Cardona

unread,
Jan 23, 2006, 9:41:42 PM1/23/06
to
CharlieR wrote:
> Hmmm, from another venue, a simpler, if more far reaching change: Grant full
> control to System on the entire HKEY_LOCAL_MACHINE32\Software\Classes hive.
> I did, and it worked.

I'm glad that worked for you. I tried that change more localized to the
MSXML keys and it did NOT work for me, in fact the permissions kept
getting reverted after the install would fail.

Thanks,
Richard

CharlieR

unread,
Jan 24, 2006, 1:38:34 AM1/24/06
to
Yes, that was my experience, but apparently going to the top solved it.

--
Charlie.
http://msmvps.com/xperts64

Richard Cardona

unread,
Jan 24, 2006, 10:18:28 AM1/24/06
to
CharlieR wrote:
> Yes, that was my experience, but apparently going to the top solved it.

I think most of the steps above are unnecessary, i.e. manually
uninstalling MSXML 4.

I've found subsequently that re-installing MS-XML4 solves the problem.
I would rather do it that way than modify my registry permissions from
the top of the hive.

To each their own :)

Richard

CharlieR

unread,
Jan 24, 2006, 2:17:34 PM1/24/06
to
Yeah, I can understand your reluctance to make sweeping changes to an entire
hives worth of permissions. I've asked that there be a clear KB on this, so
we'll see.

--
Charlie.
http://msmvps.com/xperts64

Matt Pierce

unread,
Dec 27, 2006, 1:53:55 AM12/27/06
to

That was a seriously UGLY solution posted above, but it did work like a charm. Many thanks to Mr. Ryan and Mr. Cardona for posting that.


Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com

Brilliant stuff. It worked for me as well.

unread,
Jun 14, 2007, 2:04:17 PM6/14/07
to

Keep up the good work and tips.

Many thanks

0 new messages