Delayed Write Failed - Mup

{Delayed Write Failed} Windows was unable to save all the data from the file \\ServerName\Folder Name\File.pst;the data has been lost. The error was returned by the server on which the file exists. Please try to save the file elsewhere

I am seeing this error a lot on windows server 2008 R2 - running Xenapp 6.0. Users are not able to access their Outlook PST’s when opening Outlook.  I have another Citrix environment that is Citrix Presentation 4.0 and users are not experiencing this problem.  They experience this problem when I moved them from Citrix 4.0 to Citrix XEN App6.  The Citrix 4.0 is running Windows 2003 Server with Office 2003.  The Citrix XENApp6 is running Windows Server 2008 R2 Enterprise with Office 2007.  When their PST becomes corrupt, I have to repair them but it’s a temporary fix until they become corrupt again.  I do know Microsoft does not support PST’s before you guys say anything but the problem does not exist unless I moved users to Citrix XEN App6.  I have seen someone post the same problem back in July of this year but you guys stopped responding to their POST.  I was told by the Exchange Expert Rep to open a case for some help.
Event-140.docx
idgaminAsked:
Who is Participating?
 
idgaminAuthor Commented:
I am using XenApp6.  I have the latest Rullup.  I am using Rollup XA600W2K8R2X64R01.
0
 
idgaminAuthor Commented:
Will someone be able to help me today?
0
 
David Johnson, CD, MVPOwnerCommented:
in provisioning setup increase the size of the swapfile.. error 140 is normally a hardware error (drive error) but I've seen reports of people increasing their swapfile to reflect the actual server memory has helped with this issue.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
MidnightOneCommented:
The use of PSTs across a network connection, i.e. not local to the Outlook application, is not supported by Microsoft.

My experience with it is there's only two types of PSTs: Those that are corrupt, and those that will be.
0
 
idgaminAuthor Commented:
Please give me a better answer than that.  I did not have any problems until I moved to the new Citrix Environment.  I do not have any problems in the Citrix 4.0 Presentation Environment but the problem does exist in the Citrix XenApp 6.0 environment.  The only difference is I am using Windows 2008 and Outlook 2007 instead of Windows Server 2003 and Outlook 2003 and different versions of Citrix.  I recently saw someone posted the same problem back in July but no one from Exchange Expert was able to help them from what I could tell.
0
 
David Johnson, CD, MVPOwnerCommented:
If you look on the Citrix Xenapp site, you're not alone..

If the hard drive is NOT bad (normal cause of event 140), then it is a contention issue within XenApp itself.

http://forums.citrix.com/thread.jspa?threadID=279877&tstart=165

Disable Delayed Write Caching on Hard Drive
To turn off Enable write caching on the disk, follow these steps:
Click Start, and then click My Computer.
Right-click the hard disk, and then click Properties.
Click the Hardware tab.
Click to select the hard disk, and then click Properties.
Click the Policies tab.
Click to clear the Enable write caching on the disk check box, and then click OK.
Click OK to close the Local Disk (C:) Properties dialog box.
Repeat steps 3 through 5 for each hard disk that is installed in your computer.
0
 
idgaminAuthor Commented:
Yep, I find this article also but my servers do not support this feature.  I have tried this already.
0
 
idgaminAuthor Commented:
Sorry about that, but this option is off by default.  I have verified it on my servers.
0
 
David Johnson, CD, MVPOwnerCommented:
have you added all of the rollups? I'm not sure whether or not XenApp 7 addresses this issue.
0
 
idgaminAuthor Commented:
http://blogs.citrix.com/2010/10/21/smb-tuning-for-xenapp-and-file-servers-on-windows-server-2008/

http://support.citrix.com/servlet/KbServlet/download/29413-102-681796/XA%20-%20Windows%202008%20R2%20Optimization%20Guide.pdf


Has anyone tried the above changes to 2008R2? We found the following information related to SMB and SMB2 changes from 2003 server and 2008R2.  Could this cause the Delayed Write Failed we are seeing in the system logs?  Has anyone actually tried these settings or implemented the NIC registry settings mentioned in the Citrix 2008R2 best practices PDF?   These changes were not implemented in our 4.5 environment.   Apparently Microsoft has made changes to SMB.  This may be our problem and I would like to hear your thoughts?
0
 
sparabCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
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.

All Courses

From novice to tech pro — start learning today.