error 1925 You do not have sufficient privileges - Command line
Dominique
When executing msiexec.exe with the /jm switch (advertised
installation), I get the following error:
"You do not have sufficient privileges to complete the installation
for all users of the machine. Log on as administrator and then retry
the installation."
The log indicates:
....
Action ended 12:18:26: PublishComponents. Return value 0.
Action start 12:18:26: PublishFeatures.
Action 12:18:26: GenerateScript. Generating script operations for
action:
GenerateScript: Publishing Product Features
Action ended 12:18:26: PublishFeatures. Return value 1.
Action start 12:18:26: PublishProduct.
GenerateScript: Publishing product information
Action ended 12:18:26: PublishProduct. Return value 1.
Action start 12:18:26: InstallFinalize.
Error 1925. You do not have sufficient privileges to complete this
installation for all users of the machine. Log on as administrator
and then retry this installation.
MSI (s) (78:88): Product: GeoMedia Professional -- Error 1925. You do
not have sufficient privileges to complete this installation for all
users of the machine. Log on as administrator and then retry this
installation.
Action ended 12:18:28: InstallFinalize. Return value 3.
Action 12:18:28: .
Action ended 12:18:28: ADVERTISE. Return value 3.
.....
and so on...
I do not see that problem if I double-click on the same MSI, same
product installation... It installs fine.
The problem occurs only when using the command line.
For example:
msiexec /jm "Myinst.MSI" /l* mylog.txt
Thank you
Carolyn Napier (MS)
an administrator in order to perform per-machine advertisements. Are you
running as an administrator on the machine?
Double-clicking the .msi initiates an install. The context of the
installation is determined by the package authoring and more specifically by
the value of the ALLUSERS property. If ALLUSERS is 1, then the installation
will be per-machine (in which case you'll require administrative privileges
to perform the install). If ALLUSERS is not set, then the installation will
be per-user. If ALLUSERS is 2, then the installation will be per-machine if
you are an administrator; otherwise it will be per-user. Note that the
ALLUSERS behavior is different on Win9X. See the Windows Installer MSDN
documentation for more information.
If you want to perform an advertisement of the product to a user, then use
/ju. In summary, you must be an administrator in order to perform a
per-machine installation (ALLUSERS=1) or perform a per-machine advertisement
(/jm).
Hope this helps,
- Carolyn Napier (MS)
Microsoft Windows Installer Team
Check out the Windows Installer FAQ at:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.a
sp>
Please do not send email directly to the alias used to post to the
newsgroup. The alias is for newsgroup purposes only. This posting is
provided "AS IS" with no warranties, and confers no rights.
"Dominique" <dgsc...@ingr.com> wrote in message
news:3bcef786.02111...@posting.google.com...
Louis
"Per machine" installations require elevated privileges. It seems you
are running your installation package as a "non privileged" user:
search for the value of the property "Privileged" in your log file, it
will be defined if and only if you are a "privileged" user.
Here are some links you may find of interest
- http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/privileged_property.asp
Hopes this help, Louis
dgsc...@ingr.com (Dominique) wrote in message news:<3bcef786.02111...@posting.google.com>...
Dominique
Yes I have administrator privileges on my machine.
Yes I am an administrator on my machine.
ALLUSERS is set to 1 in the Property table of the MSI in question.
I still do not understand why it works fine if I double click on the
MSI but it does not work via the command line.
You said: "Double-clicking the .msi initiates an install."
Does that mean that using the command line does not initiate an
install?
Why is there a difference in the behavior between the command line and
the "Double-clicking" the MSI?
Thank you for your help
"Carolyn Napier \(MS\)" <cna...@microsoft.com> wrote in message news:<uPVtt5hiCHA.2512@tkmsftngp11>...
Dominique
Here is the section of my log file related to elevated privileges:
.............
Property(S): Privileged = 1
Property(S): Setup = Setup
Property(S): RepairIcon = repairic
Property(S): RemoveIcon = removico
Property(S): ButtonText_Ignore = &Ignore
Property(S): PROMPTROLLBACKCOST = P
Property(S): ButtonText_Finish = &Finish
.............
Privileged = 1 shoudl be ok?
I am also going to search the links you sent me.
I appreciate the help.
Dominique
louis_...@silanis.com (Louis) wrote in message news:<f17510.021112...@posting.google.com>...
Dominique
being advertised correctly.
When using the command line
The shortcuts are not created but the registry entry
"HKEY_CLASSES_ROOT\Installer\Products\...\..." is created.
So when I re-typed the command line
msiexec /jm "Myinst.MSI" /l* mylog.txt
I received the error:
"You do not have sufficient privileges to complete the installation
for all users of the machine. Log on as administrator and then retry
the installation."
I have to remove the the application before retyping the command line
msiexec /jm "Myinst.MSI" /l* mylog.txt
So my now problem is: why the shortcuts are not advertised correctly
when I use the command line with the option jm or ju?
The same MSI via the "double-clik" installs the product without any
problem at all.
The document "Certified for Microsoft® Windows® Test Plan" refers to:
... Advertised applications look just like installed applications to
the computer user. They have shortcuts on the Start menu, they can be
installed or customized using Add//Remove Programs, and they will be
installed when the user opens one of the application's native files.
But, only the shortcuts, options and native file associations are
created on the computer by the advertising process. The application is
not actually installed until the first time the user opens a shortcut
or a native file, or uses Add//Remove Programs to customize the
"installation." ...
Any help is very welcomed
Thank you
Carolyn Napier (MS)
here:
/jm performs a per-machine advertisement of the application. When an
application is advertised, the Windows Installer will write its own private
configuration information as well as the relevant application entry points
to the machine. No files are actually installed. The entry points that are
written are the CLSID, file extension, etc. information as well as the
advertised shortcuts. Advertised shortcuts are shortcuts tied to a feature
in the product. It's with this information that you can get self-repair of
an application when it is invoked from an advertised shortcut. The /jm
switch only processes the AdvtExecuteSequence table in the installation
package.
When you double-click the package, you are actually performing an install
and not an advertisement. The actual files will be installed on the
computer. The InstallUISequence and InstallExecuteSequence tables are
processed in this scenario. Note that the InstallUISequence table is not
processed when the UILevel is none or basic.
The error in your situation results from the fact that you are attempting to
"re-advertise" the product. This isn't allowed. You have to uninstall the
product first. Your first attempt at advertising the product succeeded.
You mention that the shortcuts are not created. I take it this is why you
keep attempting the advertisement again. During advertisement, only
advertisable shortcuts will be created. These are shortcuts where the
Target column of the Shortcut table refers to a feature in the product (eg.
a feature in the Feature table). Non-advertisable shortcuts will not be
created during advertisement. These are shortcuts directly to a file.
During an actual installation, both advertisable and non-advertisable
shortcuts will be created since the files are actually being installed.
Given the nature of advertisement, only shortcuts that could result in an
installation will actually be placed on the computer. The reason for this
is that there needs to be a hook inside the shortcut to tell the Installer
what files to install when the shortcut is double-clicked.
As an example, here's a sample entry for a package containing an
advertisable and non-advertisable shortcut. Let's assume that components
Component1 and Component2 exist, Feature1 is an advertisable feature in the
product, and Test.exe is a File in the file table:
Shortcut table
AdvtShortcut ProgramMenuFolder AdvtShortcut Component1 Feature1
{NULL} "Advertisable Shortcut" {NULL} myicon.exe 0 {NULL}
{NULL}
NonAdvtShortcut ProgramMenuToolsFolder NonAdvtShortcut Component2
[#Test.exe] {NULL} "Nonadvertisable Shortcut" {NULL} myicon.exe
0 {NULL} {NULL}
If I were to double-click this package, then I would end up with two
shortcuts on my computer. One would be in the ProgramMenuFolder and one
would be in the ProgramMenuToolsFolder.
However, if I were to advertise the package using /jm (or /ju), then I would
end up with only one shortcut on the computer. This would be the
AdvtShortcut because it's the only advertisable shortcut.
I think your next step should be to look at the package you are attempting
to advertise and see what types of shortcuts are actually listed in the
Shortcut table. And additionally thing to be aware of is that advertisement
can only advertise features that are advertisable. If you have a feature
whose attribute includes msidbFeatureAttributesDisallowAdvertise, then the
feature cannot be advertised.
Hope this helps,
- Carolyn Napier (MS)
Microsoft Windows Installer Team
Check out the Windows Installer FAQ at:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.a
sp>
Please do not send email directly to the alias used to post to the
newsgroup. The alias is for newsgroup purposes only. This posting is
provided "AS IS" with no warranties, and confers no rights.
"Dominique" <dgsc...@ingr.com> wrote in message
news:3bcef786.02111...@posting.google.com...