Oh ye gods! I hate PFM. It's working.
I suspect that one of the command line options I used simply took a while to work, but I don't know which one, or the root cause. The one thing I can say for sure is that the mailbox was not hidden - I didn't specifically search for that, but I distinctly remember that setting being unchecked when I was looking through the GUI for clues. Thanks to Michael, DR and Adam (in reverse order of reply) for the suggestions. Kurt On Mon, Aug 10, 2015 at 4:03 PM, Kurt Buff <[email protected]> wrote: > Both Exchange and Outlook are patched - though Oulook is a month behind. > > I have one user who cannot open Outlook. Attempts made on multiple > machines, including machines he's never logged into before, always the > same message: > > --------------------------- > Microsoft Outlook > --------------------------- > Cannot start Microsoft Outlook. Cannot open the Outlook window. The > set of folders cannot be opened. You must connect to Microsoft > Exchange with the current profile before you can synchronize your > folders with your Outlook data file (.ost). > --------------------------- > OK > --------------------------- > > User gets in fine with OWA. > > I've used various command line switches for Outlook, including > /resetfolders, /resetfoldernames, /resetnavpane, etc. I've tried > turning cached mode off and on, using encryption and not, and deleting > both the Outlook and Windows profiles. Nada. > > I see nothing in the workstation event logs, nor anything on the CAS > or DB server event logs either. > > Nothing seems amiss via the Exchange GUI. > > I'm going blind looking at google, too. > > Anyone have something else I can try? > > I'd prefer not to export to PST and nuke the mailbox, but it might come to > that. > > Kurt > >
