Link to home
Start Free TrialLog in
Avatar of e_sandrs
e_sandrsFlag for United States of America

asked on

Disk Full Error on Win2k Server Mapped Drive from Office Apps.

Ok, this one is weird, and I'll put it here for now since I *think* it's a problem on the server, not with the apps - but what do I know?  Maybe this should be in Applications...

As of last Thursday, no one on our network (including the Administrator account) can save Office files from most Office applications to our mapped, Win2k Adv. Server, network drive - you cannot save a Word document from Word to our "U:" drive.  The error from Word is precisely "The save failed due to out of memory or disk space".  The errors from other Office applications are similar.

The network drive is mapped via the Net Use command in a logon script.  I have tried manually mapping the drive from Windows XP and Windows 98 and the problem persists.  The issue is present when saving from Office 97, 2000, XP, and 2003 Beta (not every combination of Windows/Office tested, FYI.  Mostly WinXP with Office 2000 SP3).  Word, Excel, PowerPoint, and Access are all effected.  Frontpage and Publisher are not - I can save from both those applications.

The server is a Windows 2000 Advanced Server w/ SP3 and all updates except SP4 (which is in testing to be applied later this month).  The machine is operating as a Backup Domain Controller and running Symantec Antivirus Corporate Edition 8.0.  We've tried disabling Real Time File Scanning, wtih no effect.  There is 168 GB free on the drive mapped.

What else can we do?  We CAN save files from numerous non-Office applications to the drive - including Windows Explorer (so we can save to another resource and move it to the mapped drive as a temporary kludge), Notepad/Wordpad, several Macromedia programs, etc.  It seems to only be effecting most of Office apps.  Also, we CAN save Rich Text Format (.RTF) files from Word to the mapped drive - just not .DOC files.  :-\

IMPORTANT FACT (probably):  We've been playing with activating a 3rd party quota enforcement tool - QuotaAdvisor v.4.1.462 (fully updated) originally by Wquinn, sold a couple of times, now owned by Veritas.  Our problem started very close to when a test quota was either enforced and then removed on a subfolder of the mapped drive with this issue.  We've tried removing all quotas applied by the tool (and the Quotas in W2k), stopping the tools Services, and rebooting the server - but the problem persists.  Since the problem continues with the tool all but uninstalled, we think it's not the current cause - although it may have "nudged" some Windows setting somewhere that it didn't put back (just as a thought).  Veritas does not list any issue with this software.

We've seem some reference to people having this problem elsewhere, but the only answer we've seen is "and then it went away".  This is probably enough info for the starting message - anything I've missed I'll post upon request.  Thanks for your attention!

Eric Sanders
-Just some guy on a board.
SOLUTION
Avatar of zefiro
zefiro

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Bartender_1
Bartender_1
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of e_sandrs

ASKER

zefiro:  
Unfortunately, the Q329170 patch is already applied to the servers and workstations, so that's not it.  

I'm confused by your next recommendation - I'm not seeing a %systemroot%\test directory to clear - do you mean Temp?

I also don't know where to get to the "Tools, Options, File Locations" to set Full UNC paths - I could try saving by browsing via the full path, but ...  Anyway if you could clarify I'll try it.
_____________________________________________
Bartender_1:
Sorry, Office is up to date on the systems I'm testing with.  Some client machines don't have Office 2k Sp3 yet, but mine do.

Sadly, I did try setting Quotas in Win 2k on the server, tried saving with the quota in place, then tried removing the quota and saving again.  All nothing.  :(
______________________________________________
Tatw:
We're hesitant to install any part of Office onto our servers - it just means we have to patch and maintain them!  Depending how desparate we get, we will probably come to that test.
______________________________________________

Thanks to all for your suggestions so far - I'll watch for more ideas and post any progress we see...

-ES
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
FYI - a follow up, finally.  We re-ran SP3 on the the Win2k server and the problem went away.  Along the way, we did see a Microsoft document that described the "can't save DOC but can save RTF" problem (of course, I don't have it in front of me right now) that pointed to a problem with a specific DLL file.  The SP3 run must have restored the problem DLL (at a guess).  If someone wants the specific MS writeup on the DOC save issue, I could probably still find it for them.

Zefiro seemed to be on the closest track with his answers and followup, so I'll accept from him, but spread out some points to the field for your efforts in looking at my question - Thanks!
Avatar of bullitt78
bullitt78

Many Thanks E_Sandrs and Zefiro,

At my company we to had the same issue. Ours happened when one of our main file servers had Norton AntiVirus Corp 8.0 pushed to it in the midst of the MSBlaster and SOBIG.F worms running around. It seems that NAV Corp 8.0 caused a problem with the SP3 on our ADV 2000 Server. We had the same issue of not being  allowed to save .XLS and .DOC files to it. Couldn't find anything on it at Microsoft. Big waste of time. After reading this article we decided to bring it down and repatch with SP3. Worked like a charm.

Thanks Again.
Glad it was here to help!  EE is a very nice site for those really unusual/undocumented problems.

-ES
You guys rock, we had the same problem I was going crazy trying to figure it out.  People couldn't save excel and word files about %30 of the time they would click save.

I reinstalled SP3 and it fixed our problem.. I also posted something on Symantec's site to let them know.
**** This is now a known issues with Veritas' Open File Option ****

Call Veritas for a fix or wait for the official patch from Veritas.  The offending file is %systemroot%\system32\drivers\vsp.sys.  Below is my correspondence with their support person.

***Removed by CS***
Thanks Brian!  It's always nice to have a fix rather than a "this works for now" band-aid solution.

-ES
Until my posts or this thread gets deleted please take note.

I have been contacted by Veritas Software that this patch was for testing purposes only and is not openly distributable.  A fix is in the works but there currently is no release date set.  Until the update is posted on their website please remove the AOFO from your installation if you are experiencing this problem.

I have asked for my comments to be deleted.

Sorry for any inconveinences I have caused due to my post.
I only thought the service pack had fixed my problem, Brian was right about Veritas.  I didn't have the open file option installed, but I did have the Remote Agent installed, and that file and problem did exist on my server.  I contact Veritas and they wouldn't give me the file, so I uninstall the remote agent and haven't had the problem in weeks.
Brian was really very helpful, same problem here with Storage Central 5 and win2k adv server, EE is great, I looked for the OFO by Veritas, removed it and everything worked like a charm.
It really seems that the OFO conflicts with other software which installs file system filters like Storage Central SRM and Symantec AV do.
Thanks you all.
I've been looking for a solution for this for 2 weeks. Ide done service packs deleted tmp files done everything I could think of. I even called veritas once but was on hold so long I gave up. this board is awsome
and Thanks Brian
For as much time this site has helped save my rear, I am only glad to return the favor.

Brian Kronberg
I have posted this issue at Veritas's support site but I am still waiting for an answer is there someone who can help me out with the location of an update or patch on the internet?

Thanks,

Evert Smit
This might be a dead thread but I am having the exact same problem with Word 2003!!! All the updates are installed so that's out. Any suggestions for 2003?

I'm using xp pro and saving to an xp pro file server which is connected to the network by a switch.. I can save to a wide open shared folder, but it seems any thing with restrictions, but permission for this computer, give me the error after stalling for 20-40 seconds. I'm baffled.
2003 server shares are not shared with full permissions.  Check the permissions on the share to make sure they are set to write for some group which you are a part of ("domain users" or "authenticated users" are good, just not the "everyone" group).

Next check the NTFS permissions for the folder.