Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: damjan on April 20, 2007, 01:01:02 PM

Title: Trouble with samba share and MS office documets
Post by: damjan on April 20, 2007, 01:01:02 PM

Hi,

We have simple network with SME 7.1.3 and couple of Win XP machines.
MS office documents ( word , excel etc.) are located on ibay which is used as a share drive.
The user are accessing the share according the ibay settings and username/password which are identical on SME and XP machines.

Users open the documents direct from share (ibays).

The problem is that when they wanted to save the MS Word documents they gets an error:

"Word cannot complete save due the file permission problem."

F: /....document.doc

It should be noted that this file is opened only with single user.

The situation is even more complex that we can not reproduce the exact error but it appears randomly.

Br
D.

Title: Domain or Workgroup
Post by: reubanks on April 20, 2007, 06:01:14 PM

Are your users logging into the server as a Domain User or through a Workgroup?

What type of hardware are you using for the Server and PCs? Are you using Gigabit Ethernet or 10/100Mb? (Switches, NICs, Cat5e/6 wiring, etc.)

Thanks, Randy

Title: Trouble with samba share and MS office documets
Post by: damjan on April 23, 2007, 11:14:52 AM

hi,

They are logged through workgroup.
SME is set: Workgroup and domain controller -> Yes

In fact there is only one ibay - with group to write access - everyone , read access -> everyone

The file attributes on thet ibay are :
764
owner name is: userok
group is: shared


The network 10/100

Title: Try this
Post by: reubanks on April 23, 2007, 06:18:53 PM

Try attaching to and logging in via the domain instead of as a workgroup.

I've had issues with workgroup shares not working well with antivirus programs and the issues went away when I changed to a domain login.

I can't guarantee anything, but it seems a good place to start.

Randy

Title: Trouble with samba share and MS office documets
Post by: damjan on May 28, 2007, 08:20:21 PM

ok the thing goes so far:
1. We establish domain controller (roaming profiles)
2. add veto oplock for *.xls and *.doc files -(according the help on this forum)
3. switch off other lockings on global scale on top of that:
oplocks = false
kernel oplocks = false
level2 oplocks = false
4. updated SME on the latest update


Saving is now working but we have a LOT of temp files form ms office on working directory :
~WRLxxxxx.TMP
~WRDxxxxx.TMP

This happens every time we open the file , change it and save it on the same location. It happens on domain or workgroup mode.

br
D

Title: Trouble with samba share and MS office documets
Post by: girkers on May 29, 2007, 08:32:21 AM

These temp files should be deleted when you quit Word. I believe they are part of the autosave functionality to help you recover files if you app crashes.

Title: Trouble with samba share and MS office documets
Post by: damjan on May 29, 2007, 11:29:17 AM

unfortunately they are not. Number of tmp files depends on how much time users change and save the documents.

We also try to veto oplock *.tmp, *.TMP files but no luck.

There must be some critical error on samba on SME 7.1.x since this kind of errors didn't happen on SME 6.01 (hardware stayed the same).

br
D

Title: Trouble with samba share and MS office documets
Post by: alt-network on June 22, 2007, 07:44:06 PM

We have been experiencing the same error.  

1) When trying to WinZip files to a network drive.
2) When trying to save Word, Excel or jpg files.

Any solutions yet????

Title: Re: Trouble with samba share and MS office documets
Post by: alt-network on September 21, 2007, 11:53:30 PM

Has anyone find why and how to fix the issues with the MS office temp files note removing after closing the document?

I am still having the issues with SME 7.2.

Thanks

Title: Re: Trouble with samba share and MS office documets
Post by: chris burnat on September 22, 2007, 02:55:15 AM

The obvious next step would be to fill a Bug Report at Bugzilla if indeed this issue has emerged since moving from VS6 to version 7.  At the very least, the culprit will be identified, may it be Samba or MS.  Please fill a bug report providing details of your system, and please be prepared to provide additional information as requested by the Dev Team.
Thanks.
chris