Link to home
Create AccountLog in
Avatar of City_Of_Industry
City_Of_IndustryFlag for United States of America

asked on

Cannot open your default (e-mail) folders, ...

Recently set up clean installation of Exchange Server 2010 Standard Edition on Window Server 2008 R2 without any problem.

Windows XP client with Office 2007 Enterprise Edition SP2.

When setting up Outlook 2007 on client's PC, email address and name resolution were sucessfully filled and found.

Open Outlook it showed " Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your offline folder file"

If disable cached Exchange mode, error message change to "Cannot open your default folders. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance."

Run lots of solutions in this forum still can't resolve the problem.  Please help.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Does this user have access to the mailbox, check Exchange Server event logs?
Avatar of City_Of_Industry

ASKER

user is domain administrator group

BTW our PDC is Windows Server 2003
Ther is error message in Exchange Server event log

Process MSEXCHANGEADTOPOLOGY (PID=1536). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.
This error message's timestamp was earlier

Process MSEXCHANGEADTOPOLOGY (PID=1536). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object [Exchange Server Name] - Error code=8007077f.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
so this is a new installation, so no users can login?
Yes, it is new installation and try the first Outlook client setup.
Exchange is not installed on a Global Catalog Server?
Hi City_Of_Industry.
Are all the Exchange Services running?

Once the server is running properly the client will connect correctly.
A new Client, set up to run in Cache Mode (with Offline folder) still needs to connect to the server the first time.
Is the user a NEW user, or an upgrade to Outlook 2007. If the former, Exchange is the problem, if the latter, you may have more than one problem.
Avatar of 1intelsys
1intelsys

are you using exchange server 2007 or 2003? we had this issue with exchange server 2007 and outlook client 2003. there is an option to enable backwards compatibility, i wont elaborate too much so as not to waste your time. respond back with the details and i can explain further.
Exchange Server 2010 is on Windows Server 2008 R2 which is member server.

This is the first Exchange Server on this domain.

All clients are Windows XP Pro SP3 with Office 2007 Enterprise SP2

Global Catalog Server is on PDC which is Windows Server 2003 SP2.

I suspect the problem maybe in that two error messages of Exchange Server posted above, working on that right now ...
SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Yes all services are started correctly and run Exchange Analysis with out any error messages.
any other exchange related errors or domain errors on the DCs?
No, only those two error messages posted above showed in Event / Application log
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
It happened unexpectedly, we have power failure in our server room, server re-start itself then problems are gone.
in that case, it's possible that services are not starting correctly, or the startup sequence or dependices are incorrect.
hanccocka,

Thank you for your comments and your valuable time to looking into this question.
Lucky solution