I have a network consisting of various types of Windows XP Pro machines connecting to a domain hosted on a Dell PowerEdge 2950 Windows 2008 Standard SP2 server. They are all connect to a gigabit Cat6 network. The server has two gigabit connections which are teamed (paired).
The server shows no hardware errors. The network itself seems fine. However, numerous users are randomly receiving the following errors when they log in or out, and their Outlook PST files are being corrupted:
"Windows was unable to save all the data for the file \\server\path\outlook\pf6DD.tmp. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save the file elsewhere."
This is seen during the "Saving your settings" portion of the logout process, and it basically means that their Outlook PST file is now corrupted and will have to be restored from a backup because repairing it means data will be lost.
Sometimes the following roaming profile error occurs:
"Windows cannot update your roaming profile. Possible causes of this error include network problems of insufficient security rights. If this problem persists, contact your network administrator."
When the PST file is corrupted, this message may appear:
"Cannot start Microsoft Office Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file ...\outlook.pst is not a personal files folder."
There are a few more errors, all pointing in the same directions - no where. Sometimes a roaming profile error or network connectivity error will occur and Outlook will become corrupted, and sometimes it won't. Most of the time on each workstation it just works normally. There is no correlation between the model or workstation, the SP level applied, or the version of Office (using 2003 and 2007).
I'm looking for any input at all here. The only thing I can think of is some kind of elusive network connectivity issue, but even that doesn't make sense because it works most of the time. Switches usually work or don't. If it's the server, it's strange because it doesn't really have any errors on it that indicate these sorts of issues.