D
DavidK
Hello All,
I have recently installed a number of computers with Vista Business
and Office 2007. I have installed all available updates and installed
Service Pack 1 to Office 2007. I have disable the Offline Files and
Webclient services. When users try to save an Excel 2007 (.doc) file
to a mapped network drive it says 'Document not saved'. There is
plenty of space on the server, the users have full control over the
share, and I have even temporarily disabled our Sophos Anti-Virus
protection to eliminate this possibility. Nothing works! If the user
tries to manually move it then it will save but not Save As... Also,
the same users can save the same documents using Excel XP and Windows
XP Professional SP2 with no issues.
I have been researching this particular issue for a few days now and
cannot seem to find a fix anywhere despite looking in lots of forums
and searching on the Microsoft support website. I wish Microsoft would
make reference to it somewhere as it's obviously a widespread issue.
Has anyone got the faintest idea how to resolve this before I log a
call with Microsoft Support?
Thanks.
David
I have recently installed a number of computers with Vista Business
and Office 2007. I have installed all available updates and installed
Service Pack 1 to Office 2007. I have disable the Offline Files and
Webclient services. When users try to save an Excel 2007 (.doc) file
to a mapped network drive it says 'Document not saved'. There is
plenty of space on the server, the users have full control over the
share, and I have even temporarily disabled our Sophos Anti-Virus
protection to eliminate this possibility. Nothing works! If the user
tries to manually move it then it will save but not Save As... Also,
the same users can save the same documents using Excel XP and Windows
XP Professional SP2 with no issues.
I have been researching this particular issue for a few days now and
cannot seem to find a fix anywhere despite looking in lots of forums
and searching on the Microsoft support website. I wish Microsoft would
make reference to it somewhere as it's obviously a widespread issue.
Has anyone got the faintest idea how to resolve this before I log a
call with Microsoft Support?
Thanks.
David