problems saving to network

[AntunB]

Getting error messages when saving to network sghares


All machuines are running windows XP SP2 - office xp sp3

saving from excel
The document was saved successfully, but excel cannopt re-open it because of a sharing violation


when you try and open the file you saved
this file is not in a recognizable format


saving from word
the save failed due to out of memory or disk space

most of the problems are with excel


the share is DFS

thanks

 

[tf1]

Has this always happened or was it the Win XP SP2 update?

What's on the server (OS and SP level)?

In Word, go to Tools, Options, File Locations and make sure that any network paths are using UNC addressing and not mapped drives.




Regards: tf1

 

[AntunB]

can i ask y would UNC addressing be a problem?



It used to be on a novell share, since we converted to windows we are having troubles,

problems are with xp, xp sp1, xp sp2


server is windows 2003


its only happening to a few computers

 

[AntunB]

also microsoft excel has not got an option to set the UNC path,

most of our problems are with excel

 

[AntunB]

oh and another question,

could the drive mapping be too long?

drive is:

\\server.com\data$\users\user

 

[AntunB]

i do not think it is a long path thing, i saved to a shorter path and still same problem


the file is created, but when open in notepad it just has a bunch of spaces in it,

i tried saving in different formats, csv, html, workbook 4

wen i save it to excel 97 format it half works, in that when i open it, it has all weird characters in it, but no spaces


any ideas? thanks

 

[tf1]

Mapped drive paths look fine. If you set paths in Word to use UNC addressing (Tools, Options, File Locations), it will also change the default Workgroup template folder for Excel.

Since Office 2000, UNC paths are needed, especially for Word network locations: in Word 2000, you had to open Support8.dot and run the macros and choose the option to force UNC addressing.


Regards: tf1

 

[AntunB]

ok ill try that

has ne1 else got any ideas?

thanks alot

 

[AntunB]

that UNC path did not work.....

could it be the way microsoft saves excel files?


has any1 got any more solutions?
thanks

 

[tf1]

It could be Norton Anti Virus: Do you use NAV or has it every been installed (e.g. a 3-month trial version preinstalled?), if so which version?

tf

Regards: tf1

 

[AntunB]

nope

we use sophos anti virus,

we have 400 or so users here, and only a handful hav this problem.

 

[AntunB]

ok this is what i have done

* I have changed to use UNC paths and not mapped drives.
* I have removed the anti-virus program
* I have tried saving in different formats (ie. xl95, xl97, txt, csv ect...)



and it all does the same thing. an error comes up saying "The document was saved successfully, but excel cannopt re-open it because of a sharing violation"

if you open the file you get "Unrecognized Format"

if you try and open the same file in notepad there are only spaces.

If you open a working xls file it has all sorts of characters.....

so it is just saving empty files, but the file size is the same.


Corrupt file size = 13,824 bytes
total characters = 13824

Good file size = 13,824 bytes
total characters = 13657


so does anyone know why this is happening? is there a tool i could use to test what is going on when the file saves? excel isn't saving correctly.....

 

[petrosky]

Hi,

Whilst not exactly your problem, it might be worth looking at this from microsoft.

http://support.microsoft.com/?kbid=297024

HTH.

Peter

Remember- It's nice to be important,
but it's important to be nice

 

[AntunB]

ok i have been searching around, and it could have something to do with the novell client... so i will remove it and see what happens.

ill test it out on monday, please anyone with suggestions please help

 

[AntunB]

Ok the problem has now been resolved.


It is the novell client. We are migrating to full windows.

by removing the novell client it also makes the network quicker

 

[Dollar]

FYI: I've seen the problem in a non-Novell environment as well. The problem is normally resolved by setting the NIC to 100 Full and the catalyst to 100 Full as well, to stop auto-negotiation of the network speed.

 

[AntunB]

we have 10mbit network cards.....


so that could be the problem then?