Hello, Is the Outlook working fine for this user. because, looking at the error message, it seems to be a AD replication issue.S.A. Jones | Exchange 2003/2007/2010 | Remember to Mark as Answer if this Helps!

Hello, Is the Outlook working fine for this user. because, looking at the error message, it seems to be a AD replication issue.S.A. Jones | Exchange 2003/2007/2010 | Remember to Mark as Answer if this Helps!

Hi, I have an SBS 2008 server. Exchange 2007 is obviously installed in it. A strange issue has occurred. I was unable to open Exchange Management Console. That issue was resolved by repairing .NET Framework installation. This was done by running the repair tool for .NET framework, which was available from microsoft download site itself. After this, the OWA was not accessible. I have performed the following resolution steps. I recreated the OWA virtual directory and OWA was accessible. But, then the next wierd thing. Now, OWA will appear and prompt for my username and password. Once I enter it, I get an error screen as shown in the attachhed screenshot. Any thoughts regarding this? Please share it. Thanks in advance.Tom Jacob

Hi Tom, Any udpate? It is useful to test in Outlook so that we may confirm the mailbox account is working fine. You may also try the steps below to troubleshoot this issue: 1. Restart Exchange Information Store service; 2. Restart IIS service; 3. Check IIS log/application event log in the CAS server to see what error cord is recorded when the issue occurs. Hope it is hlepful. Fiona Liao TechNet Community Support

I have resolved it. The Exchange server was actually configured with an incorrect domain controller. I changed it and configured with the correct domain controller and the issue was resolved. Earlier, i forcefully initiated a full AD replication and it was completed successfully. But, still the issue was persisting. I manually changed the domain controller which is configured and the issue was resolved. Thanks a lot for the suggestions and helps. ThanksTom Jacob

Hi Fiona Liao, Thanks for the suggestion. I had tried the steps you had told but still the issue was not resolved. However, I had resolved it, by changing the domain controller configured in the Exchange Server. The domain controller which was configured initially was wrong, and that was the reason behind the whole issues. I do appreciate the help which you guys has tried, when I was really in a mess. ThanksTom Jacob

On Tue, 9 Oct 2012 17:57:52 +0000, FriendzKnight wrote: >I have resolved it. The Exchange server was actually configured with an incorrect domain controller. I changed it and configured with the correct domain controller and the issue was resolved. Earlier, i forcefully initiated a full AD replication and it was completed successfully. But, still the issue was persisting. I manually changed the domain controller which is configured and the issue was resolved. Thanks a lot for the suggestions and helps. Why are you not letting the Exchange server figure out which Dcs and GCs to used based on site membrship? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Tom, Thanks for your update and sharing. Have a nice day:)Fiona Liao TechNet Community Support