delayed write failed

hello experts
i have some errors in terminal servers event logs

Log Name: System
Source: Mup
Event id: 139
{Delayed Write Failed} Windows was unable to save all the data for the file \\192.168.32.25\HOME_DIRECTORY$\DATA\Emma Pap .. a\Roaming\Chrome\Profile\Default\Visited Links; the data has been lost.  This error may be caused by network connectivity issues. Please try to save this file elsewhere.  

Log Name: System
Source: Mup
Event id: 140
{Delayed Write Failed} Windows was unable to save all the data for the file \\192.168.32.25\HOME_DIRECTORY$\DATA\Karine N .. MERIABANK\outlook archive karine\archive11.pst; the data has been lost.  This error was returned by the server on which the file exists. Please try to save this file elsewhere.  

we update network drivers and, disable  large sent offload v2 (IPv4) TCP/UDP check sum offload
it is a virtual server windows 2008R2 on hyper-v:
files stored on file server, and requested files are very large. (it is about 20Gb)

please help
ameriaadminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
Can you add timestamps to your cut-down log messages?
0
Nick67Commented:
I do understand that this is a terminal server; HOWEVER:
The storage of PST files in a UNC path is generally frowned upon by MS, and is not a supported configuration.
http://support.microsoft.com/kb/297019.
If you are running Exchange, MS suggests using cached mode
If you are not running Exchange, it is suggested that you use PST files saved on a local drive (of the terminal server) and then copied to a desired backup location when Outlook is closed.

However, .pst files are not intended as an enterprise network solution. Although it is possible to specify a network directory or a Universal Naming Convention (UNC) path as a storage location for a .pst file, network usage is not meant to be a long-term, continuous-use method of storing messages in an enterprise environment.

Are you encountering this problem with ANY file OTHER than a .pst file?
Then perhaps you may be having imminent hard drive failure issues.
If it is only with a .pst file, you will soon be encountering corrupt pst files -- if you haven't been already.
Read the kb article and configure your pst storage locations accordingly.
If Outlook takes longer to close than Windows decides to wait when killing/logging off a user, bad things happen.
iTunes and Outlook 2010 were a killer combination and the iTunes add-in constantly caused .pst corruption upon reboot -- until I killed it.  In a TS environment, the server is unlikely to be gentle in waiting for Outlook to close.  .pst files on a network share -- and in this case it looks like in a roaming profile -- are heartache waiting to happen.
0
Nick67Commented:
You do not say what version of Outlook is involved.
pre-Outlook 2010 versions have an upper limit of a 20 GB pst file
http://support.microsoft.com/kb/982577
This may be compounding your problems
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

ameriaadminAuthor Commented:
The version of Outlook is 2010.
There were no hard drive failures - the share located on v-storage.
Yes, *.pst files are corrupting often. We haven't installed iTunes.
0
gheistCommented:
v-storage humm. You need to set extreme scsi timeouts for that, it must be documented somewhere, e.g. vmware tools would set SCSI command timeout to 180s...
0
Nick67Commented:
The storage of PST files in a UNC path is generally frowned upon by MS, and is not a supported configuration.
http://support.microsoft.com/kb/297019.

Since you are using Outlook 2010, the 20 GB size of the file itself is not a problem, however, the fact that it is stored on a UNC path is, and will continue to be a problem, and an unfixable problem in that location.  That file MUST be stored on a local drive of the terminal server, and not on a UNC path to resolve the problem.
Are you encountering this problem with ANY file OTHER than a .pst file?
0
ameriaadminAuthor Commented:
we have removed pst files from network device.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ameriaadminAuthor Commented:
thank you all
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.