[THIN] Re: Outlook PST Files
- From: "Turman, David C." <david_turman@xxxxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Mon, 1 May 2006 16:31:31 -0500
No extra devices, (VOIP, FAX, PDA, etc) but those registry keys do
exist.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Kinchen, Tyler
Sent: Monday, May 01, 2006 2:56 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Outlook PST Files
David, do you have other MAPI applications accessing Outlook (VOIP, fax
client, PDA software)? Can you check and see if you have either of the
following registry keys?
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Microsoft Office Outlook
Or
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Microsoft Outlook
Regards,
Tyler Kinchen
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Turman, David C.
Sent: Monday, May 01, 2006 1:54 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Outlook PST Files
Though not specifically a Term Server issue, I thought some
smart person here could help.
Our users run either Outlook XP or Outlook 2003 on Windows 2000
and
Windows XP PCs'. We currently are running Exchange 2000. The
users keep
PST files out on their network shares, which reside on Windows
2003 Server
Clusters (HP DL 585) and the disks are on a SCSI Fiber Attached
EMC Clarion 300 CX SAN.
The users will be in Outlook and when they try to get to a
folder is a PST they get
"The set of folders could not be opened. The server is not
available. Contact
your administrator if this condition persists". And if they try
to move something
to or from the PST they get "Can't move items The file
\\servername\filename.pst <file:///\\servername\filename.pst> could
not be accessed"
If they click on one of the folders in the PST files a few times
it may eventually open,
or if they go to Explorer and click on the file from inside
there it may. It seems that
if they have the file on a SAN based drive it is much more
susceptible to this.
I know that MS does not support PST files on network drives, but
this has been working
fine for years, until we moved from fiber attached "local" disks
and Windows 2000 to
the Windows 2003 / EMC combo. Any ideas?
Other related posts:
