Hi,
This is my problem:
I had a Windows NT Server SP6 which was migrated into a Windows 2000
Server SP3 This server act as a Primary Domain Controlor in mixed
mode (ie:there is also a NT server on the network) and is also a file
server

Now since we migrated the server, each time a client station ( under
Win2k Pro) try to save a office ( Office XP) document (Word,
excel)through the network on the server, we get the following error:

"Disk full or too many files opened"

The error does not appear everytime, and if you retry several times,
you finally succeed to save your file ( after 10~20 times at least).

Yet, there is plenty of free space available on the HDD of the server.
To resolve the problem,I've tried several things:

-I've disabled all systems quotas on the disk to be sure the quoats
wasn't exceeded.
-turn off the antivirus ( Mc Afee) to be sure it wasn't a problem of
locked files when there were scanned by the antivirus!
-Check If there were enough virtual memory for the system server
(abuot 3Go for services & applications)
-I've searched for tmp files (*.tmp or ~*.doc) to see if there were
not too numerous.
-The document saved on the server does not contain disrupted links or
math equation objets ( which seems to cause these problems sometimes)
-it is not a problem of ACL because even if you encouter saving
problems, you still can open and save the file after severals tries.

Presently, I don't now if the problem is caused by office XP or by the
file server, knowing that it was working perfectly before the
migration?

One another point, even opening a file with Word 97 and then saving it
on the network, we get the same error, so we can reproduice the same
error with Office 97 and office XP ( patched with SP2).

I was asking myself if the problem would not come from the server
which is a PDC and also a file server?
Wouldn't it be better to put a file server on anoter machine which is
not a PDC?

Any help would be welcome

I have found this article hope this helps

http://www.dessci.com/en/support/TSN/tsn64.htm

"Filpinpin" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Hi,
> This is my problem:
> I had a Windows NT Server SP6 which was migrated into a Windows 2000
> Server SP3 This server act as a Primary Domain Controlor in mixed
> mode (ie:there is also a NT server on the network) and is also a file
> server
>
> Now since we migrated the server, each time a client station ( under
> Win2k Pro) try to save a office ( Office XP) document (Word,
> excel)through the network on the server, we get the following error:
>
> "Disk full or too many files opened"
>
> The error does not appear everytime, and if you retry several times,
> you finally succeed to save your file ( after 10~20 times at least).
>
> Yet, there is plenty of free space available on the HDD of the server.
> To resolve the problem,I've tried several things:
>
> -I've disabled all systems quotas on the disk to be sure the quoats
> wasn't exceeded.
> -turn off the antivirus ( Mc Afee) to be sure it wasn't a problem of
> locked files when there were scanned by the antivirus!
> -Check If there were enough virtual memory for the system server
> (abuot 3Go for services & applications)
> -I've searched for tmp files (*.tmp or ~*.doc) to see if there were
> not too numerous.
> -The document saved on the server does not contain disrupted links or
> math equation objets ( which seems to cause these problems sometimes)
> -it is not a problem of ACL because even if you encouter saving
> problems, you still can open and save the file after severals tries.
>
> Presently, I don't now if the problem is caused by office XP or by the
> file server, knowing that it was working perfectly before the
> migration?
>
> One another point, even opening a file with Word 97 and then saving it
> on the network, we get the same error, so we can reproduice the same
> error with Office 97 and office XP ( patched with SP2).
>
> I was asking myself if the problem would not come from the server
> which is a PDC and also a file server?
> Wouldn't it be better to put a file server on anoter machine which is
> not a PDC?
>
> Any help would be welcome

This sounds like the SMB Signing bug that was afflicted on Windows 2000
Server by ServicePack 3. You need to disable SMB Signing and I recommend
that you seek information on this from an appropriate Windows Server
Newsgroup.

--
Terry Farrell - Word MVP
http://www.mvps.org/word/

"Filpinpin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
Hi,
This is my problem:
I had a Windows NT Server SP6 which was migrated into a Windows 2000
Server SP3 This server act as a Primary Domain Controlor in mixed
mode (ie:there is also a NT server on the network) and is also a file
server

