kellnerp
Mechanical
- Feb 11, 2005
- 1,141
My file server is based on Linux and Samba 3.4.0. When using SolidWorks on multiple clients I sometimes get Windows-Delayed Write Failed errors and sometimes SolidWorks just refuses to write files that were opened on the file server. Writing the file locally will typically work.
Looking at MSoft's KB article 330174 the first thing to look at is hardware. However, as mentioned this error occurred on the file-server which was networked. This leads to another MSoft KB article 812937 which explains why this problem can happen.
MSoft article 812937 gives enough information to solve the problem using Samba.org's help documents. Chapter 08 discusses oplocks. The settings that seem to do the job on shares that server SolidWorks files are:
The last entry, level2 oplocks = yes is important as it allows Samba to deal with SolidWorks changing files from read only to read in a multi-user environment.
TOP
CSWP, BSSE
"Node news is good news."
Looking at MSoft's KB article 330174 the first thing to look at is hardware. However, as mentioned this error occurred on the file-server which was networked. This leads to another MSoft KB article 812937 which explains why this problem can happen.
MSoft article 812937 gives enough information to solve the problem using Samba.org's help documents. Chapter 08 discusses oplocks. The settings that seem to do the job on shares that server SolidWorks files are:
Code:
[customers]
comment = Customers
path = /mySolidWorksFiles
writeable = yes
browseable = yes
...
hide files = /~*.sld*/
hide dot files = yes
fake oplocks = no
oplocks = yes
level2 oplocks = yes
TOP
CSWP, BSSE
"Node news is good news."