Bug 3665 - problem installing programs deployed with "Wise Installation Wizard"
Summary: problem installing programs deployed with "Wise Installation Wizard"
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.14a
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2006-04-07 16:49 UTC by Christoph Fuchs
Modified: 2006-04-09 10:18 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Fuchs 2006-04-07 16:49:46 UTC
When I install a commercial program with its "Wise Installation Wizard" setup-tool to a samba-share (with drive letter assigned) and the file(s) the installation-program wants to copy do already exist I get an error like that: 

"The file "foobar.txt" could not be opened. Please check that your disk is not full and that you have access to the destination directory. Permission denied."

The permissions are alright, I can rename, delete, create, modify, ...

Instead, when using a windows server all the old files get correctly overwritten.

At <www.in.tum.de/~fuchsc/test-setup.exe> you find a simple installation tool (made with Wise Installation Wizard) which just creates a textfile.
Try it and install the textfile to a samba share (it works). Then try it again and install it to the same location (the file from the previous run should still be there) - it will fail.

I tried it with Samba 3.0.14a, 3.0.22 and the "trunk"-branch from the subversion repository - everytime same behaviour.
Comment 1 Volker Lendecke 2006-04-09 10:18:08 UTC
I'm afraid this seems to be a broken application. When it finds the file in question it does successfully open it and queries the security descriptor. For some reason it finds that it can not write to the file where it perfectly can. Thus it quits operation. You can prove this by doing a 'chmod 777 hallo.txt' on the file before trying a second time. Then it works.

Until we have full NT access control lists we can not do much about this.