I have a recent-model Mini at work running Mavericks server, acting as a file server for about a dozen Macs and half dozen Windows machines. I had major issues with Apple's SMBX server through 10.8, but 10.9 has mercifully resolved enough of the problems that it's now more or less usable.
However, I'm still getting one regular complaint, and it's from both Windows and Mac (10.9) users: While working with Office documents stored on the server, periodically Office will throw an error that the file is in use and cannot be modified, at which point the user has no choice but to save a copy and work from that.
These spurious locks aren't just Office temp files, they affect everything--you also can't use the Finder or Windows Explorer to delete the file until the server has been rebooted, although if you control the Server directly you can use its Finder directly to delete them without a reboot.
My assumption was that the Mac user I've been getting complaints from is connecting via SMB2 rather than AFP, but the default connection appears, at least when I've checked, to be via AFP, so I'm not 100% sure that it's SMBX to blame.
I could turn up a couple of people complaining about similar problems in searches, but no solutions, and not even any particularly good info. Is anyone else seeing this, and does anyone have a suggestion of what I might try to fix it other than waiting for Yosemite?
However, I'm still getting one regular complaint, and it's from both Windows and Mac (10.9) users: While working with Office documents stored on the server, periodically Office will throw an error that the file is in use and cannot be modified, at which point the user has no choice but to save a copy and work from that.
These spurious locks aren't just Office temp files, they affect everything--you also can't use the Finder or Windows Explorer to delete the file until the server has been rebooted, although if you control the Server directly you can use its Finder directly to delete them without a reboot.
My assumption was that the Mac user I've been getting complaints from is connecting via SMB2 rather than AFP, but the default connection appears, at least when I've checked, to be via AFP, so I'm not 100% sure that it's SMBX to blame.
I could turn up a couple of people complaining about similar problems in searches, but no solutions, and not even any particularly good info. Is anyone else seeing this, and does anyone have a suggestion of what I might try to fix it other than waiting for Yosemite?