Discussion:
unable to save document on the network share
(too old to reply)
Zeilkman
2009-02-21 10:17:30 UTC
Permalink
Hi,
I just updated an Office 2003 to Office 2007 in one of our PC.

Users can save attachments or new documents to the local desktop or my
docuements, but they can not save new documents to a network share.
The Error ('filename' can not be found. Check your spelling or try
a different path.) This includes Word, Outlook attachments,
Excel.....

The file can be coppied to the network drive after it is save locally.

They can modify existing documents on the network and save but not
create new documents. As part of trying to troubleshoot the
situation, I have given users full control over the share.

This error does not occur in other desktop with same configuration
neither with Office 2003.
Also I installed the office 2007 SP1 but no chnage, I still have this
problem.

thnaks for helping on this

S.
Mark
2009-06-17 01:16:01 UTC
Permalink
Ditto:, they want you to either disconnect any mapped or network drives, or
ask you Anti-viral to ignore network drives.

Which is basically ignorant.

There must be a better fix Microsoft.

Why can I save to C:\ or a flash drive and not to a permissioned shard
network drive?
Post by Zeilkman
Hi,
I just updated an Office 2003 to Office 2007 in one of our PC.
Users can save attachments or new documents to the local desktop or my
docuements, but they can not save new documents to a network share.
The Error ('filename' can not be found. Check your spelling or try
a different path.) This includes Word, Outlook attachments,
Excel.....
The file can be coppied to the network drive after it is save locally.
They can modify existing documents on the network and save but not
create new documents. As part of trying to troubleshoot the
situation, I have given users full control over the share.
This error does not occur in other desktop with same configuration
neither with Office 2003.
Also I installed the office 2007 SP1 but no chnage, I still have this
problem.
thnaks for helping on this
S.
wcranmer
2009-07-09 18:38:30 UTC
Permalink
I am encountering this problem on 2 different PC's both using WinXP and
Office 2007 saving to a network share folder. It only happens with new
files. They can be saved locally.
I get error "<\\networkshare\filename> cannot be found. Check your
spelling or try another path."

Any suggestions?
--
wcranmer
------------------------------------------------------------------------
wcranmer's Profile: http://forums.techarena.in/members/113084.htm
View this thread: http://forums.techarena.in/ms-office-support/1127608.htm

http://forums.techarena.in
Mark
2009-07-09 19:41:01 UTC
Permalink
I'll bet you are using CA\Etrust.


Call them... you need the updated INORT.EXE fle, save it.

stop Etrust from run: services.msc

replace the inort.exe file in CA

restart the services

works fine.

they can and will login and do it for you.

Hope this helps

Mark
Post by wcranmer
I am encountering this problem on 2 different PC's both using WinXP and
Office 2007 saving to a network share folder. It only happens with new
files. They can be saved locally.
I get error "<\\networkshare\filename> cannot be found. Check your
spelling or try another path."
Any suggestions?
--
wcranmer
------------------------------------------------------------------------
wcranmer's Profile: http://forums.techarena.in/members/113084.htm
View this thread: http://forums.techarena.in/ms-office-support/1127608.htm
http://forums.techarena.in
wcranmer
2009-07-10 20:24:27 UTC
Permalink
Thanks for the heads up on the CA issue. In this case it was a matter o
a setting in the AV that was checked by default to protect the networ
drives.
Per CA they will be addressing that in a future update

--
wcranme
-----------------------------------------------------------------------
wcranmer's Profile: http://forums.techarena.in/members/113084.ht
View this thread: http://forums.techarena.in/ms-office-support/1127608.ht

http://forums.techarena.i
x***@gmail.com
2013-03-07 15:32:51 UTC
Permalink
I had this same issue, what I did was synced the user's documents and that fixed the problem.
Loading...