Now since we migrated the server, each time a client station ( under
Win2k Pro) try to save a office ( Office XP) document (Word,
excel)through the network on the server, we get the following error:

"Disk full or too many files opened"

The error does not appear everytime, and if you retry several times,
you finally succeed to save your file ( after 10~20 times at least).

Yet, there is plenty of free space available on the HDD of the server.
To resolve the problem,I've tried several things:

-I've disabled all systems quotas on the disk to be sure the quoats
wasn't exceeded.
-turn off the antivirus ( Mc Afee) to be sure it wasn't a problem of
locked files when there were scanned by the antivirus!
-Check If there were enough virtual memory for the system server
(abuot 3Go for services & applications)
-I've searched for tmp files (*.tmp or ~*.doc) to see if there were
not too numerous.
-The document saved on the server does not contain disrupted links or
math equation objets ( which seems to cause these problems sometimes)
-it is not a problem of ACL because even if you encouter saving
problems, you still can open and save the file after severals tries.

Presently, I don't now if the problem is caused by office XP or by the
file server, knowing that it was working perfectly before the
migration?

One another point, even opening a file with Word 97 and then saving it
on the network, we get the same error, so we can reproduice the same
error with Office 97 and office XP ( patched with SP2).

I was asking myself if the problem would not come from the server
which is a PDC and also a file server?
Wouldn't it be better to put a file server on anoter machine which is
not a PDC?

Any help would be welcome

It could have been a problem of SMB signing, but it wasn't.
The problem comes from the vsp.sys file installed by BacckUp Exec
which create a conflit with Norton Antivirus.

The following article details all the probleme encourtered and know to
fix it!
For me it worked, and I have no more errors
If this can help anyone who dealed with the same problems as me,at the
end of the post, there are also the reference to other article of the
knowledge base which treats similar problems

============================================================================
=====================================
ErrMsg: "The save failed due to out of memory or disk space"
----------------------------------------------------------------------------
---
The information in this article applies to:

- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows XP 64-Bit Edition
- Microsoft Windows XP Professional
- Microsoft Windows NT Server 4.0 (Version: 4.0)
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Workstation 4.0 (Version: 4.0)
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Web Edition

----------------------------------------------------------------------------
---
The information in this article also applies to:

- Office 2000
- Office XP
- Microsoft Excel 2000
- Microsoft Excel 2002
- Microsoft FrontPage 2000
- Microsoft FrontPage 2002
- Microsoft PowerPoint 2000
- Microsoft PowerPoint 2002
- Microsoft Word 2000
- Microsoft Word 2002
- Microsoft Access 2000
- Microsoft Access 2002

The clients are Win2k, WinXP, Win98 and Win95.


----------------------------------------------------------------------------
---

SYMPTOMS
=========

- Outlook users cannot open PST folder on a share across the
network.

- Office applications users cannot save their documents on a
DFS
storage.

- Users who are modifying files (e.g. Excel documents, or Word
documents) on a network file server
are unable to save files or receive the error message
"Disk is Full" not enough resources.
even though there is enough free disk space on the network
drive.

"Disk full or out of memory"


- You see the following verbatim error messages for different
applications


- Excel .xls:
"Document not saved"
"The disk is full"


- Word .doc:
"The save failed due to out of memory or disk space
(drive:\path\filename)"
Click OK.
"Do you want to retry the save?"
Click YES. Try to save to same location.
"Disk is full or to too many files are open."

Note: You CAN save Rich Text Format (.RTF) files from Word to
the
mapped drive - just not .DOC files.


- PowerPoint .ppt:
"Read only file"
"There was an error accessing (filename)"


- Outlook:
"Cannot start the reminder service. Unable to show reminders.
An error occurred that prevented the file <drive
letter>:\Outlook\filename.pst from being saved.
Close and then re-start all mail-enabled applications."

In Outlook accessing a personal file
"Unable to expand the folder. An error occured that prevented
(file
name) to save.
Close and then restart all mail enabled application."


- MSpaint
"An unknown error occurred when accessing <drive
letter>:\folder\filename.bmp"
Note: You CAN save as jpg, tiff, gif. - only BMP fails in
MSPAINT


