Access Control not being set for folders

[rlangham]

have some folders that I need to assign special access permissions to. I am needing read/write access for the NETWORK SERVICE and the CREATOR OWNER. You can see assign these values via the Security settings when right clicking on a folder.

In the Designer under Access Control, I have created share items for

Named User Account Group -> NETWORK SERVICE
with Read/Write access, Object Type -> File System,
Operation -> Set Chosen Users with Access Rights

I have done same for CREATOR OWNER.

The NETWORK SERVICE works fine on my XP system, but when running on Windows 2003 Server 64-bit, they are not set. The NETWORK SERVICE by default is not included in permissiosn for a folder. In this case, it is not persent in the list of values, so no value at all being set for it.

Any way to debug or track this down?

Ron

[MichaelNesmith]

Need more details...like the code you're using to create, etc.

Also there are similar posts on this forum - I'd do a search if my question has already been answered before.

[rlangham]

After the ApplyInstall command in the 2 If SUCCESS blocks, I have the following...

Set Read Write Permissions on File System Object "$TARGETDIR$" for NETWORK SERVICE
Set Read Write Permissions on File System Object "C:\\OracleDrivers" for NETWORK SERVICE

The permissions are set fine on XP, but not set on Windows 2003 Server 64-bit.

fyi, the OracleDrivers directory is created early on in the install, I install files in this directory and it is created ok.

Thanks,
Ron

[MichaelNesmith]

You may need to set 64 bit install mode, especially for $TARGETDIR$; also see if manually creating the folders using Call DLL Function, and then immediately after that setting permissions helps.

[rlangham]

Thanks for your response. Yes, the 64 bit mode is set. I set this at the very top of the script before almost anything is done. One way of knowing this is set correctly is that the files do get installed in the correct x64 Program Files target folder.

I do not attempt to set the folder permissions until after the ApplyInstall (e.g. after all is installed ok). I have put a MessageBox in the install at this point and verified the directories are created before trying to set the permissions.

I have not tried the Call DLL, been using high-level languages so long no sure what Win32 API method to use for creating a folder , but it really looks like this is probably not the issue in my testing, the directories are created fine and early in the install sequence.

One other note, the c:\\OracleDrivers directory is independent of 64-bit or 32-bit, it was a hardwired directory set in the install. I verified it was also present before applying the permissions, and it to failed to have the NETWORK SERVICE permissions applied to it.

Thanks,
Ron

[MichaelNesmith]

I'd create an empty script that does nothing other than set permissions on a hard-coded folder (just one line of MSIcode). You can create that folder in explorer and then build the InstallAware setup and see if it applies any permissions, or not.

If that doesn't work, let me know so I can escalate to R&D.

[rlangham]

I did this test and it fails only if the 64-bit mode is set under Application Requirements.

Test #1
Do not check 64-bit mode in Application Requirements
Assigned RW permissions to hard-coded folder for NETWORK SERVICE
Run test on Windows 2003 Server 64-bit
Permissions were set OK

Test #2
Check 64-bit mode in Application Requirements
Assigned RW permissions to hard-coded folder for NETWORK SERVICE
Run test on Windows 2003 Server 64-bit
Permissions were NOT set. The NETWORK SERVICE does not even appear in the Security settings

Ron

[MichaelNesmith]

That's quite odd...care to post the actual scripts that worked and failed?

[rlangham]

Here is the test project. It has the 64-bit mode set. I used the same script for both tests, I just toggled the 64-bit mode setting in the Design \\ Application Requirements area.

It will try to set permissions for NETWORK SERVICE on c:\\ron directory

I would delete the directory and re-create between each test.

Thanks,
Ron

File Attached:

test.zip

[rlangham]

Michael, you mentioned above that you could escalate this task to R&D, curious if anything done with this. Desperately trying to get away from InstallShield.

Thanks,
Ron