topic Re: Unable to read or save large files on File server in Operating System - Microsoft

Unable to read or save large files on File server

IMraN1 — Tue, 03 Mar 2009 15:25:16 GMT

Hello All,

Any help is much appreciated please.

Following errors are seen by users accessing files from a File server

Errors:

1. Windows was unable to save all the data for the file
The data has been lost. This error may be caused by a failure of your computer hardware or network connection. please try to save this file elsewhere.

2. Cannot copy: Not enough server storage is available to process this command.

3. Error: AN I/O error has occured on file

The files types are excel, ppt and dat format

Errors are noticed for files with size more than 50 Mb mostly

File server details:
VM slice with Windows 2003 standard
4 GB RAM
There is lots of hard disk space connected to SAN MSA 1500

VM server hosted on Physical HP DL 585 G2 with 8 CPU, 48 GB RAM - This host server has 8 other VM slices - but not used much

Have checked perfmon logs and spotlight monitoring - There were memory warnings for page file size.

Increased the pagefile size on VM server as per standards 1.5 times of RAM but still the problem is seen.

No logs on server when the error occurs.
Users face this problem INTERMITTENTLY.

Thanks.

Re: Unable to read or save large files on File server

Jon Finley — Fri, 06 Mar 2009 21:50:39 GMT

MS thinks it's due to a Lanman setting.
http://support.microsoft.com/kb/177078

Otherwise, it "may" actually turn out to be a locking contention issue with the Server's or client's anti-virus package.

Jon

Re: Unable to read or save large files on File server

IMraN1 — Sat, 07 Mar 2009 15:08:48 GMT

Thank you,

Server protect 5.58 is the version of Trend installed -
So, could not add the said parameter in the registry and check

Could this be related with registry settings of VM or possibility of increasing the number of threads being accessed please..?

Re: Unable to read or save large files on File server

Jon Finley — Fri, 13 Mar 2009 23:08:28 GMT

It's possible that it's a thread issue, but based on the file names, it sounds more related to your Virus Scanning program. As a test, have your virus scanner OMIT the file share folder. If the error goes away, you've found the culprit.

Jon