The application log on Windows Small Business Server shows the following errors:

1. Event ID 2424, The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application 'Search', Catalog 'index file on the search server Search'
2. Event ID 3760, SQL Database 'ShareWebDb' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below. Cannot open database "ShareWebDb" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
3. Event ID 3355, Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query not found. Additional error information from SQL Server is included below. Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

SQL Server Management Studio Express, a graphical management tool based on SQL Server Management Studio that makes it easy to manage and administer SQL Server Express databases. If yo are running Windows Small Business Server 2008, Management Studio Express is already installed. It can be accesses by selecting, Start/Programs/Microsoft SQL 2005/SQL Server Management Studio

You can use this tool to manage SQL Express Databases by installing the SQL Server Management Studio Express from
http://msdn2.microsoft.com/sv-se/express/bb410792.aspx

NOTE: Make sure you download the SQL Server Management Studio Express and not the Microsoft SQL Server 2005 Express Edition

1. Press Options icon
2. Select Device
3. Select Device and Status Information

Blackberry Desktop Software can be downloaded from here:
https://www.blackberry.com/Downloads/browseSoftware.do;jsessionid=E6C4B48BFA11D0486280FA4FDE663F58.node2

This issue applies to Worry Business Security Standard v6.0 SP2

Issue
Double clicking on the Trend Micro icon in the system tray shows the firewall with status OFF. Issue occurred on one computer out of a total of 5. Attempted to uninstall and reinstall several times without success

Solution

1. We called Trend Micro support and indicated that this is a know issue and suggested that we perform the steps described in this KB article:
   http://esupport.trendmicro.com/Pages/To-complete-the-installation-restart-the-computer-always-appears-when.aspx
   The steps were performed and the issue remained.
2. We then downloaded the 3 patches for SP2 and installed. Uninstalled the troubled client and reinstalled. Still no cure.
   The patches were: B3132, B3154 and B3100
3. We were then given instructions to manually uninstall the client:
   http://esupport.trendmicro.com/Pages/Manually-uninstalling-the-ClientServer-Security-Agent-of-Worry-EN-1037502.aspx
   
   We then downloaded Service Pack 3 for WBS Standard edition and installed on the server. Uninstalled the Trend Micro Client on the client computer, still no cure.
4. The Solution
   We were finally told that the Cryptographic service on the computer was responsible and to uninstall the Trend Micro client, reinstall Windows XP SP3 and reinstall the Trend Micro Client. This corrected the issue and now the firewall turns ON and no more driver installation messages from Trend Micro.

We had a server that would not purge the Exchange Server 2007 log files after it was backed up using the Windows Small Business Server 2008 Backup (Windows Imaging Backup). In addition the event log displayed the following errors when the backup started:

Event ID: 565 Consistency check for component 'd0e6a265-d38e-4f6d-91cf-bc0ca049c8da'\'Microsoft Exchange Server\Microsoft Information Store\<server name>' failed. Application 'Exchange' will not be avaliable in the backup done at time '8/28/2010 11:00:03 PM'

Event ID: 9782 Exchange VSS Writer (instance a2e37eb9-fd4c-4cb5-9b5c-607857108522:1) has unsuccessfully completed the backup of storage group 'First Storage Group'. No log files have been truncated for this storage group.

Solution
To correct this issue we installed Exchange Server 2007 Service Pack and now the backup purges the log files.

Other Troubleshooting Steps
In researching this issue we used some tools that you may find usefull.

1. The following command will list all of the VSS writers and there current state.
   All should report their state with no errors, for example:
   Writer name: 'Microsoft Exchange Writer'
      Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
      Writer Instance Id: {074c8496-4064-498a-a590-f4d6f67d4b6f}
      State: [1] Stable
      Last error: No error
   Issue the following command from a DOS Prompt: VSSADMIN LIST WRITERS
   
2. This command will list the state of your Exchange Databases
   eseutil /mh "Mailbox Database.edb"
   Take a look at the following fields:
   State: Clean Shutdown
          ECC Fix Success Count: none
      Old ECC Fix Success Count: none
            ECC Fix Error Count: none
        Old ECC Fix Error Count: none
       Bad Checksum Error Count: none
   Old bad Checksum Error Count: none
   
   Repeat using the command using: eseutil /mh "Public Folder Database.edb"

We spend days trying to figure out we could not install the Security Update for SQL Server 2005 Service Pack 3 (KB970892). We've seen this issue on multiple computers. Once we changed the registry key as decribed in this artible the SQL update installed without errors.

Althought this article pertains to ACT, I believe it applies to any other SQL Express instances.

