Loading…
5
I finally fixed a client's Outlook loop after 6 hours and the culprit was one 3 year old PST file on a network share
Spent most of Tuesday chasing a profile corruption issue in their Portland office when the whole thing came down to a 2GB PST file sitting on a shared drive that Outlook kept trying to mount over a slow VPN, so has anyone else run into that combo where the fix was just moving the file local?
1 comments
Log in to join the discussion
Log In1 Comment
olivia_carr719d ago
I once spent a whole afternoon blaming the user for a "broken" Outlook, then realized the PST was on a mapped drive that kept dropping every 10 minutes. Moving it local fixed it in about two seconds, which made me feel real smart after three hours of uninstalling and reinstalling Office like a genius. Network shares and PST files just do not mix, so moving it local is usually the first thing to try instead of the last.
4