Bug 9712 - Cannot copy file on share (error 0x8007003A) Windows Vista 32bit (No service packs)
Summary: Cannot copy file on share (error 0x8007003A) Windows Vista 32bit (No service ...
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.0.3
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-12 14:49 UTC by Kieran McCusker
Modified: 2013-03-13 12:37 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kieran McCusker 2013-03-12 14:49:59 UTC 
Hi

Trying to copy a file on a share using Window Vista gives a windows message Error: 0x8007003A the specified server cannot perform the requested operation

the same file can be moved without problem. There is nothing in the log even with log level set to 10 except that the machine log is reset and starts with change_to_root_user

smbstatus shows

Locked files:
Pid          Uid        DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
19664        1000       DENY_WRITE 0x12008b    RDWR       BATCH            /home/mccuskk   portal.dump.backup   Tue Mar 12 14:40:38 2013
19664        1000       DENY_ALL   0x16019f    RDWR       BATCH            /home/mccuskk   Desktop/portal.dump.backup   Tue Mar 12 14:40:38 2013

This is on a clean fc18 installation, the initial smb.conf was a very basic simple share = user. I assumed it was working until I deployed to my users.

Any ideas? I will be happy to try things for you

Many thanks

Kieran
Comment 1 Kieran McCusker 2013-03-12 14:51:36 UTC 
I should of said that the problem occurs with any file
Comment 2 Kieran McCusker 2013-03-12 14:53:07 UTC 
Also directories get copied but not the files in them
Comment 3 Kieran McCusker 2013-03-13 12:36:48 UTC 
I have discovered that the workstations are running Vista 32bit. When I upgraded a workstation to Vista service pack 2 the problem disappeared. Wish I knew this before I started!