Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Word / April 2006



Tip: Looking for answers? Try searching our database.

Symantec Antivirus 10.0 breaks Word save to SMB home on Windows Server 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Terry Brady - 21 Apr 2006 05:07 GMT
Hi all,

my client has Mac OS X 10.4.6 (PowerPC) systems with Office 2004 11.2.3
and Symantec Antivirus 10.0 for Macintosh. The machines are bound to a
Windows 2003 Active Directory, with network homes provided by Windows
2003 server over SMB.

When attempting to save Word documents to any part of their network
home, users were getting the following error message: "Word cannot save
this document due to a naming or permissions error on the destination
volume."

We have temporarily resolved the problem by uninstalling Symantec
Antivirus on the client machine. Due to network restrictions we haven't
been able to get LiveUpdate to run, so we don't know whether upgrading
to SAV 10.1 would have fixed it.

I hope this info might help somebody else, but I would also like to
hear from anybody who might be able to confirm whether or not SAV 10.1
makes any difference in this situation.

Regards,
Terry
John McGhie [MVP - Word and Word Macintosh] - 27 Apr 2006 22:39 GMT
Hi Terry:

Known bug that was supposed to have been fixed in 10 but there seems to be a
reversion in 10.1.

The Microsoft coder looking after Word says " Yeah, this is a known issue
that Symantec are aware of. This was purportedly fixed in NAV 10.0, but has
reportedly begun to occur again with updates.

I have yet to be successful reproing this in house, but one thing that I do
know is that they may not need to turn off NAV completely, just the
auto-protect feature."

One of the other Beta List participants says:
" It's a bug on Symantec's part. Basically, you can't autoprotect any
directory that any Carbon application writes to. According to Symantec, it's
because Carbon applications aren't "native", but just old, munged OS 9 code.
The real reason is that they assume that all applications delete ala Cocoa,
which is really just an unlink, instead of the way Carbon applications do
it, which is a true delete."

Hope this helps

> Hi all,
>
[quoted text clipped - 17 lines]
>
> Regards, Terry

Signature

Please reply to the newsgroup to maintain the thread.  Please do not email
me unless I ask you to.

John McGhie <john@mcghie.name>
Microsoft MVP, Word and Word for Macintosh.  Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.