- Adobe PageMaker 7.0: "disk full" and/or "invalid parameter"


- Other applications may return:
"Access Denied" or "Document not saved".

"Disk full or not enough memory"

Message that the file is in use by someone else, but it is
not in
actuality.

- Sometimes there is no error and the file appears to save
correctly
- but, in actuality, it does not save.



Other symptoms:

- Event ID 2020 INVALID_PARAMETER in system eventlog

- After initiating a system shutdown or restart, the computer
does
not successfully complete shutdown but instead displays a
black screen with a blinking cursor (or no cursor) and does
not
continue past this screen.



CAUSE
======

- This issue may occur if a non-Microsoft application that is
installed on your computer uses an outdated
kernel-mode filter driver.

- File system filter driver interfering.

- Typically the errors described in the symptoms section occur
if
VSP.SYS is loaded in combination with antivirus filter driver, i.e.
Symantec Antivirus Corporate Edition 8.0.
SYMEVENT.SYS Symantec Event Library
NAVAP.SYS AutoProtect



RESOLUTION
===========
As of Oct 2003, this is now a known issues with Veritas'
Backup Exec
Advanced 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.


Remove VSP.SYS or uninstall Veritas remote agent, this removes
the
vsp.sys file.

Uninstall the Netbackup 4.5 client and re-install the 3.4.1
version
that does not ship vsp.sys.

Uninstall this software package and reinstall the remote agent
but
WITHOUT the Advanced Open File Option.

Install the "Advanced Open File Option" using the latest
version
from Veritas.

To resolve this issue, contact the manufacturer of the program
to
inquire about the availability of a filter driver update.
For more information about how to contact VERITAS, visit the
following VERITAS Web site:

http://support.veritas.com/

Microsoft provides third-party contact information to help you
find
technical support. This contact information may change without notice.
Microsoft does not guarantee the accuracy of this third-party contact
information.


WORKAROUND
==========

Note: 'Advanced Open File Option' is an optional component of
the
backup software which is not needed to do regular backups.

- Edit the registry to temporarily deactivate the filter
driver and
reboot the system.
Manually disable this service (Open File Option) by setting
the
registry value

HKLM\System\CurrentControlSet\Services\VSP\Start to 0x4.

Setting this key & rebooting will prevent the driver from
loading.

IMPORTANT: If the driver is disabled only, the operating
system will
likely halt
on the next reboot and display a STOP 0x7B
INACCESSIBLE_BOOT_DEVICE.
This is
because the VSP.SYS driver is referenced in the registry at
the
following locations:


HKLM\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE
2092F}\UpperFilters

(If running Windows 2000, the above registry key should be
edited in
REGEDT32.EXE since it is a multi-string binary value)



For additional information about how to temporarily deactivate
the
kernel-mode filter driver, click the following article number to view
the
article in the Microsoft Knowledge Base:

816071.KB.EN-US: How to Temporarily Deactivate the Kernel
Mode
Filter Driver



STATUS
=======

Microsoft has confirmed that this is a problem in the
Microsoft
products that are listed at the beginning of this article


MORE INFORMATION
=================

VSP.SYS comes with either Netbackup or Veritas Backup-Exec for
Windows 9.0 (Backup Exec Advanced Open File Option)

NOTE:
- Updating to the latest version of these applications may not
update the VSP.sys file.
- Uninstalling the VERITAS Software package may not remove the
filter driver VSP.sys
You can verify that this driver is removed by looking at the
output
of drivers.exe or pstat.exe


VSP.SYS is a filter driver that allows backup to suspend (and
cache)
file writes while a backup is in progress.

VSP.SYS is the "Volume Snapshot Provider Driver".


The VSP.SYS file is located in %systemroot%\SYSTEM32\DRIVERS

This file is installed on the system by the Veritas's remote
backup
agent.


Affected file versions are 1.2:0.0 and 1.0:0.0


VSP.SYS |VERITAS Software |Volume Snapshot
Provider
Driver

