Highlighted
Anonymous_User Absent Member.
Absent Member.
2141 views

MS Office file corruption when saved on traditional Netware volume from a Vista workstation

Hi to all,

There is a problem when saving MS Office files (.doc, .xls, .ppt..) from a
Vista workstation on a traditional Netware volume (Netware 5.1 SP8).
The Vista Workstation runs the Netware client for Vista 1.0 Update 4.
The file becomes corrupted and can't be read again and the file size is
increased (2Mb on the original file to 60Mb when saved on the Netware
volume).
The problem doesn't occur on the NSS volume which is on the same server.

Thanks for any help on this subject.

Thierry Le Floch


Labels (1)
0 Likes
10 Replies
BSchnur Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

I'd guess I'd move the data storage all over to an NSS volume --
ideally, you could add another drive (or increase a RAID5 array with
another drive) and allocate it as the new volume for data only, then
clear off data folders from the SYS volume.




--
Barry Schnur
Novell Support Connection Volunteer Sysop

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

Hi Barry,

Thanks for your answer, but it's not very satisfactory !
We use the volume SYS: to save data for almost 20 years without any problem
(we are a small company with only few users only so it's easy to control !),
from workstations with all type of OS from DOS to XP and all versions of
Netware (from 3.1 TO 6.5). And suddenly, no more possible with Vista !
You're right when you say that it's not a good practice, but anyway, this
should work....
Now the problem has been noticed with MS Office files, but what about other
type of files ?
We can suspect that this kind of problems can occur with other applications
as well !
Is-it totaly forbidden to write any data on the volume sys: ?
Hope the Novell development team for the Netware client for Vista is aware
of this problem and will solve it as soon as possible.
This is a major bug (because data are lost without warning) which must be
corrected.

About migrating data to a new volume, this can be a solution obviously, but
what about the disk space already allocated to the volume Sys: ?
As far as I know, it's not possible to reduce it and get back some space to
create an NSS Volume. So this involves either rebuild the server from
scratch, either buy a new disk.
All of this is costly and it would be simpliest to install an update of the
Netware client for Vista !

Thierry Le Floch

"Barry Schnur" <BSchnur@cox.net> a écrit dans le message de
news:MPG.2226566690a6194c98e5af@forums.novell.com...
> I'd guess I'd move the data storage all over to an NSS volume --
> ideally, you could add another drive (or increase a RAID5 array with
> another drive) and allocate it as the new volume for data only, then
> clear off data folders from the SYS volume.
>
>
>
>
> --
> Barry Schnur
> Novell Support Connection Volunteer Sysop


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

I suggest that you eliminate the antivirus software on the server or the PC
as a cause of the problem.


"Thierry Le Floch" <tlefloch@pgs.fr> wrote in message
news:vEbvj.3316$Ec7.3230@kovat.provo.novell.com...
> Hi Barry,
>
> Thanks for your answer, but it's not very satisfactory !
> We use the volume SYS: to save data for almost 20 years without any
> problem (we are a small company with only few users only so it's easy to
> control !), from workstations with all type of OS from DOS to XP and all
> versions of Netware (from 3.1 TO 6.5). And suddenly, no more possible with
> Vista !
> You're right when you say that it's not a good practice, but anyway, this
> should work....
> Now the problem has been noticed with MS Office files, but what about
> other type of files ?
> We can suspect that this kind of problems can occur with other
> applications as well !
> Is-it totaly forbidden to write any data on the volume sys: ?
> Hope the Novell development team for the Netware client for Vista is aware
> of this problem and will solve it as soon as possible.
> This is a major bug (because data are lost without warning) which must be
> corrected.
>
> About migrating data to a new volume, this can be a solution obviously,
> but what about the disk space already allocated to the volume Sys: ?
> As far as I know, it's not possible to reduce it and get back some space
> to create an NSS Volume. So this involves either rebuild the server from
> scratch, either buy a new disk.
> All of this is costly and it would be simpliest to install an update of
> the Netware client for Vista !
>
> Thierry Le Floch
>
> "Barry Schnur" <BSchnur@cox.net> a écrit dans le message de
> news:MPG.2226566690a6194c98e5af@forums.novell.com...
>> I'd guess I'd move the data storage all over to an NSS volume --
>> ideally, you could add another drive (or increase a RAID5 array with
>> another drive) and allocate it as the new volume for data only, then
>> clear off data folders from the SYS volume.
>>
>>
>>
>>
>> --
>> Barry Schnur
>> Novell Support Connection Volunteer Sysop

>



0 Likes
BSchnur Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

I understand what you are saying here, but understand further that as
the problem is specific to Vista one issue is that the workstation OS
change is the significant variable.

That being said, Novell made changes in their OS so that NSS volumes
have features not available in TFS (they have been going that way
increasingly).

How large is the SYS volume?



--
Barry Schnur
Novell Support Connection Volunteer Sysop

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

It is not SYS that the issue is with, it is that SYS is a Traditional
File System format.

If you moved SYS to NSS the issue would most probably disappear.

--
Timothy Leerhoff
Novell Volunteer Sysop
"Some people drink from the fountain of knowledge, others gargle"
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

Yes, I agree, but is it possible to move the SYS: volume from traditional
to NSS with Netware 5.1 SP8 ?
If yes, how ?
I didn't see any tool for that in nwconfig.

Thierry
PGS Progisoftware



"Timothy Leerhoff" <tleerhoffNO@SPAMqwest.net> a écrit dans le message de
news:RsDvj.3917$Ec7.2369@kovat.provo.novell.com...
> It is not SYS that the issue is with, it is that SYS is a Traditional
> File System format.
>
> If you moved SYS to NSS the issue would most probably disappear.
>
> --
> Timothy Leerhoff
> Novell Volunteer Sysop
> "Some people drink from the fountain of knowledge, others gargle"


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

Hello!

> Now the problem has been noticed with MS Office files, but what about other type of files ?
> We can suspect that this kind of problems can occur with other applications as well !
> Is-it totaly forbidden to write any data on the volume sys: ?
> Hope the Novell development team for the Netware client for Vista is aware of this problem and will solve it as soon as possible.


OT, but Windows Home Server has a similar problem:

http://arstechnica.com/journals/microsoft.ars/2008/02/22/list-of-programs-associated-with-whs-bug-grows

MS dev. team is trying to solve the problem:

http://www.wegotserved.co.uk/2008/02/21/data-corruption-bug-list-of-potential-applications-affected-grows/

Until the fix is issued, my advice is do not edit any file in any application
directly on your home server. Copy the file to a home computer, edit it,
and then copy it back again.



Regards, Roman


0 Likes
BSchnur Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

> OT, but Windows Home Server has a similar problem:
>
> http://arstechnica.com/journals/microsoft.ars/2008/02/22/list-of-programs-associated-with-whs-bug-grows
>
> MS dev. team is trying to solve the problem:
>
> http://www.wegotserved.co.uk/2008/02/21/data-corruption-bug-list-of-potential-applications-affected-grows/
>

> Until the fix is issued, my advice is do not edit any file in any application
> directly on your home server. Copy the file to a home computer, edit it,
> and then copy it back again.
>

>

You mean Microsoft is not expecting Novell to solve the problem for
them? <smile>.


--
Barry Schnur
Novell Support Connection Volunteer Sysop

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volumefrom a Vista workstation

The tool used is VCU. It does require free disk space the same size as
the volume to be migrated.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Marcel_Cox Absent Member.
Absent Member.

Re: MS Office file corruption when saved on traditional Netware volume from a Vista workstation

Thierry Le Floch wrote:

>Yes, I agree, but is it possible to move the SYS: volume from traditional
>to NSS with Netware 5.1 SP8 ?
>If yes, how ?


No. It's not possible. On NetWare 5.x, the SYS volume can only be TFS. I
think Andrew missed the fact that you were running NetWare 5.1 as he
mentioned VCU, a tool only available on NetWare 6.x

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel_Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.