This is a reported issue. You also may find that the security update failing to install will cause the SQL Server ACT7 instance to stop and you receive a "Database Cannot be Accessed" error message if you open ACT! and try to open your database after. To attempt to workaround this issue and install the security update, please use the following steps:

Note: The following information is provided as a convenience. Sage does not provide support for Microsoft® Products. For more information on this topic go to Microsoft.com.
Click Start and select Run.
The Run dialog box appears. In the Select field, type regedit.

Caution: We strongly recommend that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure you modify only the keys specified. For detailed information on backing up the Windows® Registry, click the link below:

Title: How to Backup the Windows® Registry
Answer ID: 13807

Navigate to the following registry key:
32-bit Computers: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup
64-bit Computers: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1\Setup

Note: If you have multiple instances of SQL Server installed, the registry key may be different. You can verify by checking each MSSQL.x root key and locating the one which has ACT7 in the Name column on the right pane. In addition, you may need to follow the steps below for each MSSQL.x key to prevent to security update from failing..
Locate the Resume REG_DWORD entry on the right pane
Right click on the Resume entry and select Modify. Change the Decimal value from 1 to 0 and press OK.

Close the Windows Registry.
You should now be able to successfully install the SQL Server 2005 Security update via Windows update or from a manual download.

Rerefence: http://kb.sagesoftwareonline.com/cgi-bin/sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=25673&p_created=1256925768&p_sid=m3dcpf8k&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MSwxJnBfcHJvZHM9NjUxMiZwX2NhdHM9JnBfcHY9MS42NTEyJnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1rYjk3MDg5Mg**&p_li=&p_topview=1

Before running this command edit c:\windows\system32\etc\drivers\hosts and add entry for 127.0.0.1 localhost. Not doing this will cause the following error to be displayed by vihostupdate.pl: 
Error connecting to server at 'https://ESXI Host IP/sdk/webService': Perhaps host is not a Virtual Center or ESX server

1. You must install vSphere CLI - Download Here vCLI
2. Download the Upgrade Package for 4.0 to 4.1 or the Upgrade Package from 3.5 to 4.1
3. Power off your VM's and put the host into maintenance mode
4. Go to a command prompt
5. Type C: enter
6. Type cd "\Program Files\VMware\VMware vSphere CLI\bin"
7. Type: vihostupdate.pl --server hostname or IP -i -b upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip -B ESXi410-GA-esxupdate
8. Type: vihostupdate.pl --server hostname or IP -i -b upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip -B ESXi410-GA

Tried both solutions below and none of them corrected the issue.

1. Start regedit.exe
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\
3. Right-click MSV1_0. Point to New, and then click Multi.-String value.
4. Type BackConnectionHostNames, and then Press ENTER.
5. Right-click BackConnectionHostNames and then click Modify. In the Value data box, type name of your remote.???.???  (whichever you have!), and then click OK.
6. Right-click BackConnectionHostNames and then click Modify. In the Value data box, type name of your Companyweb, and then click OK.

The above entries did not fix the issue for us, althought the SBS Best Practice Analyzer said that these entries needed to be created, it's problably a good idea to create them if you don't have those entries.

What did fix the issue was as follows:
1. Download http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab to a temp folder.
2. Double click on the file and copy the authroot.stl
3. Go to a command prompt and type: certutil -f authroot.stl
4. Reboot the server and check the application log for event id: 11

Reference: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/54ec7afa-3d9b-45c1-befa-a3229d18214b
Reference: http://blogs.technet.com/b/instan/archive/2010/08/12/capi2-event-id-11-errors-on-machines-that-don-t-have-access-to-the-internet.aspx

Another possible solution:
1. Backup and delete the contents of the following folders:
C:\Windows\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content
C:\Windows\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData
2. Backup and delete the certificates listed under "Certificates" key:
HKEY_LOCAL_MACHINE\Software\Microsoft\SystemCertificates\AuthRoot\Certificates
Then, restart the server to check the result."

Windows XP ONLY: I have installed the latest available root certificates (http://www.microsoft.com/downloads/details.aspx?FamilyID=f814ec0e-ee7e-435e-99f8-20b44d4531b0).
Reference: http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/685e65f6-72a7-4986-b02c-f17e8be78926

Windows will display error message when performing Offline Synchronization if it encounters a file that it connot synchronize such as database files, outlook PST files etc. To disable the error message and prevent Offline Sync from stopping do the following:

1. Start Regedit
2. Go to HKLM/SOFTWARE\Microsoft\Windows\CurrentVersion\Syncmgr
3. Add a DWORD value: KeepProgressLevel=0

Download the following file and double click on it to make the entry for you:
OffLineSyncErrors.reg (298.00 bytes)