title: What is the best approach to handle exceptions in WCF service?
body: <p>I have a WCF service deployed on two or more remote machines and there is a desktop based application that is used by the client to access any wcf service.</p>
  
  <p><strong>The WCF service is connected to SQL server 2005 to read and write data.</strong>
  This is an intranet scenario in which the client should be on same domain.</p>
  
  <p>Now there can be scenarios where the wcf service throws exceptions:</p>
  
  <ol>
  <li>Invalid URL</li>
  <li>WCF service is down</li>
  <li>SQL server 2005 is not running</li>
  <li>Client is not on the same domain</li>
  <li>Authentication fails</li>
  <li>Authorization fails</li>
  </ol>
  
  <p>and many other exceptions.</p>
  
  <p>For every exception I have to perform some action or update a status bar, depending on the exception. For example if authorization fails I have to prompt the user to re-enter their credentials.</p>
  
  <p>Please suggest the best design approach to handle this.</p>