D
Dan Sheehan
Greetings.
A colleague and I both just tried to switch our Outlook 2003 clients
to using cache mode. Upon restart, I got the following error:
"Unable to open your default e-mail folders.
This error can occur if you attempt to run Outlook from a Terminal
Server
session when the OST file is in use by the console session. To access
this
instance of Outlook, exit the current Terminal Server session and
start a new
session by using the following Run command (click Start, then click
Run):
mstsc.exe /console"
He got a similar error message. We tried lots of different things on
the web, to no avail. If we switched it back to not using cache mode,
it was fine. Checked the local profile settings (not using roaming)
and those were all fine as well (including the permissions as far as I
can tell). Re-creating the profiles didn't help either.
During my various tests, I could never find an OST on the file system,
so I went into the profile to see where it thought it was storing the
offline file. It pointed to the default location, but there was no
OST. I used the browse button to re-select the same directory, and
Outlook prompted me to create the OST file. After I said yes and
closed out the profile, Outlook 2003 opened just fine.
I was running Outlook 2003 SP2, and my colleague was running Outlook
2003 w/o a SP.
Any ideas as to why Outlook was not auto-creating the OST file?
This is also an FYI to the "fix" as I saw a couple of older posts on
the news groups of people having this exact issue.
Thanks!
Dan Sheehan
MCSE 2003 + Messaging
A colleague and I both just tried to switch our Outlook 2003 clients
to using cache mode. Upon restart, I got the following error:
"Unable to open your default e-mail folders.
This error can occur if you attempt to run Outlook from a Terminal
Server
session when the OST file is in use by the console session. To access
this
instance of Outlook, exit the current Terminal Server session and
start a new
session by using the following Run command (click Start, then click
Run):
mstsc.exe /console"
He got a similar error message. We tried lots of different things on
the web, to no avail. If we switched it back to not using cache mode,
it was fine. Checked the local profile settings (not using roaming)
and those were all fine as well (including the permissions as far as I
can tell). Re-creating the profiles didn't help either.
During my various tests, I could never find an OST on the file system,
so I went into the profile to see where it thought it was storing the
offline file. It pointed to the default location, but there was no
OST. I used the browse button to re-select the same directory, and
Outlook prompted me to create the OST file. After I said yes and
closed out the profile, Outlook 2003 opened just fine.
I was running Outlook 2003 SP2, and my colleague was running Outlook
2003 w/o a SP.
Any ideas as to why Outlook was not auto-creating the OST file?
This is also an FYI to the "fix" as I saw a couple of older posts on
the news groups of people having this exact issue.
Thanks!
Dan Sheehan
MCSE 2003 + Messaging