6 replies to this topic

[luke_s]

I have a problem where from a type 1 custom action (DLL function), I run a
process (CreateProcess) which in turn launches another process and calls a
function from a DLL. The DLL function calls the windows API functions -
"AdjustTokenPrivilges" and "GetFileSecurity".

When we use Windows Installer V3 everything works correctly, but when the
machine has Windows Installer V2.6, the "AdjustTokenPrivileges" function
fails with error code 1300, and then continuing on, the "GetFileSecurity"
function fails with error 1314.

I have run quite a bit of debugging on this code and I have found that the
privileges assigned to the process are exactly the same for both versions.
(I originally thought that this was the problem).

The only difference I have found (using "GetTokenInformation") is that for
Windows Installer V3, all of the privileges are NOT enabled are lableled
specifically as "disabled".

From the information i have found, this looks like a change introduced with
the Windows Installer V3 package.

Has anyone seen this before or has anyone got any ideas on what could be
causing this?

[luke_s]

Does anyone know where i can raise this with the MSI developers??

[Stefan Krueger]

You could open a support incident with Microsoft or post this in a monitored newsgroup if you have a MSDN subscription (which entitles you to newsgroup support from Microsoft)

[luke_s]

I have already posted this issue twice to the MSDN newsgroups and recieved no reply :-( But thanks for the reply anyway!

[Stefan Krueger]

Do you have a MSDN subscription? If yes: did you register your e-mail address (that you are using for posting in the newsgroup) with MSDN to get guaranteed replies?

[luke_s]

Ahh ok no I havent done that, and yes I have an MSDN account. Thanks Stefan!

[Stefan Krueger]

See here for details - a little known but useful benefit for MSDN subscribers:
http://msdn.microsof...groups/managed/