Module[ 22] [C:\WINNT\SYSTEM32\DRIVERS\VSP.SYS]
Company Name: VERITAS Software
File Description: Volume Snapshot Provider Driver
Product Version: (1.0:0.0)
File Version: (1.0:0.0)
File Size (bytes): 50176
File Date: Mo Nov 04 12:02:14 2002

Module[178] [C:\WINNT\SYSTEM32\DRIVERS\VSP.SYS]
Company Name: VERITAS Software
File Description: Volume Snapshot Provider Driver
Product Version: (1.2:0.0)
File Version: (1.2:0.0)
File Size (bytes): 50528
File Date: Thu Apr 03 15:16:06 2003





NetBackup
---------
Netbackup client version that is running without problems is
the
3.4.1ga.
The 3.4.1ga version client doesn't appear to install the
vsp.sys
driver.
Upgrading to the 4.5 feature pack 4 client may introduce the
problem.



Network Monitor
---------------
From a Network Monitor (Netmon) captures you can see errors
while
flushing the cache.

There is a SMB C_Flush_File sent from the client to the
server, that
happens at the end of a file being written.
This gets responded by the server with a
STATUS_INVALID_PARAMETER
error:

SMB: C Flush File
SMB: R flush file - NT error, System, Error, Code = (13)
STATUS_INVALID_PARAMETER

SMB: NT status code = 0xC000000D, Facility = System, Severity
=
Error, Code = (13) STATUS_INVALID_PARAMETER
SMB: NT Status Severity Code = Error
SMB: NT Status Customer Code = 0 (0x0)
SMB: NT Status Reserved Bit = 0 (0x0)
SMB: NT Status Facility = System
SMB: NT Status Code System Error = STATUS_INVALID_PARAMETER

The SMB_COM_FLUSH command ensures that all data and allocation
information for the corresponding file has been written to stable
storage.
The response is not sent until the write operations are complete.


Notes:
------
Typically the problem happens after several hours or several
days of
uptime of the file server.

You can save Wordpad or Notepad documents to the same network
share
without a problem.
The issue is happening to applications that use temporary
files
within the save process.
In general, Office applications do something like this:

1. Open the source file.
2. Open a temporary copy of the file.
3. Make changes to the temporary copy.
4. When we save the file, we flush all changes to the temp
file,
then replace the original source file with this temporary file.



REFERENCES
===========
822219.KB.EN-US You Experience Slow File Server Performance
and
Delays Occur When You
http://support.microsoft.com/?id=822219

816071.KB.EN-US How to Temporarily Deactivate the Kernel Mode
Filter
Driver
http://support.microsoft.com/?id=816071


Veritas Web Site Information:
-----------------------------
How to install and uninstall the Advanced Open File Option to
remote
Windows servers from the command prompt
http://seer.support.veritas.com/docs/253620.htm

Uninstall the Advanced Open File Option on a remote server
from the
Windows command prompt:
1. At the remote server, open a command prompt window.
2. Change directories to the Remote Agent install directory
using
the following path:
\Program Files\VERITAS\Backup Exec\RANT
3. Type setup.exe /AOFO: -s -u, and press ENTER.
Note: The -s parameter is used to run the operation in silent
mode,
without using the user interface. The -u parameter specifies an
uninstall
operation. The parameter -boot is used to automatically restart the
computer. If this is desired, then add the -boot parameter; if not,
make
sure to restart the computer manually to disable the Advanced Open
File
Option.
The Advanced Open File Option is uninstalled from the remote
server.
After the uninstall process is completed, restart the system to
disable the
Advanced Open File Option.



Found the following 3rd party File system Filter(s).
Additional
file
system filters may be present in PStat Module Name summary
section

---------------------------------------------------------------------
SYMEVENT.SYS Symantec Event Library
NAVAP.SYS AutoProtect
VSP.SYS Volume Snapshot Provider Driver


For additional information about third-party filter drivers,
click
the following article number to view the article in the Microsoft
Knowledge
Base:
253195.KB.EN-US: Information About Third-Party Windows NT and
Windows 2000 File-System Filter Drivers

--------------------------------------------------------------------------


