Outlook 2003, PST files, and delayed write error

[barretech]

HI. I have a server 2003 R2 standalone DC with SP1 that we installed
updates onto last night (about 25 updates). Now it seems to have some
kind of problem with serving files. Outlook PST files.

The clients have Outlook 2003 with PST files ranging from 300MB to
2.3GB. Before the updates they seemed to be fine. Now we are seeing
"delayed write" errors and Outlook generally is unhappy. Outlook is
obviously asking for more than a simple file-copy does.

Can anyone suggest why file copies might work, but Outlook is still
not happy ? I don't know what Outlook is missing but it doesn't work.

Thinking that maybe the probl was caused by the switch, I tried a new
one. Same problem. Thought maybe it was user-related, so I tried a new
profile of a new user. Same problem. We try to File > Open >Outlook
data file, point it at the PST file on the server, and Outlook "checks
for errors" . Eventually the network activity halts, the computer sits
for a few minutes then fails.

I tried a new NIC in the server (being sure to add it to the existing
one) and it didn't help. Same results.

Of course we can copy the files from the server to the C: drives.
1.6GB copies in about 4 minutes. And Outlook is able to open the
copies of the files from local C: drive. This is my only workaround
for now.

I have already gone into the Windows folder and one by one in proper
order used "spuninst.exe" to remove each update. Didn't reboot between
the uninstalls. Maybe I should have.

I am getting ready to restore the system state from the time before
the updates were installed. I have posted a similar post in the
windows server general group and asked about using my USB hard drive
(actually two) with system state backups. I sure hope USB is supported
during system state restores.

Please , any Outlook insight is appreciated regarding the difference
between Outlook opening PST files (which always fails), and simple
file copies (which always work). Thank you in advance.!!

 

[dlw]

PST files on network shares are not supported and not recommended.

http://support.microsoft.com/kb/297019

 

[barretech]

Thanks. I wish I could say this wasn't the only customer of mine out
of probably 30 who have a problem, and only after the updates were
installed.

The PST files range in size all the way up to 3GB in some cases.

Another example of an organization who bucked the rules was this: up
til just this past March a nationwide customer of mine, an
organization of 3000 some PC's, relied on PST files stored on Linux
servers (not by my choice, their IT department always was able to
school me as much as I could help them, but they used Outlook 2000 in
IMO mode. So the only limitation was the 2GB limit). I am happy then
that my server installs must have all been better than perfect since
this is the first time and first and only place I have ever
experienced a problem with keeping PST files on a server.

But yes, thanks for links and the reminder!!

I just hate to tell a customer "well, yeah, I know it was working
perfectly before Monday and now it's busted. But it never should have
worked to begin with. What? You heard about how none of my other
customers have the problem? Well, maybe it's related to AIG or the
bailout. Just wait. They will be hurting soon too......" <g>

I'll figure it out and will let everyone know what broke it or what
fixed it. Thanks again for the reminder.