Right, challenge for you all

[Dead_One]

upgraded a pc to win xp, new pc etc.
using word 97 when the user saves to a network share , they get an error saying unable to save, check hard drive isnt full or permissions etc.
Every other app works fine
have used sr1 and 2a, then unisinstalled and used sr 1 and 2b, all fixes etc, nothing solves it
user on an identical pc has no problems

any ideas?

[master baits]

its a newtwork problem , as if you didnt already know that , is both pcs xp , is the hd mounted or just shortcutted

[Dead_One]

how is it a network problem?
there were no problems with the previous desktops, using the same network set up.
and why would it only show up in word?

[HRGIGER]

Sounds like permissions problem, try saving file locally then use explorer to move to network share location.

Attach to share by mapping drive using connect as administrator account on computer running the share to test permissions?

Both computers in same domain with account for pc accessing share?

[Dead_One]

permissions, mmm.
Unfortunatley they can save to that location from all other apps, so permissions are out.

[HRGIGER]

You didn't mention what type of share?
If its NFS then:
Case 1: Saving a Do***ent
When you save a do***ent, the following error message may occur:

Word cannot save or create this file. Make sure the disk is not write protected.


-or-

You are able to save to the local drive but receive the following message when you attempt to save to a network drive:

Word cannot save this do***ent. Be sure the drive is not full or write-protected.
NOTE: You may be able to use My Computer or Explorer in Windows 95 (or File Manager in earlier versions of Windows) to move do***ents to the network drive, but you are unable to access the do***ents directly from within Word for Windows.

CAUSE
These error messages occur when Word cannot create a docfile (the OLE2 file format). This happens when your connection to a PC-NFS network drive does not include file locking (also known as mandatory record locking). File-locking functionality does not exist when:


You create the connection WITHOUT using the /NS ("no share") switch.

For example:

NET USE F: SUNNY:/HOME/WINWORD

-or-


You create the connection WITH the /MS ("must share") switch. For example:

NET USE F: SUNNY:/HOME/WINWORD /MS

Both of the examples above create a connection to a PC-NFS network that does not include file locking. Therefore, Word cannot create docfiles.

RESOLUTION
Change the /MS switch to /NS, or add the /NS switch if it is missing from your network connection command line. The following sample command line creates a connection on a PC-NFS network that supports file locking:

NET USE F: SUNNY:/HOME/WINWORD /NS

[HRGIGER]

To test for file locking problem save file from word as word 2 doc, see below.

CAUSE
You cannot save Word do***ents on a network drive if your network operating system file-sharing and file-locking capabilities are not turned on or are set too low. You can save in other file formats on a network drive because the file converters do not use the Storage.dll file, which requires file-locking capabilities.
RESOLUTION
To avoid these error messages, have your network administrator turn on or increase the range-locking settings for your network.

For more information about the file-sharing and file-locking capabilities of your network, refer to your network do***entation.

To temporarily work around this "Cannot save or create file" problem, do one of the following:


Save your do***ent to a local hard disk or floppy disk. -or-
Save the do***ent on the network drive in a different file format, such as Word For Windows 2.0.
Save the file to the local hard drive and move it to the network drive. You will also need to have your network administrator remove this file if nobody is using it.

[Dead_One]

you found the bit on the knowledge base about this then?

there are 2 articles on this, and all of the solutions in this don't work.
aparantly it could be something to do with user profiles, but i havent investigated that yet.
will be trying tomorrow.

[Dead_One]

have tried the /ns thing, and w2k and wxp don't seem to think it exists, wanna shed any light?

[HRGIGER]

Lifted from technet KB117703

[Dead_One]

try article 108918

now, if i can only find an article relating to changing the ranglocking settings... :-)

ms link (http://support.microsoft.com/default.aspx?scid=kb;EN-US;108918)

is a bit of a nightmare this problem.
btw, server is a dc , running w2k sbs.