Otherwise, I invite you to check those KB if you still have errors:

KB 814112 - Files on Network Shares Open Slowly or Read-Only or You
Receive an Error Message
KB 182934 - WD97 : Not Enough Memory or Disk Space Saving File Windows
NT
KB 210335 - WD2000: Error Message: "Not Enough Memory or Disk Space"
Saving File in Word 6.0/95
KB 211326 - WD2000:Error Messages When You Save File with Low Hard
Disk Space
KB 224041 - WD2000 :Error Message :The Disk Is Full or Too Many Files
Are Open
KB 224054 - WD2000: Error Message: There Is Not Enough Memory or Disk
Space to Complete the
Operation
KB 296264 - Configuring Opportunistic Locking in Windows
KB 324491 - XL2002: "The File May Have Been Changed..." Error When You
Save Workbook to Network
Server
KB 329170 - MS02-070: Flaw in SMB Signing May Permit Group Policy to
Be Modified
KB 810907 - Error Messages When You Open or Copy Network Files on
Windows XP SP1 Clients That
Require SMB Signing
KB 812937 - File Lock or Access Denied Error Message When You Save
Files Over the Network











"TF" <(E-Mail Removed)> wrote in message news:<e$(E-Mail Removed)>...
> This sounds like the SMB Signing bug that was afflicted on Windows 2000
> Server by ServicePack 3. You need to disable SMB Signing and I recommend
> that you seek information on this from an appropriate Windows Server
> Newsgroup.
>
> --
> Terry Farrell - Word MVP
> http://www.mvps.org/word/

Thanks for the feedback.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://www.mvps.org/word
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

