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

MSXML4 SP1 Merge Module installation problems on XP!

0 views
Skip to first unread message

Per Bergland

unread,
Aug 27, 2002, 7:45:39 AM8/27/02
to
I have included the MSXML4 (runtime) merge module in our MSI installation.

Unfortunately, the install fails when installing as poweruser on XP since
the MSXML4_Parser.21206420_6BA8_4CFB_A48C_C72A6BFE80C0
component - GUDI {303994BA-6487-47AE-AF1D-7AF6088EEBDB} - generates an
installation failure HRESULT:-2147024891 (0x7FF8FFFB).

There are two XP-only components in the merge module (conditioned with
"VersionNT >= 501") that both install into some strange WinSXS folder.
What can I do to make our installer run as power user on XP?

If XP included XML4, I guess we could put a condition "NOT (VersionNT >=
501)" on the MSXML4 merge module, but I don't think XML4 is part of XP.


Duke Sun

unread,
Aug 27, 2002, 10:42:26 PM8/27/02
to
Does the problem occur when you install them with administrator account?

Per Bergland

unread,
Aug 28, 2002, 2:02:33 AM8/28/02
to
"Duke Sun" <qua...@microsoft.com> wrote in message
news:Yid01xjTCHA.2520@cpmsftngxa10...

> Does the problem occur when you install them with administrator account?

Nope. But forcing our installer to go admin-only is not a solution. All
installers that don't install drivers should support power user usage
(except InstallShield users that rely on ISScript of course since their
install-time script engine requires admin installation, but that's OT)

/Per


Duke Sun

unread,
Aug 29, 2002, 7:01:27 AM8/29/02
to
Now that the problem doesn't occur while installing the component with
Administrator account, and the problem occurs with Power User account, the
problem should be caused by security issue.

An application is a "managed application" if system, also known as
elevated, privileges are used to install the application. An application is
managed on a system if it is a per-machine installation on Windows NT 4.0
or Windows 2000 or if the application is assigned or published using Group
Policy on Windows 2000.

Therefore, you can assign or publish the MSI package to the machines to
install them.

I think the following article may be of help to your prolem:
Title: HOWTO: Allow Users Who Are Not Administrators to Install MSI
Packages (Q259459)
URL: http://support.microsoft.com/support/kb/articles/Q259/4/59.asp

0 new messages