g

I am attempting to get an Outlook 2003 client to connect to an Exchange 5.5
Server. I am able to add the account fine and it can verify the account
name. It can also view the Global Address Book without any issues, however
I can't access the mailbox. Whenever you attempt to access the mailbox, I
get the following error.

Unable to expand the folder. The set of folders could not be opened.

I am also unable to change the message delivery location to the Mailbox from
personal folders. The error message here is "The specified default store
could not be opened. Please make sure you can access your default store and
try again."

This occurs when I am logged into the client as the local administrator and
the machine is not part of the domain. I have set the option to always
prompt for a username and password.

When I add the machine to the domain, but am still logged in as the local
administrator, the samething occurs.

Finally, When I am logged in as a domain user, I get the same message.

Any suggestions? Is Outlook 2003 incompatible with Exchange 5.5?

Thanks for any help
Gerrard

tim hackbart [msft]

Gerrard

Outlook 2003 is compatible with Exchange 5.5. The only known issue is if
you are using OWA 5.5 you need this hotfix.

818709 Outlook Web Access Stops Responding When You Try to Access a Mailbox
on
http://support.microsoft.com/?id=818709

The other difference is that OL2003 will only make a connection to the
Exchange server over the TCP-IP protocol. Previous versions of OL would
fallback to NamedPipes or other protocols if TCP-IP is not available.
832396 Outlook 2003 uses only TCP/IP or HTTP protocol bindings when Outlook
http://support.microsoft.com/?id=832396

The first thing I could think of is that maybe your Exchange 5.5 server does
not have a TCP endpoint for the Store and Directory service and your other
clients are falling back to Namedpipes. I usually see this when the TCP
ports were statically mapped incorrectly.
155831 XCCC: Setting TCP/IP Ports for Exchange and Outlook Client
Connections
http://support.microsoft.com/?id=155831
Check the registry keys in the above article and make sure that if they are
there they are all unique and in the 4000-5000 range.

To further troubleshoot this issue you may want to use RPCPing and RPCdump
as explained in the following KB's
831051 How to Use the RPC Ping Utility to Troubleshoot Connectivity Issues
with
http://support.microsoft.com/?id=831051

I do hope this helps.

--
Tim Hackbart M.C.S.E.
This posting is provided "AS IS" with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.