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

Exchange Error

Getting error in Exchange 2010

Unhandled Exception "User setting 'PreferredSite' is not available. "
Stack trace:
0
Gaurav Singh
Asked:
Gaurav Singh
  • 6
  • 5
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I would look at your AD Sites and Services and check what site names you have and ensure that all of your network subnets are associated with a site
Then run the Get-ClientAccessServer | fl Auto* to verify that it is handling all sites
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26911287.html

What is the Exchange 2010 SP and RU ??

- Rancy
0
 
Gaurav SinghSolution ArchitectAuthor Commented:
I checked the link, we have 3 exchange servers two on 1 site and other is in DR site... 3 subnets in DR site... Exchange 2010 SP2 RU 4
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Where do you get this error -- Event logs ? EMC or Shell ?

- Rancy
0
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!

 
Gaurav SinghSolution ArchitectAuthor Commented:
I am getting this error in Event logs...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/98b14c5b-b928-4213-ad63-a272101342a7

I agree, I'd hate to reinstall a server inorder to fix an issue.
I sumbled upon this while looking for a solution to the same issue with a different cause, I realize this is a very old post and is likley already resolved.  
Here is what I did to fix my issue.

Get-ClientAccessServer | fl Auto*
Make sure that all of my CAS servers had valid AutoDiscoverSiteScope settings (one of them had a site that nolonger existed)
 Set-ClientAccessServer $BadCAS -AutoDiscoverSiteScope $CorrectADSite
Problem Solved.

Are you getting this on the DR server or the CAS on the production site ?
Most of the links say that the Site association to the CAS is the problem ?
Did you happen to remove any DC\GC or AD site ?


- Rancy
0
 
Gaurav SinghSolution ArchitectAuthor Commented:
This is on CAS server... we have removed DR server from DAG..
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
How many AD sites do you have and which site is the CAS pointing to ?
Did you happen to remove any DC\GC or AD site ?


- Rancy
0
 
Gaurav SinghSolution ArchitectAuthor Commented:
CAS pointing to single AD site and DR server is pointing to DR site
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Is it possible to restart the AD topology or the server ..... maybe if everything is right it shouldnt be throwing such error.

Also please make sure all Exchange services and others are started on the CAS server. Run the below command

Test-ServiceHealth

- Rancy
0
 
piyushranusriSystem Cloud SpecialistCommented:
0
 
Gaurav SinghSolution ArchitectAuthor Commented:
I am not deploying Exchange, it is already setup and few days back started getting the error.
0
 
Gaurav SinghSolution ArchitectAuthor Commented:
None of the solution worked, still getting the error, so closing the question
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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