Hi all, We've been using samba for a couple of years now and it always running well. But last week we decided to shut down our windows server and move all solidworks file into the samba server. Since then we can't save project created by solidworks with error code shown below Access to \\sambaserver\solid-files\~$project1.SLDPRT was denied. The fact is that ~$*.SLDPRT was created on samba server, but solidworks cannot load file project1 (it still read Part1). I read somewhere that they were running well with Mandrake 8 and solidworks (solaris & samba either) but no one really showed their configuration. Well, you'd maybe saying,"So start installing Mandrake 8". I cannot do that simply that this is a running production server and we have 400GB within. Is anybody succeed with the combination of samba-3.0.10-1.4E.2 and solidworks 2008 SP3.1? FYI, I've tried the parameter veto oplock files /*.prt/*.PRT/*.sldprt/*.SLDPRT/*.slddrw/*.SLDDRW/*.sldasm/*.SLDASM/ then oplocks = Yes level2 oplocks = Yes then chmod'ed 777 the share directory (all others application like visio, openoffice, etc, can save safely into this directory). They all failed. I use RHEL 4ES and samba that came with this distro. Any help would be appreciated. Regards,
On Thu, Nov 06, 2008 at 10:24:22AM +0700, FC Mario Patty wrote:> Hi all, > > We've been using samba for a couple of years now and it always running well. > But last week we decided to shut down our windows server and move all > solidworks file into the samba server. Since then we can't save project > created by solidworks with error code shown below > > Access to \\sambaserver\solid-files\~$project1.SLDPRT was denied. > > The fact is that ~$*.SLDPRT was created on samba server, but solidworks > cannot load file project1 (it still read Part1). I read somewhere that they > were running well with Mandrake 8 and solidworks (solaris & samba either) > but no one really showed their configuration. Well, you'd maybe saying,"So > start installing Mandrake 8". I cannot do that simply that this is a running > production server and we have 400GB within. Is anybody succeed with the > combination of samba-3.0.10-1.4E.2 and solidworks 2008 SP3.1? FYI, I've > tried the parameter > > veto oplock files > /*.prt/*.PRT/*.sldprt/*.SLDPRT/*.slddrw/*.SLDDRW/*.sldasm/*.SLDASM/ > > then > > oplocks = Yes > level2 oplocks = Yes > > then > > chmod'ed 777 the share directory (all others application like visio, > openoffice, etc, can save safely into this directory). > > They all failed. I use RHEL 4ES and samba that came with this distro. Any > help would be appreciated.Please post level 10 log files so we can see what the underlying problem is. It may already be fixed in a later release. Is it possible you can test a later release on a different server to see if it addresses your problem ? Jeremy.
Quoting FC Mario Patty <fcmario76@gmail.com>:> Access to \\sambaserver\solid-files\~$project1.SLDPRT was denied.To me it sounds like a samba configuration issue. Below is an extract (for that share that works for a client of mine: path = <full path to destination directory> valid users = @<group with access to this share> write list = @<group with access to this share> force user = <user with access to this share> force group = <group with access to this share> read only = No create mask = 0755 directory mask = 07771 What happens here is that all files are owned by a user (with corresponding group) that is not a login user but one that is designated to own all files in the repository. And all users who are allowed to "fiddle" are made members of this users' group. HTH. tom
On Thu, Nov 06, 2008 at 07:16:50PM +0700, FC Mario Patty wrote:> Guys, > > I think I've finally found the cause of my problem. After playing with some > parameters, I've found out that the "culprit" is "vfs objects = full_audit" > line. Is this a known bug or a new one? Currently I commented out this line > to let those engineers working with their project from my samba server > (samba-3.0.10-1.4E.2 on RHEL 4ES). I attach the log for success working with > samba (eng24_.log - I got it while commented out "vfs objects") and the > failed one (eng24_NB.log - I got it from "vfs objects"). Now I will dig > samba.org to find out just in case nice people there have already cured this > bug(?). Thank you very much for your help.full_audit should just be a passthrough - nothing other than generation of audit messages should be going on there. The only thing it can do is slow down the server a bit, but that shouldn't cause client failures. Jeremy.