• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4044
  • Last Modified:

Exchange 2003 error message - "The specified default store could not be opened. Please make sure you can access your default store and try again"

I have 2 servers in a domain - a Windows 2000 server (SP4) running as a AD Domain Controller/File and Print server, and a Windows 2000 server (SP4) running ISA server 2000 (SP1).  I have just recently installed Exchange 2003 on the ISA server (running in native mode).  There was 10 pre-existing domain accounts prior to the exchange install, and I have created one new account since the exchange install.  All pre-existing accounts had personal folders set up in outlook 2003.

When I try to add the Exchange service to any existing user (running Outlook 2003) I can resolve the user's mailbox on the Exchange server, as long as I don't change the data store to the Exchange mailbox (ie leave as Personal Folders).  If I try to change this, I get the following message "The specified default store could not be opened. Please make sure you can access your default store and try again".  If I try to resolve the exchange properties of the newly created user, I get an error message saying outlook is offline.


Please advise if you require any further information.

Thanks in advance.
1 Solution
I would suspect ISA. Can you turn off you rules and then test?
It appears that Outlook can resolve the name (NSPI lookups) just not open the mailbox (Mapi lookups) turning off ISA will test if those ports are being blocked.
Does OWA work? try http://localhost/exchange in the browser

ceejay27Author Commented:
Hi Adam,

Yes, OWA works.  Disabled ISA but still get the same error messages.

Thanks for you assistance so far...
David WilhoitSenior Consultant, ExchangeCommented:
Create a new profile in Outlook 2003, forget the one they already have. does the new profile work? If not, verify that the user has SELF rights on the mailbox, in AD users and computers.

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

ceejay27Author Commented:
Created new profile - didn't work (same error).  Checked AD, SELF has full mailbox access.
David WilhoitSenior Consultant, ExchangeCommented:
1. Is any account accessible from Outlook?
2. Can you send mail either internally or externally to these mailboxes?
3. Is each workstation using the internal DNS server on the AD box, and is your Exchange server pointed to the same internal DNS?

I ask the simple stuff, because Exchange should work cleanly in this setup, with the exception of the trickiness of ISA. No proxy client installed on the Exchange box?

ceejay27Author Commented:
Hi Kidego,

Sorry for the delay.

1.  No.
2.  I can send and receive email internally via OWA.  not using for external email as yet.
3.  Yes, and yes.

Also, no proxy client is loaded on the exchange/isa sever.

David WilhoitSenior Consultant, ExchangeCommented:
ahhh, you know what? did you in-place upgrade the Outlook client to 2003? I saw this last month on the board here, seems the RPC protocol gets dinged in teh upgrade.


read thru this, and test out the steps to repair the RPC on a singel desktop, see if this works....

ceejay27Author Commented:
outlook install of test machine was a clean install.  Outcome of KB article:

Step 1: Verify Registry Entries - all present and accounted for
Step 2: Verify the Version of the DLL File - version correct
Step 3: Remove and Then Reinstall TCP/IP - first time after reboot was able to resolve mailbox name, but unable to connect to mailbox.  Eventually, was able to connect after performing a detect and repair of Office 2003.

Tried step 3 on another box (but this time was only able to use "netsh int ip reset [log_file_name]" to reset tcp/ip as uninstall option was greyed out) and then a detect and repair, but this didn't work - same unable to connect error message.

I also am unable to attach on a W98SE machine running Office 2000.

Thanks for your help so far...

David WilhoitSenior Consultant, ExchangeCommented:
How about the bind order on the network card on the server? When performing a check name, does it work? Something odd, just haven't found it yet. Please post any errors in the applog relevant to Exchange and DSAccess.

Does the 98 client have the dsclient installed?

PAQ'd and 250 points refunded.
Questionner will post "Points for" questions to reward the experts for their effort !


Community Support Moderator
Experts Exchange
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now