Operating System - HP-UX
1834811 Members
2755 Online
110070 Solutions
New Discussion

MS Word File corruption on HP-UX V11 using Samba

 

MS Word File corruption on HP-UX V11 using Samba

I have a problem that happens to only one group of users.
When a word file is saved over a network to a HP-UX server via Samba, the file
gets corrupted after doing cut & paste or any text formatting: part of the document gets
replaced by random characters, most appearing as rectangles on the
screen, some as new lines, columns or page breaks.
5 REPLIES 5
KapilRaj
Honored Contributor

Re: MS Word File corruption on HP-UX V11 using Samba

I am nothing in samba ,

but this happens when a word / any formatted file transfered through ftp in ascii mode . Check up for some setting in samba to transfer the file in binary mode.

Good luck


kaps
Nothing is impossible
Ravi_8
Honored Contributor

Re: MS Word File corruption on HP-UX V11 using Samba

Hi,
hp-ux doesn't support MS-word. so convert the ms-word file to .txt and do ftp or nfs to hp machine. even then too the file will not be in it's original format. it contains the linefeeder(^M) which can be eliminated using 'sed'
never give up
Herve BRANGIER
Respected Contributor

Re: MS Word File corruption on HP-UX V11 using Samba

Hi,

Really strange problem. We use Samba with HPUX
11 on our servers without this kind of problem.

Give Samba version and explain what is this
special "group of users". If you can join your
smb.conf to see if there is something wrong on
it... Perhaps somebody can compare with his own
system...

Did you look in your logs to see if there are
error messages ?

Regards,


Herve


Re: MS Word File corruption on HP-UX V11 using Samba

Sorry to all more information supplied - please see the question I reposted. Thanks for all contributions
rainer doelker
Valued Contributor

Re: MS Word File corruption on HP-UX V11 using Samba

Anna,

have you tried to turn on samba in debug mode? I'd suggest to use (in smb.conf)
debug level = 5
debug pid = Yes
log file = /var/opt/samba/log.%m
max log size = 1000 # eventually more

Before doing a saving attempt of the word file sero the logs in a way like (not tested)
# for i in `ls |grep log. `
>do
>cat /dev/null > $i
> done

Then after saving collect the logfile from the client and examin it.

Some additional questions may be: Which Office package on wich OS are the affected users working with? What is the samba-version you are using? How is "oplocks" set? What else is common with the group of users, are they NIS users?

FYI: See as well the samba form HP called CIFS/9000: http://www.software.hp.com/ click on "network & system administration" (currently based on SAMBA2.0.7)