I am trying to setup a test exchange environment so I can test an upgrade path for our archiving software. I am getting an ERROR: Could not connect to the Microsoft Exchange Information Store service on server when trying to access the Mail stores on the Exchange server from one of the XP clients in the environment. Also from the XP clients when trying to run Load Gen it complains it can't connect via MAPI and when opening outlook it always asks for credentials which seems odd. I've also tried running the BPA and it comes up with no errors. The environment I am running is an ESXi 4.1 host, Network running on isolated vSwitch (10.10.0.x), Server 2008 32b Domain Controller (Native 2008 Domain), Server 2008 32b Exchange 2007 Server HUB/CAS/Mailbox, Server 2003R2 32b Zantaz EAS Server and two XP SP3 clients for admin and Outlook connectivity. I have read some of the other postings regarding this error and have tried all of the suggestions with no success. This is my first crack at setting up a net new exchange environment so any help would be greatly appreciated.Merlin Boissonneault Sr. Technical Analyst Messaging/OCS Northern Health

Just to confirm> None of the clients can access Exchange or just one? Which suggestions have you already tried?

Hi Andy, The Outlook client will connect but it prompts for credentials. I have not yet been able to verify that mail will flow between mailboxes yet. I am trying to get LoadGen to populate the server so I something for the archiving software to pick up. I have tried the following suggestions below. Warning: ERROR: Could not connect to the Microsoft Exchange Information Store service on server EX01.NHATEST.local. One of the following problems may be occurring: 1- The Microsoft Exchange Information Store service is not running.: I have verified the service is in fact running. 2- There is no network connectivity to server EX01.NHATEST.local.: I can ping the server from the clients and outlook will connect after prompting for credentials. 3- You do not have sufficient permissions to perform this command. The following permissions are required to perform this command: Exchange View-Only Administrator and local administrators group for the target server.: The account I am using is a domain admin and Exchange org admin. 4- Credentials have been cached for an unprivileged user. Try removing the entry for this server from Stored User Names and Passwords.: I have verified that there are no cached credentials. Do you have any other suggestions? Merlin Boissonneault Sr. Technical Analyst Messaging/OCS Northern Health

What’s the Zantaz EAS Server, ZANTAZ Enterprise Archive Solution (EAS) for exchange? How do you get the error “Could not connect to the Microsoft Exchange Information Store” on XP client, by launching outlook client or running cmdlets in EMS? Please check if there’s any incorrect host entry in the “host” file, which would cause the error information in this post Host file path: c:\windows\system32\drivers\etc Please verify if the problematic user can access mailbox correctly via OWA Please verify that the window will prompt for credential on outlook for newly created mailbox and mail profile Please increase the diagnostic logging level on the exchange server, reproduce the issues (Error “Could not connect …” and password prompt), and then monitor the related event in the application log on the exchange server MSExchangeIS\9000 Private\General MSExchangeIS\9000 Private\Logons MSExchangeIS\9000 Private\Access Control Resources: Diagnostic Logging of Exchange Processes James Luo TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi James, It is the Zantaz Enterprise Archive Solution. I get the error on the XP client by opening the EMC and going to Server Config --> Mailbox and when it tries to load that is when the Could not connect error shows up. I have checked the host files and there are no strange entries, this is a net new environment that was built for these testing purposes. I have tested OWA and it works for all users. I created a new user and tried to setup its client, when i open outlook it tells me that exchange if Offline. If i go to an old profile it will prompt me for a password. I will get back to you on the logging details.Merlin Boissonneault Sr. Technical Analyst Messaging/OCS Northern Health

Does the EMC error still appear when you launch it directly on the exchange server? Please use the EMTshooter tool to troubleshoot the issue on the EMC (Reference) What’s the outlook client version? On the problematic client, please run Test E-mail AutoConfiguration on the internal outlook client, and then check the output (Reference) Please verify the configuration on the virtual directories on the exchange server Default settings for Exchange-related virtual directories in Exchange Server 2010 James Luo TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi James, I was able to sort out the Outlook client issues, the Office disk i used to install contained profile information for our production environment. I downloaded a fresh copy from technet and reinstalled from that and did not get the Exchange offline error. I am however still getting prompted for credentials when i open outlook. The EMC works fine from the exchange server its only when i try to use it from one of the client machine. I will try the EMT and check the virtual directories. Any ideas of other things that i can possibly try? Cheers,Merlin Boissonneault Sr. Technical Analyst Messaging/OCS Northern Health

Could you provide the outlook client version? The connecting procedure is the same for launching the management tools (EMC/EMS) from client machine, or the server locally. So, the issue shouldn’t be on the server side. Please refer the article below to confirm if you have met the prerequisites to connect the exchange server from client machine Connect Remote Exchange Management Shell to an Exchange Server Resources: Troubleshooting the Exchange Management ShellPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How's the issue currently?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.