"Filpinpin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> It could have been a problem of SMB signing, but it wasn't.
> The problem comes from the vsp.sys file installed by BacckUp Exec
> which create a conflit with Norton Antivirus.
>
> The following article details all the probleme encourtered and know to
> fix it!
> For me it worked, and I have no more errors
> If this can help anyone who dealed with the same problems as me,at the
> end of the post, there are also the reference to other article of the
> knowledge base which treats similar problems
>
>
============================================================================
> =====================================
> ErrMsg: "The save failed due to out of memory or disk space"
> --------------------------------------------------------------------------
--
> ---
> The information in this article applies to:
>
> - Microsoft Windows 2000 Advanced Server
> - Microsoft Windows 2000 Professional
> - Microsoft Windows 2000 Server
> - Microsoft Windows XP 64-Bit Edition
> - Microsoft Windows XP Professional
> - Microsoft Windows NT Server 4.0 (Version: 4.0)
> - Microsoft Windows NT Server 4.0 Terminal Server Edition
> - Microsoft Windows NT Workstation 4.0 (Version: 4.0)
> - Microsoft Windows Server 2003, 64-Bit Enterprise Edition
> - Microsoft Windows Server 2003, Enterprise Edition
> - Microsoft Windows Server 2003, Standard Edition
> - Microsoft Windows Server 2003, Web Edition
>
> --------------------------------------------------------------------------
--
> ---
> The information in this article also applies to:
>
> - Office 2000
> - Office XP
> - Microsoft Excel 2000
> - Microsoft Excel 2002
> - Microsoft FrontPage 2000
> - Microsoft FrontPage 2002
> - Microsoft PowerPoint 2000
> - Microsoft PowerPoint 2002
> - Microsoft Word 2000
> - Microsoft Word 2002
> - Microsoft Access 2000
> - Microsoft Access 2002
>
> The clients are Win2k, WinXP, Win98 and Win95.
>
>
> --------------------------------------------------------------------------
--
> ---
>
> SYMPTOMS
> =========
>
> - Outlook users cannot open PST folder on a share across the
> network.
>
> - Office applications users cannot save their documents on a
> DFS
> storage.
>
> - Users who are modifying files (e.g. Excel documents, or Word
> documents) on a network file server
> are unable to save files or receive the error message
> "Disk is Full" not enough resources.
> even though there is enough free disk space on the network
> drive.
>
> "Disk full or out of memory"
>
>
> - You see the following verbatim error messages for different
> applications
>
>
> - Excel .xls:
> "Document not saved"
> "The disk is full"
>
>
> - Word .doc:
> "The save failed due to out of memory or disk space
> (drive:\path\filename)"
> Click OK.
> "Do you want to retry the save?"
> Click YES. Try to save to same location.
> "Disk is full or to too many files are open."
>
> Note: You CAN save Rich Text Format (.RTF) files from Word to
> the
> mapped drive - just not .DOC files.
>
>
> - PowerPoint .ppt:
> "Read only file"
> "There was an error accessing (filename)"
>
>
> - Outlook:
> "Cannot start the reminder service. Unable to show reminders.
> An error occurred that prevented the file <drive
> letter>:\Outlook\filename.pst from being saved.
> Close and then re-start all mail-enabled applications."
>
> In Outlook accessing a personal file
> "Unable to expand the folder. An error occured that prevented
> (file
> name) to save.
> Close and then restart all mail enabled application."
>
>
> - MSpaint
> "An unknown error occurred when accessing <drive
> letter>:\folder\filename.bmp"
> Note: You CAN save as jpg, tiff, gif. - only BMP fails in
> MSPAINT
>
>
> - Adobe PageMaker 7.0: "disk full" and/or "invalid parameter"
>
>
> - Other applications may return:
> "Access Denied" or "Document not saved".
>
> "Disk full or not enough memory"
>
> Message that the file is in use by someone else, but it is
> not in
> actuality.
>
> - Sometimes there is no error and the file appears to save
> correctly
> - but, in actuality, it does not save.
>
>
>
> Other symptoms:
>
> - Event ID 2020 INVALID_PARAMETER in system eventlog
>
> - After initiating a system shutdown or restart, the computer
> does
> not successfully complete shutdown but instead displays a
> black screen with a blinking cursor (or no cursor) and does
> not
> continue past this screen.
>
>
>
> CAUSE
> ======
>
> - This issue may occur if a non-Microsoft application that is
> installed on your computer uses an outdated
> kernel-mode filter driver.
>
> - File system filter driver interfering.
>
> - Typically the errors described in the symptoms section occur
> if
> VSP.SYS is loaded in combination with antivirus filter driver, i.e.
> Symantec Antivirus Corporate Edition 8.0.
> SYMEVENT.SYS Symantec Event Library
> NAVAP.SYS AutoProtect
>
>
>
> RESOLUTION
> ===========
> As of Oct 2003, this is now a known issues with Veritas'
> Backup Exec
> Advanced 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.
>
>
> Remove VSP.SYS or uninstall Veritas remote agent, this removes
> the
> vsp.sys file.
>
> Uninstall the Netbackup 4.5 client and re-install the 3.4.1
> version
> that does not ship vsp.sys.
>
> Uninstall this software package and reinstall the remote agent
> but
> WITHOUT the Advanced Open File Option.
>
> Install the "Advanced Open File Option" using the latest
> version
> from Veritas.
>
> To resolve this issue, contact the manufacturer of the program
> to
> inquire about the availability of a filter driver update.
> For more information about how to contact VERITAS, visit the
> following VERITAS Web site:
>
> http://support.veritas.com/
>
> Microsoft provides third-party contact information to help you
> find
> technical support. This contact information may change without notice.
> Microsoft does not guarantee the accuracy of this third-party contact
> information.
>
>
> WORKAROUND
> ==========
>
> Note: 'Advanced Open File Option' is an optional component of
> the
> backup software which is not needed to do regular backups.
>
> - Edit the registry to temporarily deactivate the filter
> driver and
> reboot the system.
> Manually disable this service (Open File Option) by setting
> the
> registry value
>
> HKLM\System\CurrentControlSet\Services\VSP\Start to 0x4.
>
> Setting this key & rebooting will prevent the driver from
> loading.
>
> IMPORTANT: If the driver is disabled only, the operating
> system will
> likely halt
> on the next reboot and display a STOP 0x7B
> INACCESSIBLE_BOOT_DEVICE.
> This is
> because the VSP.SYS driver is referenced in the registry at
> the
> following locations:
>
>
>
HKLM\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE
> 2092F}\UpperFilters
>
> (If running Windows 2000, the above registry key should be
> edited in
> REGEDT32.EXE since it is a multi-string binary value)
>
>
>
> For additional information about how to temporarily deactivate
> the
> kernel-mode filter driver, click the following article number to view
> the
> article in the Microsoft Knowledge Base:
>
> 816071.KB.EN-US: How to Temporarily Deactivate the Kernel
> Mode
> Filter Driver
>
>
>
> STATUS
> =======
>
> Microsoft has confirmed that this is a problem in the
> Microsoft
> products that are listed at the beginning of this article
>
>
> MORE INFORMATION
> =================
>
> VSP.SYS comes with either Netbackup or Veritas Backup-Exec for
> Windows 9.0 (Backup Exec Advanced Open File Option)
>
> NOTE:
> - Updating to the latest version of these applications may not
> update the VSP.sys file.
> - Uninstalling the VERITAS Software package may not remove the
> filter driver VSP.sys
> You can verify that this driver is removed by looking at the
> output
> of drivers.exe or pstat.exe
>
>
> VSP.SYS is a filter driver that allows backup to suspend (and
> cache)
> file writes while a backup is in progress.
>
> VSP.SYS is the "Volume Snapshot Provider Driver".
>
>
> The VSP.SYS file is located in %systemroot%\SYSTEM32\DRIVERS
>
> This file is installed on the system by the Veritas's remote
> backup
> agent.
>
>
> Affected file versions are 1.2:0.0 and 1.0:0.0
>
>
> VSP.SYS |VERITAS Software |Volume Snapshot
> Provider
> Driver
>
> Module[ 22] [C:\WINNT\SYSTEM32\DRIVERS\VSP.SYS]
> Company Name: VERITAS Software
> File Description: Volume Snapshot Provider Driver
> Product Version: (1.0:0.0)
> File Version: (1.0:0.0)
> File Size (bytes): 50176
> File Date: Mo Nov 04 12:02:14 2002
>
> Module[178] [C:\WINNT\SYSTEM32\DRIVERS\VSP.SYS]
> Company Name: VERITAS Software
> File Description: Volume Snapshot Provider Driver
> Product Version: (1.2:0.0)
> File Version: (1.2:0.0)
> File Size (bytes): 50528
> File Date: Thu Apr 03 15:16:06 2003
>
>
>
>
>
> NetBackup
> ---------
> Netbackup client version that is running without problems is
> the
> 3.4.1ga.
> The 3.4.1ga version client doesn't appear to install the
> vsp.sys
> driver.
> Upgrading to the 4.5 feature pack 4 client may introduce the
> problem.
>
>
>
> Network Monitor
> ---------------
> From a Network Monitor (Netmon) captures you can see errors
> while
> flushing the cache.
>
> There is a SMB C_Flush_File sent from the client to the
> server, that
> happens at the end of a file being written.
> This gets responded by the server with a
> STATUS_INVALID_PARAMETER
> error:
>
> SMB: C Flush File
> SMB: R flush file - NT error, System, Error, Code = (13)
> STATUS_INVALID_PARAMETER
>
> SMB: NT status code = 0xC000000D, Facility = System, Severity
> =
> Error, Code = (13) STATUS_INVALID_PARAMETER
> SMB: NT Status Severity Code = Error
> SMB: NT Status Customer Code = 0 (0x0)
> SMB: NT Status Reserved Bit = 0 (0x0)
> SMB: NT Status Facility = System
> SMB: NT Status Code System Error = STATUS_INVALID_PARAMETER
>
> The SMB_COM_FLUSH command ensures that all data and allocation
> information for the corresponding file has been written to stable
> storage.
> The response is not sent until the write operations are complete.
>
>
> Notes:
> ------
> Typically the problem happens after several hours or several
> days of
> uptime of the file server.
>
> You can save Wordpad or Notepad documents to the same network
> share
> without a problem.
> The issue is happening to applications that use temporary
> files
> within the save process.
> In general, Office applications do something like this:
>
> 1. Open the source file.
> 2. Open a temporary copy of the file.
> 3. Make changes to the temporary copy.
> 4. When we save the file, we flush all changes to the temp
> file,
> then replace the original source file with this temporary file.
>
>
>
> REFERENCES
> ===========
> 822219.KB.EN-US You Experience Slow File Server Performance
> and
> Delays Occur When You
> http://support.microsoft.com/?id=822219
>
> 816071.KB.EN-US How to Temporarily Deactivate the Kernel Mode
> Filter
> Driver
> http://support.microsoft.com/?id=816071
>
>
> Veritas Web Site Information:
> -----------------------------
> How to install and uninstall the Advanced Open File Option to
> remote
> Windows servers from the command prompt
> http://seer.support.veritas.com/docs/253620.htm
>
> Uninstall the Advanced Open File Option on a remote server
> from the
> Windows command prompt:
> 1. At the remote server, open a command prompt window.
> 2. Change directories to the Remote Agent install directory
> using
> the following path:
> \Program Files\VERITAS\Backup Exec\RANT
> 3. Type setup.exe /AOFO: -s -u, and press ENTER.
> Note: The -s parameter is used to run the operation in silent
> mode,
> without using the user interface. The -u parameter specifies an
> uninstall
> operation. The parameter -boot is used to automatically restart the
> computer. If this is desired, then add the -boot parameter; if not,
> make
> sure to restart the computer manually to disable the Advanced Open
> File
> Option.
> The Advanced Open File Option is uninstalled from the remote
> server.
> After the uninstall process is completed, restart the system to
> disable the
> Advanced Open File Option.
>
>
>
> Found the following 3rd party File system Filter(s).
> Additional
> file
> system filters may be present in PStat Module Name summary
> section
>
> ---------------------------------------------------------------------
> SYMEVENT.SYS Symantec Event Library
> NAVAP.SYS AutoProtect
> VSP.SYS Volume Snapshot Provider Driver
>
>
> For additional information about third-party filter drivers,
> click
> the following article number to view the article in the Microsoft
> Knowledge
> Base:
> 253195.KB.EN-US: Information About Third-Party Windows NT and
> Windows 2000 File-System Filter Drivers
>
> --------------------------------------------------------------------------
>
>
> Otherwise, I invite you to check those KB if you still have errors:
>
> KB 814112 - Files on Network Shares Open Slowly or Read-Only or You
> Receive an Error Message
> KB 182934 - WD97 : Not Enough Memory or Disk Space Saving File Windows
> NT
> KB 210335 - WD2000: Error Message: "Not Enough Memory or Disk Space"
> Saving File in Word 6.0/95
> KB 211326 - WD2000:Error Messages When You Save File with Low Hard
> Disk Space
> KB 224041 - WD2000 :Error Message :The Disk Is Full or Too Many Files
> Are Open
> KB 224054 - WD2000: Error Message: There Is Not Enough Memory or Disk
> Space to Complete the
> Operation
> KB 296264 - Configuring Opportunistic Locking in Windows
> KB 324491 - XL2002: "The File May Have Been Changed..." Error When You
> Save Workbook to Network
> Server
> KB 329170 - MS02-070: Flaw in SMB Signing May Permit Group Policy to
> Be Modified
> KB 810907 - Error Messages When You Open or Copy Network Files on
> Windows XP SP1 Clients That
> Require SMB Signing
> KB 812937 - File Lock or Access Denied Error Message When You Save
> Files Over the Network
>
>
>
>
>
>
>
>
>
>
>
> "TF" <(E-Mail Removed)> wrote in message
news:<e$(E-Mail Removed)>...
> > This sounds like the SMB Signing bug that was afflicted on Windows 2000
> > Server by ServicePack 3. You need to disable SMB Signing and I recommend
> > that you seek information on this from an appropriate Windows Server
> > Newsgroup.
> >
> > --
> > Terry Farrell - Word MVP
> > http://www.mvps.org/word/

Thanks

This really helped us out

Issue occurs on shares only. Subst'ed drives and local drives cause no problem
Server restart always helped shortl