SharePoint Updates Cause Site to Fail

Config Wizard Access Denied
http://blogs.catapultsystems.com/mpoole/archive/2011/02/12/sharepoint-2007-config-wizard-access-denied.aspx

Cannot Connect to the Configuration Database
http://social.technet.microsoft.com/Forums/en-US/sharepointgenerallegacy/thread/8b3094a1-31ee-49d7-ab02-72ca0dc440a7/

SharePoint 3.0 Site Inaccessible After Update
http://social.technet.microsoft.com/Forums/en-US/sharepointadminlegacy/thread/e8391454-a5b2-418f-8dab-324c430ce219/

Add Old Content Database to New SharePoint Site
http://alkalony.wordpress.com/2009/08/25/add-existing-content-database-to-a-site-collection-using-stsadm/

Restore SharePoint 2.0 Site
http://support.microsoft.com/kb/829113

Connecting to Windows Internal Database MICROSOFT##SSEE

This is often useful when administering Sharepoint services on a Windows SBS 2008 system:
http://www.networkinghowtos.com/howto/connecting-windows-internal-database-microsoftssee/

If inaccessible after an update:
http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx

http://support.microsoft.com/kb/944267?wa=wsignin1.0

Notes on Recovering / Restoring Exchange

Here are a few key sites regarding recovery or restore of Microsoft Exchange:

Checking Database State or Integrity
http://community.spiceworks.com/how_to/show/2943-find-and-replay-missing-log-files-in-exchange

Database in Dirty State
http://blogs.technet.com/b/mspfe/archive/2012/09/06/why-exchange-databases-might-remain-dirty-after-eseutil-r-recovery.aspx

Backup Recovery Issues
http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/9af2afca-3e49-4fa6-ad06-5c6c50671a45